Bug#774356: marked as done (stage2 powerpc multilib wdotap build fails)
Your message dated Fri, 24 Apr 2015 01:48:29 +0000
with message-id <E1YlSjF-00041s-Tj@franck.debian.org>
and subject line Bug#774356: fixed in cross-gcc-4.9-armhf 15
has caused the Debian Bug report #774356,
regarding stage2 powerpc multilib wdotap build fails
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 owner@bugs.debian.org
immediately.)
--
774356: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774356
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: cross-gcc-dev
Version: 11
User: helmutg@debian.org
Usertags: rebootstrap
A wdotap stage2 cross build from amd64 targeting powerpc with multilib
fails. The tail of the log[1] is:
| : # ppc 64bit build slaps libgcc and libstdc++ to powerpc64-linux-gnu
| mkdir -p debian/tmp/usr/powerpc-linux-gnu/lib64
| cp -a debian/tmp/usr/powerpc64-linux-gnu/lib64/* debian/tmp/usr/powerpc-linux-gnu/lib64/
| cp: cannot stat 'debian/tmp/usr/powerpc64-linux-gnu/lib64/*': No such file or directory
| debian/rules2:2060: recipe for target 'stamps/07-install-stamp' failed
| make[1]: *** [stamps/07-install-stamp] Error 1
| make[1]: Leaving directory '/tmp/buildd/gcc2/gcc-4.9-4.9.2'
| debian/rules:80: recipe for target 'stamps/07-install-stamp' failed
The remainder of the build log tells that this is the first mention of
"powerpc64-linux-gnu/lib64". Instead the files mentioned are installed
in the intended location (where they would be copied to).
So I attempted a build with the same configuration except for disabling
wdotap (i.e. using the supported method) and indeed the supported method
does not fail here. This is why I am filing the bug against
cross-gcc-dev.
The relevant code can be found in gcc-4.9's debian/rules2[2] (search for
"slaps"). It is conditional to:
* DEB_CROSS = yes
* multilib = yes
* DEB_STAGE != stage1
* DEB_TARGET_ARCH = powerpc
* biarch64 = yes
Likely, this should also become conditional to
with_deps_on_target_arch_pkgs != yes. The interesting bit here is that
there is similar fix above this fix for DEB_TARGET_ARCH=s390. It is not
clear whether it should also be disabled for wdotap. In particular, this
cannot be tested, because glibc no longer builds for s390, so we cannot
satisfy Build-Depends.
What do you think? Opportunistically disable both or just the one we
know to be unneeded for wdotap? (Based on this description either patch
should be trivial.)
Helmut
[1] https://jenkins.debian.net/job/rebootstrap_powerpc_gcc49/96/console
[2] http://sources.debian.net/src/gcc-4.9/4.9.2-10/debian/rules2/#L2184
--- End Message ---
--- Begin Message ---
Source: cross-gcc-4.9-armhf
Source-Version: 15
We believe that the bug you reported is fixed in the latest version of
cross-gcc-4.9-armhf, 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 774356@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Wookey <wookey@debian.org> (supplier of updated cross-gcc-4.9-armhf 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 ftpmaster@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Tue, 21 Apr 2015 03:49:02 +0100
Source: cross-gcc-4.9-armhf
Binary: cpp-4.9-arm-linux-gnueabihf gcc-4.9-arm-linux-gnueabihf g++-4.9-arm-linux-gnueabihf gfortran-4.9-arm-linux-gnueabihf
Architecture: source
Version: 15
Distribution: experimental
Urgency: medium
Maintainer: Debian Cross-Toolchain Team <debian-toolchain@lists.debian.org>
Changed-By: Wookey <wookey@debian.org>
Description:
cpp-4.9-arm-linux-gnueabihf - Cross-gcc (cpp) targetting armhf
g++-4.9-arm-linux-gnueabihf - Cross-gcc (g++) targetting armhf
gcc-4.9-arm-linux-gnueabihf - Cross-gcc (gcc) targetting armhf
gfortran-4.9-arm-linux-gnueabihf - Cross-gcc (gfortran) targetting armhf
Closes: 774356 779322
Changes:
cross-gcc-4.9-armhf (15) experimental; urgency=medium
.
[ Wookey ]
* Enable config for multilib/non-multilib builds
* Build tools for i386 as well (Closes: #779322)
.
[ Dima Kogan ]
* rebuild for 4.9.2-12, 5-20150404-1
* building cross-compiler targeting i386
* fix powerpc multilib stage2 build. (Closes: #774356)
* cross-gcc-dev Depends lsb-release. gcc builds use this
Checksums-Sha1:
cb6c3326290d09dce9d5171a6c014ad21279a028 1979 cross-gcc-4.9-armhf_15.dsc
c5996518a91ccc7a3696db25acf2f29c92f32d18 3364 cross-gcc-4.9-armhf_15.tar.xz
Checksums-Sha256:
abfdcbb9360cca8c71328a4f308c3631e2f82394d66d3f45afb4466b261eab77 1979 cross-gcc-4.9-armhf_15.dsc
36840ecb02e25f5f77e32a380e358b81241d2ce79b3992f4f8d05702fccb018c 3364 cross-gcc-4.9-armhf_15.tar.xz
Files:
0f081e580a22288c189227d1e9f78cba 1979 devel extra cross-gcc-4.9-armhf_15.dsc
f294e95e8bc22f3e2f61eff18c49fc0b 3364 devel extra cross-gcc-4.9-armhf_15.tar.xz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJVOZ9xAAoJEADolDnyKCkrh+UIAIvgr+DrGOzcJtUCq/QjdQfR
cWgYUXVV59F6FQh+2EtYY1VNl+L7k5dG1V+8srlG4TgWY73TzunOJ8duRVLa6rKg
mjef3zbm4yBYgY4rXqeUWLSweDMRSBXhbr+RmM4VPnIoMOP5Zv+j/kxzcP6X2Gby
7ApS1HoV7sJKC37uXr6jECkeJRnoRmri7SxNpmogE2nQ0DHqSxH6YgSZm5eGrBIR
lJ+ZcoB5ci2XV6Y7bkdWm+UlYuK8vgywCmY1hQUJOSxXczxoIHP8eVWDsEELFhEJ
ioNAFvmUW9w4mDFl9AA2islKh37X5XnxbYyWvNUrjbzh9AXJsGa/jW/zANKSjO4=
=BuH1
-----END PGP SIGNATURE-----
--- End Message ---
Reply to: