Your message dated Tue, 25 Aug 2015 18:50:12 +0000
with message-id <[email protected]>
and subject line Bug#796886: fixed in libcap2 1:2.24-11
has caused the Debian Bug report #796886,
regarding FTCBFS: links -lattr with build arch compiler but does not 
Build-Depends: libattr-dev:native
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.)


-- 
796886: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796886
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: libcap2
Version: 1:2.24-10
Tags: patch
User: [email protected]
Usertags: rebootstrap

The 1:2.24-10 upload introduced a regression with cross building. (I
accidentally deleted the build log, sorry.) At some point it compiles
_makenames.c with $(BUILD_CC) (which is correct), but it now passes
$(LDFLAGS) which can only be used for the host architecture compiler.
Since $(LDFLAGS) contains -lattr linking fails.

The attached patch resolves that problem by replacing LDFLAGS with
BUILD_LDFLAGS in this case. Note that BUILD_LDFLAGS is never set, so
this is equivalent to removing LDFLAGS. It will of course regress in
terms of blhc and you will receive a (wrong) report of missing
hardening. If you wish to avoid that as well, you can set

export BUILD_LDFLAGS=$(shell dpkg-architecture -a$(DEB_BUILD_ARCH) -c 
dpkg-buildflags --get LDFLAGS)

and the CPPFLAGS counterpart in debian/rules.

In general, one must not reuse any host architecture build flags for
build architecture compiler invocations, because build flags can differ
per architecture. In particular, host architecture build flags can be
unrecognized by the build architecture compiler (e.g. amd64 vs alpha).

Please consider applying the patch or a variant of it.

Helmut
--- a/debian/patches/0004-Don-t-hardcode-build-flags.patch
+++ b/debian/patches/0004-Don-t-hardcode-build-flags.patch
@@ -46,7 +46,7 @@
  
  _makenames: _makenames.c cap_names.list.h
 -	$(BUILD_CC) $(BUILD_CFLAGS) $< -o $@
-+	$(BUILD_CC) $(BUILD_CFLAGS) $(LDFLAGS) $(CPPFLAGS) $< -o $@
++	$(BUILD_CC) $(BUILD_CFLAGS) $(BUILD_LDFLAGS) $(BUILD_CPPFLAGS) $< -o $@
  
  cap_names.h: _makenames
  	./_makenames > cap_names.h

--- End Message ---
--- Begin Message ---
Source: libcap2
Source-Version: 1:2.24-11

We believe that the bug you reported is fixed in the latest version of
libcap2, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Christian Kastner <[email protected]> (supplier of updated libcap2 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Tue, 25 Aug 2015 20:40:33 +0200
Source: libcap2
Binary: libcap2-bin libcap2 libcap2-dbg libcap-dev libpam-cap libcap2-udeb
Architecture: source
Version: 1:2.24-11
Distribution: unstable
Urgency: medium
Maintainer: Christian Kastner <[email protected]>
Changed-By: Christian Kastner <[email protected]>
Description:
 libcap-dev - POSIX 1003.1e capabilities (development)
 libcap2    - POSIX 1003.1e capabilities (library)
 libcap2-bin - POSIX 1003.1e capabilities (utilities)
 libcap2-dbg - POSIX 1003.1e capabilities (debug)
 libcap2-udeb - POSIX 1003.1e capabilities (library) (udeb)
 libpam-cap - POSIX 1003.1e capabilities (PAM module)
Closes: 796886
Changes:
 libcap2 (1:2.24-11) unstable; urgency=medium
 .
   * d/rules:
     - Provide BUILD_LDFLAGS and BUILD_CPPFLAGS. Thanks, Helmut Grohne!
   * d/patches:
     - Drop patch numbers from .patch filenames
   * d/patches (updated):
     - Don-t-hardcode-build-flags.patch
       When using BUILD_CC, use BUILD_LDFLAGS and BUILD_CPPFLAGS instead of the
       host ones. Thanks, Helmut Grohne! Closes: #796886
   * Add package-specific d/gbp.conf
Checksums-Sha1:
 03cc016d0dc07897790a3bf7301ca6393d0ba74f 2211 libcap2_2.24-11.dsc
 8a869e9c8491dab7b549922c950476354cb77297 18744 libcap2_2.24-11.debian.tar.xz
Checksums-Sha256:
 6729d954f9566b71eff567a523f053954244e1f68bace1a12fc3ed37b9fb93ec 2211 
libcap2_2.24-11.dsc
 81e4fd2be49778a2b4575b77e5387e05bd7b1f9a5e087fa08aef6fe6b1e8b141 18744 
libcap2_2.24-11.debian.tar.xz
Files:
 5456c4afbb3fc45c4e6a37ebc2a2f720 2211 libs optional libcap2_2.24-11.dsc
 9028e1bfa0a086d8b3945904196d1514 18744 libs optional 
libcap2_2.24-11.debian.tar.xz

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCgAGBQJV3LceAAoJEDmVOjfeTrNrO8kQAIdN1HR5w57d/VghT3JOe9Fy
r2YZOo3Pv1CzwI9QJbFEEWCtw/sqJUq5xHEwSHMrLnOlxO9A2jdOvDbWrPxeHIB9
uAkjSex45VYk64iszlfEogpJk4sp3aUJweUeSeKVTUhQ7p9KDKnPF2n1OUYip3oP
4brnQLfiREbDD2TGE10YOa4V9VM/R2/XaGxEbnXrdilbzNjCTADJOEVhdDMkjPi8
ZHenHlPPzVMTQ13ITT2HlTHI0qNFB0YpBRAzHBTKXeI6IcynFnGRfK/DkCdsk8kB
Z+mqd1duoiuFnjUmTpyBcbUMv7fHNqkaHSdKU+EJCs0/hFugiydAxbmhebaNnLSX
atNyFpBwkoM8Qsz/N2x003hh7sUkSN49T4+xsZ7fCrJRsPCsV/Hc6vn3y3nsoTLb
chYgJzYO0B5sAbBHrK33F3UDSw/9gDXhaVk5Cf0ddSkh/AC8Y4eYSr6t2dpI+JZK
ZhkMKjtOGaXezb+9NPVaMsSTVKEcYD5HyllpT0JlPBfisi3qQx5EOgnQlcUPtI9n
5XYZN0ndaq8q3skSPJCN6yae25U9Pw0sVV6JRnIx2u8napGtgYpAUVM+MShZNuHx
jy0wgkzX4rwXT+zX9aaL0tOMJAbasNa1YOF16B4ZNiyX3ry1KOJ/EMaAMGZIlk/U
N2wcYjnYPpLFLspQl9zv
=bbnW
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to