I have two binary packages (one already in Debian - pilot-qof - and one still in development called cashutil) that previously built successfully on amd64. Each package still builds successfully (i.e. no lintian or linda errors) on powerpc and i386. Test packages are available from here: deb http://www.linux.codehelp.co.uk/ packages/unstable/$(ARCH)/ deb-src http://www.linux.codehelp.co.uk/ packages/unstable/$(ARCH)/ The repository includes binary packages for the three architectures: i386, powerpc and amd64 as well as source. However, a recent upgrade (I suspect to libtool or gcc) on amd64 has meant that I now get architecture-specific lintian errors involving rpath <groan>: $ lintian pilot-qof_0.0.10-1_amd64.deb W: pilot-qof: binary-or-shlib-defines-rpath ./usr/bin/pilot-qof /usr/lib64 $ lintian pilot-qof_0.0.10-1_i386.deb linda also complains: $ linda pilot-qof_0.0.10-1_amd64.deb W: pilot-qof; Binary /usr/bin/pilot-qof compiled with an RPATH of /usr/lib64. $ linda pilot-qof_0.0.10-1_i386.deb When I observe the build, an rpath setting of /usr/lib64 *is* being added via libtool. It appears nowhere else in the tree: $ grep lib64 * libtool:predep_objects="/usr/lib/gcc/x86_64-linux-gnu/4.1.2/../../../../lib64/crti.o /usr/lib/gcc/x86_64-linux-gnu/4.1.2/crtbeginS.o" libtool:postdep_objects="/usr/lib/gcc/x86_64-linux-gnu/4.1.2/crtendS.o /usr/lib/gcc/x86_64-linux-gnu/4.1.2/../../../../lib64/crtn.o" libtool:compiler_lib_search_path="-L/usr/lib/gcc/x86_64-linux-gnu/4.1.2 -L/usr/lib/gcc/x86_64-linux-gnu/4.1.2 -L/usr/lib/gcc/x86_64-linux-gnu/4.1.2/../../../../lib64 -L/lib/../lib64 -L/usr/lib/../lib64" I want to develop on amd64 primarily (because it's a faster desktop machine) - is this a bug in libtool? Can both lintian AND linda overrides be architecture-specific? Should I include a patch for libtool that tries to remove -L/usr/lib/../lib64 or just remove the /../lib64 component? Right now, /usr/lib64/ appears to be the same as /usr/lib/ - is this a transition that lintian doesn't know about? I am the upstream developer for both packages - how can I ensure that --disable-rpath is actually implemented in the upstream code? I'd rather not just fix this in the Debian packages unless it is a Debian-specific issue. -- Neil Williams ============= http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/
Attachment:
signature.asc
Description: OpenPGP digital signature