Paul Martin wrote: > On Wed, Jun 21, 2006 at 11:33:36AM +0100, Neil Williams wrote: >> Package: libpopt-dev >> Version: 1.10-2 >> Severity: important >> >> This reflects an earlier bug in libffi3: #268152 - libpopt-dev includes >> libpopt.la which refers to /usr/lib64 on amd64. This non-standard >> directory then causes packages built against libpopt-dev on amd64 to >> refer to /usr/lib64 via libtool and generate spurious --rpath usage. >> Packages built this way then generate lintian and linda errors related >> to --rpath usage in the resulting binaries. > > You can blame [expletive] autoconf for this one. Libraries built using > that prefer to use lib64 as the name of the libdir. >
I disagree. I'm building libqof1 on amd64 using autoconf and libqof.la does not refer to lib64 in any way. The line in libpopt.la that is referenced above contains usr/lib in libqof.la, built on amd64 using autoconf. I haven't done anything special to avoid lib64 in this build - which is why it was such a surprise to find it in packages that use libpopt-dev. I've got test packages if you want to check. deb http://www.linux.codehelp.co.uk/ packages/unstable/$(ARCH)/ deb-src http://www.linux.codehelp.co.uk/ packages/unstable/source/ The *only* library on amd64 that refers to lib64 is libpopt-dev. You cannot blame autoconf for that one. -- Neil Williams ============= http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/
signature.asc
Description: OpenPGP digital signature
