Re: symlink dll
Max Bowsher schrieb: IT WILL NOT WORK! Try it yourself if you like. Ah sure, static PE imports. So we just have to use delay loading for ld, similar to the MSVC linker. Then via some kind of libcygdelay.a with a symlink resolver before LoadLibrary(). Wine winegcc has it. http://www.mail-archive.com/[EMAIL PROTECTED]/msg20983.html But ld --help | grep delay is empty Still not there? Should be --delay-lib Should not be hard. Objections cgf? http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vccore98/html/vcconunderstandinghelperfunction.asp http://www.esat.kuleuven.ac.be/~gcc/shared_libraries.html -- Reini Urban http://xarch.tu-graz.ac.at/home/rurban/
Re: [setup] Why does PackageSpecificationhaveaprivatecopy-constructor? (Robert?)
Robert Collins wrote: On Tue, 2004-08-31 at 23:42 +0100, Max Bowsher wrote: Unless we add explicit copy-constructors to every single class, I'd rather just leave it out and let the compiler handle things implicitly? It seems cleaner to me. I think you'll find every class that has a destructor also has an explicit copy constructor assignment operator. That class certainly has an explicit assignment operator... being explicit on the copy constructor is consistent. Have you heard of the 'rule of 3' ? No. Apparently I need to do some reading. Max.
Re: [setup] Why does PackageSpecificationhaveaprivatecopy-constructor? (Robert?)
On Wed, 2004-09-01 at 08:12 +0100, Max Bowsher wrote:
Robert Collins wrote:
Have you heard of the 'rule of 3' ?
No. Apparently I need to do some reading.
http://www.parashift.com/c++-faq-lite/coding-standards.html#faq-27.9
A class with any of {destructor, assignment operator, copy constructor}
generally needs all 3
Cheers,
Rob
signature.asc
Description: This is a digitally signed message part
Re: [ITP] ocaml-3.08.1-1
On Aug 31 12:18, Igor Pechtchanski wrote: On Tue, 31 Aug 2004, Corinna Vinschen wrote: Urgh, even worse, both archives were broken as well. For some reason I can't download them using curl. Wget worked, though. I fixed them. Could be a problem with the logging script used on the site. I haven't tested it with curl, only wget and Netscape/Firefox/IE. If curl is what you normally use, I'll install it and make sure that the site works with it for the future. That would be nice. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:[EMAIL PROTECTED] Red Hat, Inc.
Re: [ITP] ocaml-3.08.1-1
On Wed, 1 Sep 2004, Corinna Vinschen wrote: On Aug 31 12:18, Igor Pechtchanski wrote: On Tue, 31 Aug 2004, Corinna Vinschen wrote: Urgh, even worse, both archives were broken as well. For some reason I can't download them using curl. Wget worked, though. I fixed them. Could be a problem with the logging script used on the site. I haven't tested it with curl, only wget and Netscape/Firefox/IE. If curl is what you normally use, I'll install it and make sure that the site works with it for the future. That would be nice. Corinna Will do. Since I've never used curl, however, what's the exact command line you use to grab the package files? This'll save me some experimenting with options... Thanks, Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! Happiness lies in being privileged to work hard for long hours in doing whatever you think is worth doing. -- Dr. Jubal Harshaw
Re: [setup] Why doesPackageSpecificationhaveaprivatecopy-constructor? (Robert?)
Robert Collins wrote:
On Wed, 2004-09-01 at 08:12 +0100, Max Bowsher wrote:
Robert Collins wrote:
Have you heard of the 'rule of 3' ?
No. Apparently I need to do some reading.
http://www.parashift.com/c++-faq-lite/coding-standards.html#faq-27.9
A class with any of {destructor, assignment operator, copy constructor}
generally needs all 3
After that, and further googling, I fully agree with the rule of 3.
However, it appears to me that PackageSpecification needs none of these.
copy-constructor: Was private, now gone.
destructor: Is currently present, but a no-op.
assignment operator: Is present and bizarre...
...in that it only assigns the name, not the operator or version!
This seems like a bug to me - and the only reason we haven't bumped into it
before, is because we haven't begun to use versioned dependencies.
So, unless there's something I'm not seeing, the destructor and operator=
can be removed too.
Max.
ocaml packaging dependency bug: curses vs. termcap
The recently produced ocaml package assumes that it will be able to find -lcurses when it links programs. I had to download the libncurses-devel package to get the linker working. I expect this should be included among the dependencies. (Perhaps gcc should as well, since the ocaml linker expects to use gcc.) (Before that, when I rolled my own ocaml, it always linked with -ltermcap instead. Forgive my ignorance, is it much better to use -lcurses instead?) BTW thanks for creating this package, it's something I had been intending to do myself for months now. Robert
Re: ocaml packaging dependency bug: curses vs. termcap
On Wed, 1 Sep 2004, Robert R Schneck-McConnell wrote: The recently produced ocaml package assumes that it will be able to find -lcurses when it links programs. I had to download the libncurses-devel package to get the linker working. I expect this should be included among the dependencies. (Perhaps gcc should as well, since the ocaml linker expects to use gcc.) Umm, right. Thanks for the heads-up. I'm a bit uncomfortable, though, with making the ocaml package depend on both libncurses-devel and gcc, since those are only needed for the native compiler, and people might just want to use the bytecode interpreter... There are a couple of solutions besides the above: split the package into the -bytecode and -native subpackages, where -native will depend on both gcc and libncurses-devel, or simply mention this dependency in the README (as I do with labltk). What do people think? (Before that, when I rolled my own ocaml, it always linked with -ltermcap instead. Forgive my ignorance, is it much better to use -lcurses instead?) That was an upstream choice -- the way it now builds OOTB pulls in -lcurses if it's installed. BTW thanks for creating this package, it's something I had been intending to do myself for months now. So had I, but I finally had to build a distributable version of it for work-related reasons, and figured why not submit the package?. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! Happiness lies in being privileged to work hard for long hours in doing whatever you think is worth doing. -- Dr. Jubal Harshaw
Re: ocaml packaging dependency bug: curses vs. termcap
On Wed, 1 Sep 2004, Igor Pechtchanski wrote: On Wed, 1 Sep 2004, Robert R Schneck-McConnell wrote: [ocaml linker requires gcc and libncurses-devel] Umm, right. Thanks for the heads-up. I'm a bit uncomfortable, though, with making the ocaml package depend on both libncurses-devel and gcc, since those are only needed for the native compiler, and people might just want to use the bytecode interpreter... FWIW, I was linking in bytecode, but with some external C functions linked in as well (with ocamlc -custom). I'd settle for a mention in the README. Incidentally, for the build requirements you list in the README: I'm pretty sure I needed to get some X libraries to build ocaml with labltk support... One more comment for the README. When running ocaml programs using labltk, I would always get exception Protocol.TkError(Can't find a usable init.tcl in the following directories: C:/cygwin/share/tcl8.4 ... The solution I found was to either set TCL_LIBRARY or (conveniently) run ln -s /usr/share /share Better, I think, would be to configure the ocaml package so that labltk looks for init.tcl where cygwin puts it. Do you know how to do that? (I don't.) Robert
