Francois Gouget wrote:
> I work on an i386 Debian package which I compile on an amd64 host. I do this 
> by setting CC="gcc -m32" and calling 'dpkg-buildpackage -ai386' which gives 
> me binaries of the right type.
> But if I call dh_strip I get the following error:
> 
> + dh_strip
> Can't exec "i486-linux-gnu-strip": No such file or directory at 
> /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 215.
> dh_strip: i486-linux-gnu-strip --remove-section=.comment 
> --remove-section=.note debian/teststrip/usr/bin/hello failed to to execute: 
> No such file or directory
> dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 
> 2
> 
> 
> I checked in Debian's package archive and none of the packages installs an 
> '*-linux-gnu-strip' file. So dh_strip's expectations that it can find such a 
> file seem mistaken. Besides plain old 'strip' works just fine in this case.
> 
> I have uploaded a test package to:
> http://fgouget.free.fr/bugs/teststrip_1.0-1.tar.gz
> 
> To reproduce this bug just run './build' in the teststrip-1.0 directory on an 
> amd64 system that has the gcc-multilib package.

All that dh_strip knows is that dpkg-architecture is returning
values that indicate there is cross compilation in process,
and that prefixing the command with DEB_HOST_GNU_TYPE
is the standard way to get a program that is capable of handling this.

You may have a bug in dpkg-dev here, I don't know.

-- 
see shy jo

Attachment: signature.asc
Description: Digital signature

Reply via email to