Jesse Becker wrote: > On Wed, Feb 10, 2010 at 12:02, Daniel Pocock <dan...@pocock.com.au> wrote: > >> Jesse Becker wrote: >> >>> On Wed, Feb 10, 2010 at 11:32, Daniel Pocock <dan...@pocock.com.au> wrote: >>> >>> >>>> A while back, I introduced a patch to configure.in that determines >>>> whether or not lib directories should be called lib or lib64 >>>> >>>> This is needed when trying to find things like libconfuse >>>> >>>> lib64 is not a universal phenomenon though - it is not the norm on Debian. >>>> >>>> However, I note that the Linux FHS does mandate lib64, >>>> >>>> >>> I must admit I find this amusing. :-) >>> >>> >>> >>>> http://www.pathname.com/fhs/pub/fhs-2.3.html#LIB64 >>>> >>>> so I may reverse the logic, the new logic will be to use lib64 on any >>>> x86_64-*-linux except for those on an exception list (e.g. Debian) >>>> >>>> >>> +1 from me. Using lib64 for 64bit libs is certainly the expected >>> behavior for the various Red Hat derived distributions. >>> >>> >>> >> Actually, the FHS does go further though: >> >> - on many other architectures, lib64 is also expected, e.g. PPC64, >> s390x, sparc64 >> >> - however, on ia64, lib64 should NOT be used (what does RHEL do on ia64?) >> > > I'm not sure (but may be able to find out if it really matters). I > *suspect* that it just uses /lib. On ia64 systems, there is no (or > at least "less") expectation of ever running 32bit code. Yes, yes, > there are emulators and such, but that is a special case. This is as > opposed to x86_64 systems where there is both the ability and > expectation that 32bit and 64bit code will coexist. > > >> Maybe a specific autoconf macro is needed to encapsulate the FHS >> requirements and the real-world variations between platforms. >> > > Possibly. I would not be surprised if something like this already > exists; we can't be the first project to deal with this problem. > > > I decided to ask about this on the autoc...@gnu.org list - the reply came very quickly
- they don't think configure should worry about lib64, - the solution is for the user to set LDFLAGS explicitly on the configure command line (e.g. LDFLAGS=/opt/confuse-2.6/lib64 ./configure) Reading over the autoconf manual, it suggests that --with is only for turning libraries on and off (e.g. to build without pcre support). It does not give any example of passing a path to the --with parameter. http://www.gnu.org/software/autoconf/manual/autoconf.html#External-Software Maybe we need to strip out all of this stuff, perhaps just for trunk? ------------------------------------------------------------------------------ SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev _______________________________________________ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
