Your message dated Wed, 4 Jan 2017 06:44:55 +0100
with message-id <[email protected]>
and subject line Re: Bug#837302: cross build produces broken packages
containing build architecture ELF objects
has caused the Debian Bug report #837302,
regarding cross build produces broken packages containing build architecture
ELF objects
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
837302: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837302
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: liblockfile
Version: 1.09-6
Tags: patch
User: [email protected]
Usertags: rebootstrap
liblockfile cross builds supposedly successfully, but the resulting
packages contain build architecture ELF executables. Switching to host
architecture triplet prefixed tools fixes that. Please consider applying
the attached patch.
Helmut
diff --minimal -Nru liblockfile-1.09/debian/changelog
liblockfile-1.09/debian/changelog
--- liblockfile-1.09/debian/changelog 2013-06-02 11:46:21.000000000 +0200
+++ liblockfile-1.09/debian/changelog 2016-09-10 14:11:56.000000000 +0200
@@ -1,3 +1,10 @@
+liblockfile (1.09-6.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix cross build: Use triplet prefixed tools. Closes: #-1
+
+ -- Helmut Grohne <[email protected]> Sat, 10 Sep 2016 14:05:43 +0200
+
liblockfile (1.09-6) unstable; urgency=low
* Merge 1.09-5ubuntu1
diff --minimal -Nru liblockfile-1.09/debian/rules liblockfile-1.09/debian/rules
--- liblockfile-1.09/debian/rules 2012-06-13 13:26:39.000000000 +0200
+++ liblockfile-1.09/debian/rules 2016-09-10 14:08:45.000000000 +0200
@@ -4,6 +4,10 @@
#export DEB_BUILD_MAINT_OPTIONS = hardening=+all
DPKG_EXPORT_BUILDFLAGS = 1
include /usr/share/dpkg/buildflags.mk
+include /usr/share/dpkg/architecture.mk
+ifeq ($(origin CC),default)
+CC = $(DEB_HOST_GNU_TYPE)-gcc
+endif
# liblockfile
MVER = 1
@@ -15,11 +19,9 @@
INSTALL=install
ifeq (,$(findstring nostrip,$(DEB_BUILD_OPTIONS)))
- INSTALL+=-s
+ INSTALL+=-s --strip-program=$(DEB_HOST_GNU_TYPE)-strip
endif
-DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH)
-
build-arch: config.status
$(checkdir)
make
@@ -28,7 +30,7 @@
build-indep:
config.status:
- ./configure --enable-shared --prefix=/usr \
+ CC=$(CC) ./configure --enable-shared --prefix=/usr \
--libdir=\$${prefix}/lib/$(DEB_HOST_MULTIARCH) \
--with-mailgroup --mandir=/usr/share/man
--- End Message ---
--- Begin Message ---
Version: 1.11-1
On Tue, Jan 03, 2017 at 10:56:26PM +0100, Miquel van Smoorenburg wrote:
> I've just uploaded liblockfile 1.11 to unstable- that should fix this bug.
> Can you check?
Works. Thanks.
For cross build bugs, I slightly prefer you just closing them when you
have made reasonable effort to fix them, because my QA infrastructure
will then automatically retest them and reopening when necessary is
trivial.
Helmut
--- End Message ---
