Actually I think we should submit an entry to lsb to change this they way gentoo does it is better... this is different to other 64bit archs (the main reason why lsb want to keep it is because all other 64bit archs reside in lib64)... I've talked about this before and I'm adamant that gentoo has it right... and lsb wrong.
reasons: a)amd64 platform runs 32bit libs natively: without clear seperation to both configure environments and the user you get interferrance b)Fundementally I think that the LSB reasoning to have lib64 as 64bit only is unclear and unreasonable... if anything lib should be the native libs for that arch (whatever it may be), why do 64bit archs get treated differently according to lsb? no clear reason, other arch (i.e ppc/arm) get lib still as the default... c)In Distros following LSB (i.e suse redhat) on amd64 platform you get all sorts of headaches with incorrect(outdated) automake environment and configure scripts getting default location wrong (i.e picking up on 32bit target dirs/ or 64bit (if compiling against ix86 target). My $0.02 Kind regards Joel W > Eventually, with 2005.1 or perhaps later, the goal is to have 64-bit libs > in lib64, with 32-bit libs in the old lib. That's what the LSB is calling > for and what pretty much every other distribution with an amd64 port is > doing. -- [email protected] mailing list
