This is the mail archive of the
cygwin-developers
mailing list for the Cygwin project.
Re: RFC: Cygwin 64 bit?
On Jul 9 15:30, Christopher Faylor wrote:
> 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
> >conditional.
>
> Those are all locations where ld searches for libraries. It does not
> control where a linked program searches for libraries.
I know. The "prepend relative path magic" must occur in ld, though.
> >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.
Ah, that's all? How disappointing.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat