Re: Current and upcoming toolchain changes for jessie
On Sat, Jun 22, 2013 at 11:48:39PM +0200, Bastian Blank wrote: > On Thu, Jun 13, 2013 at 02:51:43PM +0200, Matthias Klose wrote: > > GCC 4.8 is now the default on all x86 architectures, and on all ARM > > architectures (the latter confirmed by the Debian ARM porters). Please change the default for s390 and s390x to 4.8. Bastian -- Warp 7 -- It's a law we can live with. -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2013070100.ga12...@mail.waldi.eu.org
Re: Current and upcoming toolchain changes for jessie
On Thu, Jun 13, 2013 at 02:51:43PM +0200, Matthias Klose wrote: > GCC 4.8 is now the default on all x86 architectures, and on all ARM > architectures (the latter confirmed by the Debian ARM porters). GCC 4.8 seems fine on s390x, it can build a running Linux kernel. On s390 something weird happened and I have to investigate what I broke. Bastian -- The face of war has never changed. Surely it is more logical to heal than to kill. -- Surak of Vulcan, "The Savage Curtain", stardate 5906.5 -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130622214838.ga3...@mail.waldi.eu.org
Re: Current and upcoming toolchain changes for jessie
On Tue, Jun 18, 2013 at 8:02 PM, John David Anglin wrote: > Hi Aurelien, > > > On 18-Jun-13, at 6:05 PM, Aurelien Jarno wrote: > >> This is true that they have recently contacted me through another email >> address, but I haven't found time to work on that. Just stay tuned. > > > That's great news. > > Helge and I have been working away as best we can to maintain the port. I > know everybody is busy and this is a significant effort. ... and I'm incredibly busy with upstream glibc, but I'm trying my best to ensure hppa keeps building upstream glibc. Cheers, Carlos. -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAE2sS1g+63BWgBfwV8pHzRAQrpzv2V_AhZ9AmPsm4Y-h8=g...@mail.gmail.com
Re: Current and upcoming toolchain changes for jessie
On 14-06-13 21:11, Thorsten Glaser wrote: > Wouter, Mikael: input on switching C/C++ to 4.8? We don't have much data either way, do we? I suppose it shouldn't be too much of a problem, but I can't be sure. In the past we've usually taken the plunge, and filed bugs if things go really bad. -- This end should point toward the ground if you want to go to space. If it starts pointing toward space you are having a bad problem and you will not go to space today. -- http://xkcd.com/1133/ -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51c171d9.50...@debian.org
Re: Current and upcoming toolchain changes for jessie
Hi Aurelien, On 18-Jun-13, at 6:05 PM, Aurelien Jarno wrote: This is true that they have recently contacted me through another email address, but I haven't found time to work on that. Just stay tuned. That's great news. Helge and I have been working away as best we can to maintain the port. I know everybody is busy and this is a significant effort. Dave -- John David Anglin dave.ang...@bell.net -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/blu0-smtp54755f6f47f39a181d6a697...@phx.gbl
Re: Current and upcoming toolchain changes for jessie
On Fri, Jun 14, 2013 at 01:12:30PM +0200, Matthias Klose wrote: > Am 13.06.2013 16:46, schrieb Steven Chamberlain: > > Hi, > > > > On 13/06/13 13:51, Matthias Klose wrote: > >> GCC 4.8 is now the default on all x86 architectures, and on all ARM > >> architectures (the latter confirmed by the Debian ARM porters). I did not > >> get > >> any feedback from other port maintainers, so unless this does change and > >> port > >> maintainers get involved with toolchain maintenance, the architectures > >> staying > >> at 4.6 or 4.7 shouldn't be considered for a successful release > >> (re-)qualification. > > > > I trust these are the architectures that are okay so far: > > | gcc48_archs = amd64 armel armhf arm64 i386 x32 kfreebsd-amd64 > > kfreebsd-i386 hurd-i386 > > no, they are probably not ok, and there surely are yet undiscovered > regressions, > but at least the ARM porters did agree to address these. Same seems to be true > for the kfreebsd and hurd porters. They did change GCC defaults usually at the > same time as this was done for the x86 linux archs. > > > So the following would be the architectures for which some response is > > requested urgently from port maintainers, to confirm they are ready for > > GCC 4.8 as default: > > > > Release arches: ia64 mips mipsel powerpc s390 s390x sparc > > > > All the above have built gcc-4.8.1-2 or higher. > > and nobody committing to scan the bts for architecture specific issues, nobody > to prepare test cases, nobody to forward these. I did report a few mips/mipsel issue to upstream binutils and gcc, and they have all been solved. I am not aware of any reported mips/mipsel binutils or gcc-4.{6,7,8} problem reported in the debian BTS, except #710683, which is recent and I haven't investigated it yet (but is likely an OOM issue on the buildd). Could you please provide me a few pointers? > > Other ports: alpha hppa* m68k powerpcspe ppc64 sh4* sparc64* > > > > * these ports don't appear to have successfully built GCC 4.8 yet. > > afaics, alpha, powerpcspe and ppc64 did build. Note that you cannot trust the > hppa status, this port is still denied access to ports.debian.org and is kept > in > another place. > hppa porters have ignored my emails during a few years, and then started to write me during a few more years using an email address that went to /dev/null, so they never got my answers, and thus never answered me... This is true that they have recently contacted me through another email address, but I haven't found time to work on that. Just stay tuned. -- Aurelien Jarno GPG: 1024D/F1BCDB73 aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130618220536.ga22...@hall.aurel32.net
Re: Current and upcoming toolchain changes for jessie
Am 15.06.2013 03:22, schrieb Stephan Schreiber: > GCC-4.8 should become the default on ia64 soon; some other changes are > desirable: > - The transition of gcc-4.8/libgcc1 to libunwind8. > - A removal of the libunwind7 dependency of around 4600 packages on ia64 - > when > they are updated next time after the transition. The libc6.1 should (likely) > depend on libunwind8 after that in order to guarantee that libunwind8 is > installed. unless some ia64 porter steps up, it doesn't make sense to invest time into the ia64 port. So better drop ia64 now, and don't bother with libunwind on ia64. Matthias -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51bf06cd.3070...@debian.org
Re: Current and upcoming toolchain changes for jessie
GCC-4.8 should become the default on ia64 soon; some other changes are desirable: - The transition of gcc-4.8/libgcc1 to libunwind8. - A removal of the libunwind7 dependency of around 4600 packages on ia64 - when they are updated next time after the transition. The libc6.1 should (likely) depend on libunwind8 after that in order to guarantee that libunwind8 is installed. Stephan -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130615032245.horde.t7xtwhrox0q8ei0bj2c0...@webmail.df.eu
Re: Current and upcoming toolchain changes for jessie
Matthias Klose dixit: >> I’d like to have gcj at 4.6 in gcc-defaults for m68k please, >> until the 4.8 one stops FTBFSing. > >please send a patch. For gcc-defaults? I think that one is trivial… For gcj? I did not take Compiler Design in what two semesters of Uni I managed until I ran out of money. I will, however, forward #711558 to upstream. I can’t do everything, but I don’t think anyone can accuse me of not trying either… >> From me nothing against switching C/C++ to 4.8 for m68k at >> this point, but I’d like to hear at least Wouter’s opinion >> on that, and possibly Mikael since he’s not just doing work >> upstream on gcc but also using it (for ColdFire) heavily. > >same as well, please send a patch. Wouter, Mikael: input on switching C/C++ to 4.8? [ Ada ] >try it and send a patch please. Would be useful to get it compiled first, for which #711558 is currently the blocker AFAICT. But I guess I’ll try eventually. Note to myself: do not “temporarily help out” in any more Debian projects, you’ll never leave them… bye, //mirabilos, sponsoring for a week of Linuxhotel would be nice… (I’m seriously short of hacking time, in general, recently, and could use some switching of paper hangings for a while) -- Support mksh as /bin/sh and RoQA dash NOW! ‣ src:bash (259 (278) bugs: 0 RC, 182 (196) I&N, 77 (82) M&W, 0 (0) F&P) ‣ src:dash (86 (102) bugs: 3 RC, 41 (46) I&N, 42 (53) M&W, 0 F&P) ‣ src:mksh (2 bugs: 0 RC, 0 I&N, 2 M&W, 0 F&P, 1 gift) http://qa.debian.org/data/bts/graphs/d/dash.png is pretty red, innit? -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pine.bsm.4.64l.1306141907290.27...@herc.mirbsd.org
Re: Current and upcoming toolchain changes for jessie
Am 13.06.2013 16:46, schrieb Steven Chamberlain: > Hi, > > On 13/06/13 13:51, Matthias Klose wrote: >> GCC 4.8 is now the default on all x86 architectures, and on all ARM >> architectures (the latter confirmed by the Debian ARM porters). I did not >> get >> any feedback from other port maintainers, so unless this does change and port >> maintainers get involved with toolchain maintenance, the architectures >> staying >> at 4.6 or 4.7 shouldn't be considered for a successful release >> (re-)qualification. > > I trust these are the architectures that are okay so far: > | gcc48_archs = amd64 armel armhf arm64 i386 x32 kfreebsd-amd64 > kfreebsd-i386 hurd-i386 no, they are probably not ok, and there surely are yet undiscovered regressions, but at least the ARM porters did agree to address these. Same seems to be true for the kfreebsd and hurd porters. They did change GCC defaults usually at the same time as this was done for the x86 linux archs. > So the following would be the architectures for which some response is > requested urgently from port maintainers, to confirm they are ready for > GCC 4.8 as default: > > Release arches: ia64 mips mipsel powerpc s390 s390x sparc > > All the above have built gcc-4.8.1-2 or higher. and nobody committing to scan the bts for architecture specific issues, nobody to prepare test cases, nobody to forward these. > Other ports: alpha hppa* m68k powerpcspe ppc64 sh4* sparc64* > > * these ports don't appear to have successfully built GCC 4.8 yet. afaics, alpha, powerpcspe and ppc64 did build. Note that you cannot trust the hppa status, this port is still denied access to ports.debian.org and is kept in another place. So yes, some of these ports are in better shape than the ports released with wheezy. Matthias -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51bafa9e.5080...@debian.org
Re: Current and upcoming toolchain changes for jessie
Am 13.06.2013 21:47, schrieb Thorsten Glaser: > Matthias Klose dixit: > >> The Java and D frontends now default to 4.8 on all architectures, the Go >> frontend stays at 4.7 until 4.8 get the complete Go 1.1 support. > > I’d like to have gcj at 4.6 in gcc-defaults for m68k please, > until the 4.8 one stops FTBFSing. please send a patch. > From me nothing against switching C/C++ to 4.8 for m68k at > this point, but I’d like to hear at least Wouter’s opinion > on that, and possibly Mikael since he’s not just doing work > upstream on gcc but also using it (for ColdFire) heavily. same as well, please send a patch. > For Ada, I’d like to see a successful build of gnat-4.8 > (from src:gcc-4.8, if I understand the recent changes right) > first; gnat-4.6 mostly works at the moment, but I’m not sure > about the upstream situation wrt. patches from Mikael. try it and send a patch please. thanks for your cooperation, Matthias -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51baf88c.3080...@debian.org
Re: Current and upcoming toolchain changes for jessie
Steven Chamberlain dixit: >Before that can be changed, I think the gcc-defaults package expects >package version (>= 4.8.1-2) whereas m68k still has only the 4.8.0-7 you >uploaded. Right. That’s because gcj FTBFSes. >You will also first need newer binutils (>= 2.23.52) which is still in >the build queue. True; that’s new, but it’ll be done eventually, no hurries there ☺ bye, //mirabilos -- Support mksh as /bin/sh and RoQA dash NOW! ‣ src:bash (259 (278) bugs: 0 RC, 182 (196) I&N, 77 (82) M&W, 0 (0) F&P) ‣ src:dash (86 (102) bugs: 3 RC, 41 (46) I&N, 42 (53) M&W, 0 F&P) ‣ src:mksh (2 bugs: 0 RC, 0 I&N, 2 M&W, 0 F&P, 1 gift) http://qa.debian.org/data/bts/graphs/d/dash.png is pretty red, innit? -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pine.bsm.4.64l.1306132021420.22...@herc.mirbsd.org
Re: Current and upcoming toolchain changes for jessie
Matthias Klose dixit: >The Java and D frontends now default to 4.8 on all architectures, the Go >frontend stays at 4.7 until 4.8 get the complete Go 1.1 support. I’d like to have gcj at 4.6 in gcc-defaults for m68k please, until the 4.8 one stops FTBFSing. From me nothing against switching C/C++ to 4.8 for m68k at this point, but I’d like to hear at least Wouter’s opinion on that, and possibly Mikael since he’s not just doing work upstream on gcc but also using it (for ColdFire) heavily. For Ada, I’d like to see a successful build of gnat-4.8 (from src:gcc-4.8, if I understand the recent changes right) first; gnat-4.6 mostly works at the moment, but I’m not sure about the upstream situation wrt. patches from Mikael. bye, //mirabilos -- 17:08⎜«Vutral» früher gabs keine packenden smartphones und so 17:08⎜«Vutral» heute gibts frauen die sind facebooksüchtig 17:10⎜«Vutral» aber auch traurig; früher warst du als nerd voll am arsch 17:10⎜«Vutral» heute bist du als nerd der einzige der wirklich damit klarkommt -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pine.bsm.4.64l.1306131944240.22...@herc.mirbsd.org
Re: Current and upcoming toolchain changes for jessie
Hi, On 13/06/13 20:47, Thorsten Glaser wrote: > From me nothing against switching C/C++ to 4.8 for m68k at > this point, but I’d like to hear at least Wouter’s opinion > on that, and possibly Mikael [...] Before that can be changed, I think the gcc-defaults package expects package version (>= 4.8.1-2) whereas m68k still has only the 4.8.0-7 you uploaded. You will also first need newer binutils (>= 2.23.52) which is still in the build queue. (This applies to ppc64 as well). Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51ba2417.9070...@pyro.eu.org
Re: Current and upcoming toolchain changes for jessie
Am Donnerstag, den 13.06.2013, 15:46 +0100 schrieb Steven Chamberlain: > Hi, > > On 13/06/13 13:51, Matthias Klose wrote: > > GCC 4.8 is now the default on all x86 architectures, and on all ARM > > architectures (the latter confirmed by the Debian ARM porters). I did not > > get > > any feedback from other port maintainers, so unless this does change and > > port > > maintainers get involved with toolchain maintenance, the architectures > > staying > > at 4.6 or 4.7 shouldn't be considered for a successful release > > (re-)qualification. > > I trust these are the architectures that are okay so far: > | gcc48_archs = amd64 armel armhf arm64 i386 x32 kfreebsd-amd64 > kfreebsd-i386 hurd-i386 > > So the following would be the architectures for which some response is > requested urgently from port maintainers, to confirm they are ready for > GCC 4.8 as default: > > Release arches: ia64 mips mipsel powerpc s390 s390x sparc Is there some kind of timeframe expected when switch can be expected? I'm asking because I currently have some tool chain related build failure on the above archs (except ia64) for drizzle [1] (Bug 708434) -- From here, it looks like that the gcc 4.6.3-14 used on this archs needs a bin-nmu (?), as it is still expecting libcloog-ppl0, which is no longer available. [2] Matthias, could I be on the right path? What would be the right procedure here? (CC'ing d-mentors for this question) coldtobi [1] https://buildd.debian.org/status/logs.php?pkg=drizzle&ver=1% 3A7.1.36-stable-4&suite=sid [2] http://packages.qa.debian.org/c/cloog-ppl.html -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1371151240.6107.0.ca...@mordor.loewenhoehle.ip
Re: Current and upcoming toolchain changes for jessie
Hi, On 13/06/13 13:51, Matthias Klose wrote: > GCC 4.8 is now the default on all x86 architectures, and on all ARM > architectures (the latter confirmed by the Debian ARM porters). I did not get > any feedback from other port maintainers, so unless this does change and port > maintainers get involved with toolchain maintenance, the architectures staying > at 4.6 or 4.7 shouldn't be considered for a successful release > (re-)qualification. I trust these are the architectures that are okay so far: | gcc48_archs = amd64 armel armhf arm64 i386 x32 kfreebsd-amd64 kfreebsd-i386 hurd-i386 So the following would be the architectures for which some response is requested urgently from port maintainers, to confirm they are ready for GCC 4.8 as default: Release arches: ia64 mips mipsel powerpc s390 s390x sparc All the above have built gcc-4.8.1-2 or higher. Other ports: alpha hppa* m68k powerpcspe ppc64 sh4* sparc64* * these ports don't appear to have successfully built GCC 4.8 yet. Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51b9db2c.2060...@pyro.eu.org
Re: Current and upcoming toolchain changes for jessie
Am 07.05.2013 15:25, schrieb Matthias Klose: > The decision when to make GCC 4.8 the default for other architectures is > left to the Debian port maintainers. [...] > Information on porting to GCC 4.8 from previous versions of GCC can be > found in the porting guide http://gcc.gnu.org/gcc-4.8/porting_to.html > > It is planned to only keep GCC 4.8 and the upcoming GCC 4.9, and to remove > 4.4, 4.6 and 4.7 from jessie. GCC 4.8 is now the default on all x86 architectures, and on all ARM architectures (the latter confirmed by the Debian ARM porters). I did not get any feedback from other port maintainers, so unless this does change and port maintainers get involved with toolchain maintenance, the architectures staying at 4.6 or 4.7 shouldn't be considered for a successful release (re-)qualification. The Java and D frontends now default to 4.8 on all architectures, the Go frontend stays at 4.7 until 4.8 get the complete Go 1.1 support. Matthias -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51b9c05f.8050...@debian.org