RFC: Cygwin 64 bit?

Stan smoore@exis.net
Sun Jul 10 20:50:00 GMT 2011


On Sat, Jul 09, 2011 at 11:26:31AM +0200, Corinna Vinschen wrote:
> On Jul  8 21:16, Christopher Faylor wrote:
> >   What I wouldn't like to see is ld being changed to
> > force every -lrary refererence to default to ../lib64/cygrary.dll .

<snip> 

> The next question is, how does ld know if it should maintain ../lib or
> ../lib64 in the executable or not?  strcmp?  I don't know.  Any idea
> how this could be made conditional in a intelligent/useful way?

This isn't relevant to the above discussion, but yesterday I was
reading the FHS for another project and came across this almost
relevant little tidbit.

----------------------------------------------------------
6.1.5. /lib64 and /lib32 : 64/32-bit libraries (architecture
dependent)

The 64-bit architectures PPC64, s390x, sparc64 and AMD64 must place
64-bit libraries in /lib64, and 32-bit (or 31-bit on s390) libraries
in /lib.

The 64-bit architecture IA64 must place 64-bit libraries in /lib.
----------------------------------------------------------

I'm not offering this to help decide the matter, but it may imply
previous work on *nix systems. I'm not experienced in the area and I
can't offer anything helpful, regarding the confounding issue of
windows loading behavior, but I did see something upthread suggesting
that /lib64 may be in murky FHS waters.

I'm very reluctant to offer ideas; this exercise seems like juggling
chainsaws. It seems like a scheme to distinguish architecture's is a
helpful step towards the long term. Today's engineering pace makes it
likely that we will be facing similar predicaments in the not too
distant future.



More information about the Cygwin-developers mailing list