Re: [buildrobot] First results of running contrib/config-list.mk

2013-12-02 Thread Joseph S. Myers
On Mon, 2 Dec 2013, Jan-Benedict Glaw wrote: > On Mon, 2013-12-02 12:08:25 +0100, Gerald Pfeifer wrote: > > On Tue, 26 Nov 2013, Joseph S. Myers wrote: > > > I think it's time to remove targets that have been under > > > --enable-obsolete > > > for a while - and to obsolete, for possible future

Re: [buildrobot] First results of running contrib/config-list.mk

2013-12-02 Thread Jan-Benedict Glaw
On Mon, 2013-12-02 12:08:25 +0100, Gerald Pfeifer wrote: > On Tue, 26 Nov 2013, Joseph S. Myers wrote: > > I think it's time to remove targets that have been under --enable-obsolete > > for a while - and to obsolete, for possible future removal, targets > > without stdint.h type information conf

Re: [buildrobot] First results of running contrib/config-list.mk

2013-12-02 Thread Gerald Pfeifer
On Tue, 26 Nov 2013, Joseph S. Myers wrote: > I think it's time to remove targets that have been under --enable-obsolete > for a while - and to obsolete, for possible future removal, targets > without stdint.h type information configured in GCC (see list in >

Re: [buildrobot] First results of running contrib/config-list.mk

2013-11-26 Thread Joseph S. Myers
Many such failures may already have bugs in Bugzilla (generally filed by Joern). I think it's time to remove targets that have been under --enable-obsolete for a while - and to obsolete, for possible future removal, targets without stdint.h type information configured in GCC (see list in

Re: [buildrobot] First results of running contrib/config-list.mk

2013-11-26 Thread Ian Lance Taylor
On Mon, Nov 25, 2013 at 7:20 PM, Jan-Benedict Glaw wrote: > > The two build robot instances that schedule jobs using > contrib/config-list.mk are done with two rounds. I haven't looked at > the details (and thus there are no patches), but I'd like to point out > the results. > > Depending on the h

[buildrobot] First results of running contrib/config-list.mk

2013-11-25 Thread Jan-Benedict Glaw
Hi! The two build robot instances that schedule jobs using contrib/config-list.mk are done with two rounds. I haven't looked at the details (and thus there are no patches), but I'd like to point out the results. Depending on the host, gcc/g++ is: gcc20: g++ (GCC) 4.9.0 20131122 (experime