Re: Bug#766708: Processed: Re: Bug#766708: breaks multiarch cross building
On Mon, Oct 27, 2014 at 09:41:59PM +, Ian Jackson wrote: The most obvious bug is the one mentioned in the patch: #760770 It is about a bug in the implementation of with_deps_on_target_arch (the contended feature). I think I may not understand what's going on here. In your mail to the TC, you say: it was possible to build a gcc cross compiler with different properties from the default build by setting with_deps_on_target_arch_pkgs=yes and DEB_CROSS_NO_BIARCH=yes. You mean setting these as environment variables ? If so then it would seem that this feature has no direct effect on anyone who is not trying to use it. Is that correct ? It is correct, that builds that do not set these variables are not affected by it beyond also carrying it as dead code in the gcc packaging. Of course it does have a maintenance burden on the package maintainer, which is what Don is asking about. I have to admit that the code is not exactly lightweight. I do understand the desire to get rid it and asked that a ctte ruling does not apply beyond jessie for that reason. #760770 shows an element of that but it is immediately obvious from the initial report that something odd is going on and it contains a link to #720363 which mentions Oh, my previous bug research has missed gcc-4.8 bugs. https://wiki.debian.org/MultiarchCrossToolchainBuild which talks abouit the with_deps_on_target_arch_pkgs feature. It doesn't appear that #760770 has taken a great deal of Matthias's time, although it did necessitate some bug triage. One of the issues here is that the submitter wasn't explicit about using the non-default build here. It only surfaced in message 19 and can be spotted from looking at the patch. When being asked to do a self-contained cross build (and the self-contained kinda implies not using with_deps_on_target_arch_pkgs), a log with the alternative build method is sent back. Are the maintainers of the disputed features subscribed to the appropriate packages in the PTS ? Does Matthias welcome help triaging I am not subscribed yet. The major reason is that I did not perceive the maintenance of the feature as a problem until Matthias stated it in this bug. It is certainly fixable. these bugs ? It seems to me that it would be easy to come up with a workflow that allowed Matthias to usertag these kind of bugs and hand them over to the cross teams. Sounds reasonable to me. Asking Wookey whether he would like to share that work. What are the cross-gcc-4.9-armhf packages that are referred to ? It is a source package that uses the gcc-4.9-source binary package from the gcc-4.9 source package to build a cross compiler targeting armhf. In GNU terminology that is build=host=amd64, target=armhf. The packaging is thin compared to the gcc-4.9 packaging and its goal is to enable people to just apt-get install cross toolchains rather than building them each time they need them. (I am not a maintainer of cross-gcc-4.9-*.) Judging from the replies, I would like to repeat the timing argument here: The mechanism being discussed was disabled in gcc-4.9 without any advance notice or discussion[1]. The code for supporting the default method in glibc has not yet arrived in the Debian glibc package or the BTS, but Matthias indicated that he would be working on that and he seems to make progress outside Debian. I am not opposed to using the default build method for bootstrapping new Debian architectures in principle, but in my experience it takes a long time to merge patches into the glibc packaging and the freeze is certainly not accelerating that process. I am not opposed to disabled with_deps_on_target_arch_pkgs in general, just now is the wrong time, because it is impossible to get the corresponding functionality to gcc's default cross build into glibc. Most of the changes necessary to make the alternative method work with glibc have been merged however: #743676 #754350 #756095 #742640 #745380 #752480 #755580 #756473 (but most of these changes are also necessary for the default method) Helmut [1] It is worth noting here that the upload of cross-gcc-4.9-* similarly lacked discussion. An advance notice to the gcc list or targeting experimental would have been better here. -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141028061340.ga22...@alf.mars
Bug#766174: Removed package(s) from unstable
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: libphobos-dev |4.9.1-4 | kfreebsd-amd64, kfreebsd-i386 --- Reason --- ROP; not built anymore -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. Bugs which have been reported against this package are not automatically removed from the Bug Tracking System. Please check all open bugs and close them or re-assign them to another package if the removed package was superseded by another one. The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 766...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/766174 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain) -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1xj9sx-0004s5...@franck.debian.org
Results for 4.9.1 (Debian/Linaro 4.9.1-19) testsuite on aarch64-unknown-linux-gnu
LAST_UPDATED: Thu Oct 23 15:53:25 UTC 2014 (revision 216594) Native configuration is aarch64-unknown-linux-gnu === boehm-gc tests === Running target unix === boehm-gc Summary for unix === # of expected passes12 # of unsupported tests 1 Running target unix/-fstack-protector === boehm-gc Summary for unix/-fstack-protector === # of expected passes12 # of unsupported tests 1 === boehm-gc Summary === # of expected passes24 # of unsupported tests 2 === libatomic tests === Running target unix === libatomic Summary for unix === # of expected passes54 Running target unix/-fstack-protector === libatomic Summary for unix/-fstack-protector === # of expected passes54 === libatomic Summary === # of expected passes108 === libffi tests === Running target unix === libffi Summary for unix === # of expected passes1819 # of unsupported tests 55 Running target unix/-fstack-protector === libffi Summary for unix/-fstack-protector === # of expected passes1819 # of unsupported tests 55 === libffi Summary === # of expected passes3638 # of unsupported tests 110 === libgo tests === Running target unix FAIL: math FAIL: time FAIL: crypto/tls FAIL: crypto/x509 === libgo Summary === # of expected passes118 # of unexpected failures4 /build/gcc-4.9-Kmy7Bt/gcc-4.9-4.9.1/build/./gcc/gccgo version 4.9.1 (Debian/Linaro 4.9.1-19) === libgomp tests === Running target unix WARNING: program timed out. FAIL: libgomp.graphite/force-parallel-6.c execution test === libgomp Summary for unix === # of expected passes3244 # of unexpected failures1 # of unsupported tests 36 Running target unix/-fstack-protector WARNING: program timed out. FAIL: libgomp.graphite/force-parallel-6.c execution test === libgomp Summary for unix/-fstack-protector === # of expected passes3244 # of unexpected failures1 # of unsupported tests 36 === libgomp Summary === # of expected passes6488 # of unexpected failures2 # of unsupported tests 72 === libitm tests === Running target unix === libitm Summary for unix === # of expected passes26 # of expected failures 3 # of unsupported tests 1 Running target unix/-fstack-protector === libitm Summary for unix/-fstack-protector === # of expected passes26 # of expected failures 3 # of unsupported tests 1 === libitm Summary === # of expected passes52 # of expected failures 6 # of unsupported tests 2 === libjava tests === Running target unix FAIL: Throw_2 execution - source compiled test FAIL: Throw_2 -findirect-dispatch execution - source compiled test FAIL: Throw_2 -O3 execution - source compiled test FAIL: Throw_2 -O3 -findirect-dispatch execution - source compiled test === libjava Summary for unix === # of expected passes2574 # of unexpected failures4 # of expected failures 4 # of untested testcases 4 Running target unix/-fstack-protector FAIL: Throw_2 execution - source compiled test FAIL: Throw_2 -findirect-dispatch execution - source compiled test FAIL: Throw_2 -O3 execution - source compiled test FAIL: Throw_2 -O3 -findirect-dispatch execution - source compiled test === libjava Summary for unix/-fstack-protector === # of expected passes2574 # of unexpected failures4 # of expected failures 4 # of untested testcases 4 === libjava Summary === # of expected passes5148 # of unexpected failures8 # of expected failures 8 # of untested testcases 8 === libstdc++ tests === Running target unix FAIL: 22_locale/numpunct/members/char/3.cc execution test FAIL: 22_locale/time_get/get_date/wchar_t/4.cc execution test === libstdc++ Summary for unix === # of expected passes9830 # of unexpected failures2 # of expected failures 41 # of unsupported tests 253 Running target unix/-fstack-protector FAIL: 22_locale/numpunct/members/char/3.cc execution test FAIL: 22_locale/time_get/get_date/wchar_t/4.cc execution test === libstdc++ Summary for unix/-fstack-protector === # of expected passes9830 # of unexpected failures2 # of expected failures 41 # of unsupported tests 253 === libstdc++
Results for 4.9.1 (Debian 4.9.1-19) testsuite on mipsel-unknown-linux-gnu
LAST_UPDATED: Thu Oct 23 15:53:25 UTC 2014 (revision 216594) Target: mipsel-linux-gnu gcc version 4.9.1 (Debian 4.9.1-19) Native configuration is mipsel-unknown-linux-gnu === g++ tests === Running target unix FAIL: g++.dg/cpp1y/feat-cxx14.C -std=gnu++1y (test for excess errors) FAIL: g++.dg/guality/pr55665.C -O2 line 23 p == 40 FAIL: g++.dg/guality/pr55665.C -O3 -fomit-frame-pointer line 23 p == 40 FAIL: g++.dg/guality/pr55665.C -O3 -g line 23 p == 40 XPASS: g++.dg/tls/thread_local-order2.C -std=c++11 execution test XPASS: g++.dg/tls/thread_local-order2.C -std=c++1y execution test === g++ Summary for unix === # of expected passes79605 # of unexpected failures4 # of unexpected successes 2 # of expected failures 439 # of unsupported tests 3197 Running target unix/-fstack-protector FAIL: g++.dg/cpp1y/feat-cxx14.C -std=gnu++1y (test for excess errors) FAIL: g++.dg/guality/pr55665.C -O2 line 23 p == 40 FAIL: g++.dg/guality/pr55665.C -O3 -fomit-frame-pointer line 23 p == 40 FAIL: g++.dg/guality/pr55665.C -O3 -g line 23 p == 40 XPASS: g++.dg/tls/thread_local-order2.C -std=c++11 execution test XPASS: g++.dg/tls/thread_local-order2.C -std=c++1y execution test === g++ Summary for unix/-fstack-protector === # of expected passes79605 # of unexpected failures4 # of unexpected successes 2 # of expected failures 439 # of unsupported tests 3197 Running target unix/-mabi=64 FAIL: g++.dg/cpp1y/feat-cxx14.C -std=gnu++1y (test for excess errors) XPASS: g++.dg/tls/thread_local-order2.C -std=c++11 execution test XPASS: g++.dg/tls/thread_local-order2.C -std=c++1y execution test === g++ Summary for unix/-mabi=64 === # of expected passes81389 # of unexpected failures1 # of unexpected successes 2 # of expected failures 439 # of unsupported tests 3197 Running target unix/-mabi=n32 FAIL: g++.dg/cpp1y/feat-cxx14.C -std=gnu++1y (test for excess errors) XPASS: g++.dg/tls/thread_local-order2.C -std=c++11 execution test XPASS: g++.dg/tls/thread_local-order2.C -std=c++1y execution test === g++ Summary for unix/-mabi=n32 === # of expected passes81599 # of unexpected failures1 # of unexpected successes 2 # of expected failures 439 # of unsupported tests 3177 === g++ Summary === # of expected passes322198 # of unexpected failures10 # of unexpected successes 8 # of expected failures 1756 # of unsupported tests 12768 /build/gcc-4.9-dw4Br4/gcc-4.9-4.9.1/build/gcc/testsuite/g++/../../xg++ version 4.9.1 (Debian 4.9.1-19) === gcc tests === Running target unix FAIL: gcc.dg/graphite/id-pr46845.c (internal compiler error) FAIL: gcc.dg/graphite/id-pr46845.c (test for excess errors) XPASS: gcc.dg/guality/example.c -O0 execution test XPASS: gcc.dg/guality/example.c -O2 execution test XPASS: gcc.dg/guality/example.c -O2 -flto -fno-use-linker-plugin -flto-partition=none execution test XPASS: gcc.dg/guality/guality.c -O0 execution test XPASS: gcc.dg/guality/guality.c -O1 execution test XPASS: gcc.dg/guality/guality.c -O2 execution test XPASS: gcc.dg/guality/guality.c -O3 -fomit-frame-pointer execution test XPASS: gcc.dg/guality/guality.c -O3 -g execution test XPASS: gcc.dg/guality/guality.c -Os execution test XPASS: gcc.dg/guality/guality.c -O2 -flto -fno-use-linker-plugin -flto-partition=none execution test XPASS: gcc.dg/guality/guality.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects execution test XPASS: gcc.dg/guality/inline-params.c -O2 execution test XPASS: gcc.dg/guality/inline-params.c -O3 -fomit-frame-pointer execution test XPASS: gcc.dg/guality/inline-params.c -O3 -g execution test XPASS: gcc.dg/guality/inline-params.c -Os execution test XPASS: gcc.dg/guality/inline-params.c -O2 -flto -fno-use-linker-plugin -flto-partition=none execution test FAIL: gcc.dg/guality/pr36728-1.c -O1 line 16 arg1 == 1 FAIL: gcc.dg/guality/pr36728-1.c -O1 line 18 arg1 == 1 FAIL: gcc.dg/guality/pr36728-1.c -O1 line 18 arg2 == 2 FAIL: gcc.dg/guality/pr36728-1.c -O2 line 16 arg1 == 1 FAIL: gcc.dg/guality/pr36728-1.c -O2 line 16 arg2 == 2 FAIL: gcc.dg/guality/pr36728-1.c -O2 line 18 arg1 == 1 FAIL: gcc.dg/guality/pr36728-1.c -O2 line 18 arg2 == 2 FAIL: gcc.dg/guality/pr36728-1.c -O3 -fomit-frame-pointer line 16 arg1 == 1 FAIL: gcc.dg/guality/pr36728-1.c -O3 -fomit-frame-pointer line 16 arg2 == 2 FAIL: gcc.dg/guality/pr36728-1.c -O3 -fomit-frame-pointer line 18 arg1 == 1 FAIL: gcc.dg/guality/pr36728-1.c -O3 -fomit-frame-pointer line 18 arg2 == 2 FAIL: gcc.dg/guality/pr36728-1.c -O3 -g line 16 arg1 == 1 FAIL: gcc.dg/guality/pr36728-1.c -O3 -g line 16 arg2 == 2 FAIL: gcc.dg/guality/pr36728-1.c -O3 -g line 18 arg1 == 1 FAIL:
Bug#760770: gcc-4.9: fails to build cross-compiler package
Control: retitle -1 fails to cross build libphobos when setting
with_deps_on_target_arch_pkgs=yes
Control: tags -1 = patch
Ian Jackson suggested that I should take care of this. See:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766708#68
On Tue, Sep 09, 2014 at 07:24:19PM +0200, Rico Rommel wrote:
libphobos-cross-ma-libdir.diff corrects the installdir in libphobos and
fix-rules includes the patch into rules.patch
This should not be a separate patch but rather integrated into
cross-ma-install-location.diff. Once it sits in that patch, it is
guaranteed to not affect the native build or the supported default
cross toolchain build, because neither use that patch.
I am attaching the updated patch.
Helmut
diff -u gcc-4.9-4.9.1/debian/changelog gcc-4.9-4.9.1/debian/changelog
--- gcc-4.9-4.9.1/debian/changelog
+++ gcc-4.9-4.9.1/debian/changelog
@@ -1,3 +1,10 @@
+gcc-4.9 (4.9.1-19.1) UNRELEASED; urgency=low
+
+ * Non-maintainer upload.
+ * Update cross-ma-install-location.diff for libphobos. Closes: #760770.
+
+ -- Helmut Grohne hel...@subdivi.de Tue, 28 Oct 2014 18:57:40 +0100
+
gcc-4.9 (4.9.1-19) unstable; urgency=medium
* GCC 4.9.2 release candidate.
diff -u gcc-4.9-4.9.1/debian/patches/cross-ma-install-location.diff
gcc-4.9-4.9.1/debian/patches/cross-ma-install-location.diff
--- gcc-4.9-4.9.1/debian/patches/cross-ma-install-location.diff
+++ gcc-4.9-4.9.1/debian/patches/cross-ma-install-location.diff
@@ -402,0 +403,21 @@
+Index: b/src/libphobos/configure.ac
+===
+--- a/src/libphobos/configure.ac
b/src/libphobos/configure.ac
+@@ -247,14 +247,8 @@
+ AC_ARG_WITH([cross-host],
+ AC_HELP_STRING([--with-cross-host=HOST],
+ [configuring with a cross compiler]))
+-if test -n $with_cross_host
+- test x$with_cross_host != xno; then
+- phobos_toolexecdir='${exec_prefix}/${host_alias}'
+- phobos_toolexeclibdir='${toolexecdir}/lib'
+-else
+- phobos_toolexecdir='${libdir}/gcc/${host_alias}'
+- phobos_toolexeclibdir='${libdir}'
+-fi
++phobos_toolexecdir='${libdir}/gcc/${host_alias}'
++phobos_toolexeclibdir='${libdir}'
+ # The norm would be to use $GDC -print-multi-os-directory, but
+ # that would require modifying config-ml.in
+ multi_os_directory=`$CC -print-multi-os-directory`
Processed: Re: Bug#760770: gcc-4.9: fails to build cross-compiler package
Processing control commands: retitle -1 fails to cross build libphobos when setting with_deps_on_target_arch_pkgs=yes Bug #760770 [gcc-4.9] gcc-4.9: fails to build cross-compiler package Changed Bug title to 'fails to cross build libphobos when setting with_deps_on_target_arch_pkgs=yes' from 'gcc-4.9: fails to build cross-compiler package' tags -1 = patch Bug #760770 [gcc-4.9] fails to cross build libphobos when setting with_deps_on_target_arch_pkgs=yes Added tag(s) patch; removed tag(s) help and moreinfo. -- 760770: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760770 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.b760770.141452631110675.transcr...@bugs.debian.org
