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

[Sean Chittenden <sean chittenden org>]

> > breaks the contract between the OS and the programmer to have a
> > different path for 64bit vs 32bit libraries.  ::grump::
>
>   because the OS can run both 32 and 64 bit binaries. See 
>
> http://www.x86-64.org/lists/discuss/msg02662.html
>
>   and associated stuff at the LSB,

'Ya know, for just a few minutes every month, I wish the folks doing
standards and architecture work in the Linux would be slightly more
competent than the run of the mill bottom rung, burger flipping, VB
programmer.

> Daniel
>
> P.S.: do not blame me, thanks !

I'm not, but it's frustrating to have to deal with brain dead
linux-isms when supporting libraries that run on that OS.  Thanks for
the URL and sorry for the OT post.

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.

-sc

-- 
Sean Chittenden