On Tuesday 09 May 2006 19:11, Michael Biebl wrote: > dragoran wrote: > > Hello > > I have changed the default dirs on x86_64 to /lib64 because the FHS > > standard[1] say so and /lib has problems when building rpms on 64 bit > > systems (it searches for files in /lib64 that do not exists). > > This has been reverted [2] because it causes more problems that it > > solved... Which kind of problems does it cause? Wouldn't it be better to > > solve this problem instead of using such hacks? > > 1: http://www.pathname.com/fhs/pub/fhs-2.3.html#LIB64 > > 2: http://www.initng.org/changeset/4082 > > If you read the IRC log from tonight, you will see that matteo started > the discussion, because his build broke (or rather the deb package > generation) on a Debian AMD64 bit machine. > I can't comment on this issue that much, because I don't own a > AMD64/64bit machine. > The problem is, I guess, every distro handles it a bit different. > As matteo told me, on his (pure) AMD64 Debian platform, /lib64 is simply > a link to /lib. > Other distros have a /lib64 directory for 64bit libs and /lib for 32bit > libs, others put the 64bit libs into /lib, 32bit libs into /lib32. > If we could come up with a list, how the different distros handle these > paths (IIRC there is also the distinction between pure an mixed 32/64 > platforms) that would help a lot. please note that not all 64bit systems have it as /lib64. quoting from the FHS link given earlier:
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. anyway, giving up a list of different distros is pointless. there just should be way to specify (on commandline) the correct lib dir if autodetected is not correct one. why make it complicated with autodetection, on what not everybody will agree what is right and what is wrong. > Does anyone know how autoconf handles this issue? in autoconf you can pass --with-libdir=/lib64 > Cheers, > Michael -- glen -- _______________________________________________ Initng mailing list [email protected] http://jw.dyndns.org/mailman/listinfo/initng
