Re: gcc 7, 6 builds killed on kfreebsd

2017-01-09 Thread Jonathan Haack
Unsubscribe > On Jan 9, 2017, at 9:04 AM, Steven Chamberlain wrote: > > Christoph Egger wrote: >> | WARNING: 30 signals -- adjust and recompile. > > That comes from pkill, which recently stopped working. This means, the > build already hung / timed out and sbuild is merely

Bug#850777: [gcc-6] internal compiler error on ppc64el (may be bug)

2017-01-09 Thread lumin
Package: gcc-6 Version: 6.3.0-2 Severity: normal Hi, GCC-6 failed when buildd is building torch7 package for ppc64el architecture. The buiild log can be found here: https://buildd.debian.org/status/fetch.php?pkg=lua-torch-torch7=ppc64el=0~20170106-gf624ae9-1=1483980176 Currently I don't know

Bug#850749: gcc-6: Please enable gccgo on m68k

2017-01-09 Thread Matthias Klose
On 09.01.2017 22:44, John Paul Adrian Glaubitz wrote: > Source: gcc-6 > Version: 6.3.0-2 > Severity: normal > Tags: patch > User: debian-...@lists.debian.org > Usertags: m68k > > Hi! > > I just successfully verified that enabling gccgo on m68k produces a > working gccgo package. I merely

Bug#850749: gcc-6: Please enable gccgo on m68k

2017-01-09 Thread John Paul Adrian Glaubitz
On 01/09/2017 10:54 PM, Matthias Klose wrote: > Do you have test results for a build? I did not run the testsuite, if that's what you are asking and it seems that there are some issues that need to be resolved first. However, I would like to have gccgo enabled to be able to easily install it and

Bug#850749: gcc-6: Please enable gccgo on m68k

2017-01-09 Thread John Paul Adrian Glaubitz
Source: gcc-6 Version: 6.3.0-2 Severity: normal Tags: patch User: debian-...@lists.debian.org Usertags: m68k Hi! I just successfully verified that enabling gccgo on m68k produces a working gccgo package. I merely modified debian/rules.defs in the current gcc-6 package to remove "m68k" from the

Re: gcc 7, 6 builds killed on kfreebsd

2017-01-09 Thread Steven Chamberlain
Christoph Egger wrote: > | WARNING: 30 signals -- adjust and recompile. That comes from pkill, which recently stopped working. This means, the build already hung / timed out and sbuild is merely failing to kill it. For that I've just filed Bug#850717 against procps: [kfreebsd] pkill fails,

Re: gcc 7, 6 builds killed on kfreebsd

2017-01-09 Thread Steven Chamberlain
Hi! Christoph Egger wrote: > I've just killed the gcc builds on kfreebsd. THey're all looping with a > > | WARNING: 30 signals -- adjust and recompile. Thanks; it seems to have happened again though on kfreebsd-amd64 (stuck building gcc-6 and gcc-snapshot for 5+ days). I will look into this