[M3devel] [m3devel] Packaged AMD64_LINUX for debian

[Dragiša Durić]

Very good question,

http://proton.pathname.com/fhs/pub/fhs-2.3.html#LIB64 sez:

/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. 

                Tip
Rationale
 
This is a refinement of the general
rules for /lib<qual>
and /usr/lib<qual>. The
architectures PPC64, s390x, sparc64
and AMD64 support support both
32-bit (for s390 more precise
31-bit) and 64-bit programs. Using
lib for 32-bit binaries allows
existing binaries from the 32-bit
systems to work without any changes:
such binaries are expected to be
numerous. IA-64 uses a different
scheme, reflecting the deprecation
of 32-bit binaries (and hence
libraries) on that architecture.



On Thu, 2009-05-28 at 00:35 +0000, Jay wrote:
> > One issue with how-cm3-does-it is, IMO,
> > /usr/local/cm3/lib directory...It must be lib64 on AMD64_LINUX
>  
>  
> Is this always true or only sometimes?
> Are there "pure" 64bit systems?
> Should be if exist or unconditional?
> Also, do you know about hypothetical PPC64_LINUX, MIP64_LINUX,
> SPARC64_LINUX?
> (I only have sparc64 running so far.)
> That is, all 64bit Linux or only AMD64?
-- 
Dragiša Durić <dragisha at m3w.org>