Package: bzip2
Version: 1.0.3-7
Severity: normal
Formerly, dpkg-cross overwrote MAKEFLAGS during cross-builds so that
even if debian/rules specifies CC=gcc, the cross-build would use
CC=arm-linux-gnu-gcc etc. This behaviour was actually buggy in that it
prevented packages from using CC_FOR_BUILD correctly when internal tools
needed to be compiled during the build using the build compiler instead
of the cross-compiler.
The 2.0.0 rewrite of dpkg-cross has therefore removed the MAKEFLAGS
override to restore CC_FOR_BUILD functionality and to make it easier to
merge dpkg-cross back into dpkg and remove the old diversions. v2.0.0 is
due to be uploaded once support is enabled in dpkg. (v2.0.0 depends on
binutils-multiarch to reduce problems with strip, ranlib etc.)
bzip2 (like zlib) relied on the old behaviour to cross-build
successfully and now tries to cross-build using gcc instead of
arm-linux-gnu-gcc etc. because it does not detect a cross-build.
As bzip2 has no configure script, I need to know how you would me to
approach creating a patch for bzip2.
My initial approach is:
ifneq ($(DEB_HOST_GNU_TYPE),$(DEB_BUILD_GNU_TYPE))
CROSS += "CC=$(DEB_HOST_GNU_TYPE)-gcc"
else
CROSS += "gcc"
endif
Then using $(CROSS) where 'gcc' or $(MAKE) is used in debian/rules, in a similar
manner to how bzip2 already handles CC64.
bzip2 already avoids running the test suite if cross-compiling, would
this approach be suitable for bzip2?
If so, I can prepare a patch.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.22-2-amd64 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages bzip2 depends on:
ii libbz2-1.0 1.0.3-7 high-quality block-sorting file co
bzip2 recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
