RFC: Cygwin 64 bit?

Christopher Faylor cgf-use-the-mailinglist-please@cygwin.com
Sat Jul 9 19:30:00 GMT 2011

On Sat, Jul 09, 2011 at 11:34:14AM +0200, Corinna Vinschen wrote:
>On Jul  8 22:04, Charles Wilson wrote:
>> strings ld.exe shows the following:
>> SEARCH_DIR("/usr/i686-cygwin/lib"); SEARCH_DIR("/usr/lib");
>> SEARCH_DIR("/usr/lib/w32api");
>> [...]
>> FWIW, on  linux64 (fedora 15) I see this:
>> SEARCH_DIR("/usr/i386-redhat-linux/lib"); SEARCH_DIR("/usr/lib64");
>> SEARCH_DIR("/usr/local/lib"); SEARCH_DIR("/lib"); SEARCH_DIR("/usr/lib");
>That's that.  But that doesn't explain how we can convine ld to prepend
>the relative path to ../lib{64}.  And how to make this decision

Those are all locations where ld searches for libraries.  It does not
control where a linked program searches for libraries.

>FWIW, `strings /bin/ls' on a 64 bit Linux shows these bindings:
>  libselinux.so.1
>  librt.so.1
>  libcap.so.2
>  libacl.so.1
>  libc.so.6
>  libdl.so.2
>  /lib64/ld-linux-x86-64.so.2
>  libpthread.so.0
>  libattr.so.1
>So, how did it happen that /lib64 is prepended to ld-linux-x86-64.so.2,
>but all other libs are just plain filenames?  Maybe that gives us some
>clue how to do it in Cygwin.

/lib64/ld-linux-x86-64.so.2 is the runtime link loader so it needs to
be explicit.


More information about the Cygwin-developers mailing list