Re: /usr/lib64?? (was: Re: [xml] Patch: installing Python into actual site-packages)

[Sander Vesik <Sander Vesik Sun COM>]

On Tue, 13 May 2003, Sean Middleditch wrote:

> On Tue, 2003-05-13 at 19:37, Sean Chittenden wrote:
>
> > Libraries for the native OS _should_ reside in /usr/lib.  Libraries
> > for non-native binaries _should_ exist in either /usr/compat/[arch] or
> > /usr/local/compat/[arch], where arch == freebsd_amd64, freebsd_ia64,
> > linux_ia32, etc.
>
> x86/IA32 binaries _are_ native to AMD64.  /usr/compat is the wrong
> place.

It would be slightly more correct to say that x86-64 provides hardware
emulation for a subset of ia32. Consider vm86 for example. So do really
also IA64 (aka itanium) processors, ia32 support in it is a hardware
feature and part of the architecture definition. By this logic, the
default should also be 32bit ia32 libs in $prefix/lib on ia64 aswell. 

There is no valid reason to think x86-64 processors will not run ia32 code
at a considerably slower speed than x86-64 code in 5 years time as a
combination of compilers and the larger scope of OoO possible.

> -- 
> Sean Middleditch <elanthis awesomeplay com>
> AwesomePlay Productions, Inc.

        Sander

        Humans love to categorize and organize things. We break up time into
        hours, days and years. Everything has to have a name, a history, an
        understanding of it's origins and must be indexed somewhere on Google.