[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: cygwin dlopening backends
From: |
Ralf Wildenhues |
Subject: |
Re: cygwin dlopening backends |
Date: |
Sat, 12 Nov 2005 14:03:22 +0100 |
User-agent: |
Mutt/1.5.9i |
Hi Charles, Eric,
* Charles Wilson wrote on Thu, Nov 10, 2005 at 05:55:28AM CET:
>
> What "interface id" should loadlibrary.c's vm_open() itself use?
> loadlibrary.c is not itself a module...or is it?
Yes, it is. In CVS HEAD, it's a dlpreloaded (static) module.
> Note that most of the args "passed-thru" to the linker are given
> '-Xlinker' precedents, but the --enable-auto-image-base uses '-Wl,'
> instead. Should this be "fixed"? The current syntax 'works' (or would,
> if it weren't for that missing lt_dlhandle_next symbol) but
> stylistically the inconsistency is ugly.
Hmm. We changed the '-Wl,$lib' specifically for MSYS, because we need
the shell to do the path conversion to w32 paths here. We could use
'-Xlinker --enable-auto-image-base' as well, I guess, for consistency,
but then again all linker flags passed by the user will have '-Wl,'
prefixed, so that would still be inconsistent. OTOH, changing all to
'-Xlinker' uses a tiny bit more command line length, a scarce resource
on w32. We could also separate mingw from cygwin setting here..
Shrug. I don't know. What do you like best?
(Some patches for the actual bugs coming up in another mail..)
Cheers,
Ralf
Re: cygwin dlopening backends, Charles Wilson, 2005/11/13