Hi Joey,
Joey Hess wrote:
>> when doing a cross build (with DEB_HOST_* suitably defined), compilation
>> fails when dh_strip uses the regular "strip" command instead of the host
>> prefixed one.
>> Could dh_strip be taught to use ${DEB_HOST_GNU_TYPE}-strip if
>> ${DEB_BUILD_ARCH} differs from ${DEB_HOST_ARCH}?
> This has been requested before, and it seems to me better to use
> binutils-multiarch, since this will get you a strip that works for cross
> compiling for the many packages that have install -s etc in their
> makefiles.
This makes the build depend on binutils-multiarch even though I have a
proper toolchain for the target installed and also requires that
binutils-multiarch is able to handle the desired target architecture.
Having binutils-multiarch installed hides problems with other places of
the build process; when I do upstream work I'd like the build scripts to
fail if a place where a native instead of a cross tool is used slips
through my fingers.
In one case I have a toolchain that builds bFLT binaries directly (the
compiler's specs file knows to call elf2flt after the final link); those
cannot be further postprocessed by binutils, however I have a "strip"
script in place that knows how to handle bFLT binaries.
Simon
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
