Your message dated Sat, 19 Dec 2015 10:59:06 +0000
with message-id <[email protected]>
and subject line Bug#808174: fixed in jemalloc 3.6.0-7
has caused the Debian Bug report #808174,
regarding jemalloc FTCBFS for {hur,kfreebs}d-i386 m68k sparc{,64}: mistakes
build architecture for host architecture
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.)
--
808174: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808174
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: jemalloc
Version: 3.6.0-5
Tags: patch
User: [email protected]
Usertags: rebootstrap
Dear jemalloc maintainer,
Even after fixing #807532, jemalloc still doesn't cross well for all
architectures. The reason for this is that the architecture-specific
quirks are misdetected.
debian/rules says e.g.:
| ifneq (,$(findstring $(DEB_BUILD_ARCH),sparc sparc64))
| DEB_CPPFLAGS_MAINT_APPEND += -DLG_QUANTUM=4
| endif
What this means is that when I am building on a sparc box (for whatever
architecture), then add the cppflag. Conversely, when building for sparc
on an amd64, it doesn't add the flag and the build fails.
The intention behind all of these checks is to match the architecture
that is being built for, which is called host architecture and not build
architecture.
The fix is simple:
sed -i s/DEB_BUILD_/DEB_HOST_/g debian/rules
Helmut
--- End Message ---
--- Begin Message ---
Source: jemalloc
Source-Version: 3.6.0-7
We believe that the bug you reported is fixed in the latest version of
jemalloc, 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.
Stig Sandbeck Mathisen <[email protected]> (supplier of updated jemalloc 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: Sat, 19 Dec 2015 10:22:35 +0100
Source: jemalloc
Binary: libjemalloc-dev libjemalloc1 libjemalloc1-dbg
Architecture: source
Version: 3.6.0-7
Distribution: unstable
Urgency: medium
Maintainer: Stig Sandbeck Mathisen <[email protected]>
Changed-By: Stig Sandbeck Mathisen <[email protected]>
Description:
libjemalloc-dev - development files and documentation for jemalloc
libjemalloc1 - general-purpose scalable concurrent malloc(3) implementation
libjemalloc1-dbg - debug symbols for jemalloc
Closes: 808174
Changes:
jemalloc (3.6.0-7) unstable; urgency=medium
.
* [6985721] Use DEB_HOST_* instead of DEB_BUILD_*
Thanks to Helmut Grohne (Closes: #808174)
Checksums-Sha1:
ebd2c0421a5a332db927a73ae660102450ba7457 2019 jemalloc_3.6.0-7.dsc
53499df6ee953f2affbd15ad8e1c96c6b9576ee8 10596 jemalloc_3.6.0-7.debian.tar.xz
Checksums-Sha256:
06aa2fbc8a430007defca61591af3c5752ae6555e6065a1e94d5c855e43d29ac 2019
jemalloc_3.6.0-7.dsc
8f993e1fd4bd6a0f4d29de1b17ba6c89fc89638977756a8c4c8f22a925f1ab75 10596
jemalloc_3.6.0-7.debian.tar.xz
Files:
6f31d59913e6257909463d872a0cfa9e 2019 libs extra jemalloc_3.6.0-7.dsc
f8863019cdc302e6ddced7d68c0790da 10596 libs extra
jemalloc_3.6.0-7.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCgAGBQJWdSnEAAoJEH26lYwcBVU4n+UP/iyIMQh4IIysJKBkF8HgK9tw
nCgYfpGQjwujgrAZJRKo8eDOy5EHAB/q/ar1dvfFdCU3nd07kQgdzQy3txRAmyXD
dgJCNn31IxAtjVTzfvDu1EI4At8wTZPTpFVHskxtSzB9uD/ABNTJCDqleBzadR8p
mM2rJ+2hydD6WlMe+WyXSUozaYqrGT73U+dqR1sMI0++gJ3a1LXcEtRNz4S4J+0l
nz7s6HgDrFKnO2NimGth16mSoYvxAsiq10P6KuQ9G7KMkh8JvdIBXHQs8lYbzwO5
dDoXfmW4HAGouSX8FoWSa0/gFMci1fXKvg4AvTEsGnkZayCVA3KKwgelHntlWVei
itw3bn7krTUqiCedEHPaegWKbG1RjEhQAuRYTUsxPzUbsTQqp+FgdjPkzn3HCPY8
GolGQ57l4WNKZkDbqR3zCip4xupdd4yW5UWn7Dp4TsxBsf67Sf+3h8736cTMLGMF
KEfb0q0Ngw4AJbE86v+PLCVU4jK3NUPGfPraykOIGfg3ZnbTekih9dYw81yx6xVL
0SfGsWSUfZsNxwXl4Xds4l+4YoXt2D8QiOWR3ZrfFODuloeHAte+lnI7x/NIPwad
VLDY+nTHIGM3tiZkqMNeJNhFELBLPYYktbjbEXzjPBlibNP0sgZjKbvs2OHlCSX8
tYGc587kGSMvPqWEL7mB
=bDE7
-----END PGP SIGNATURE-----
--- End Message ---
