On Tue, Nov 19, 2013 at 3:36 PM, Joern Rennecke
wrote:
> On 19 November 2013 18:20, Diego Novillo wrote:
>
>> Right, because you're using 4.8. These warnings disappear when using
>> trunk and/or do not actually break the build. I suppose this is too
>> much for the buildbot then? It won't have
On 19 November 2013 18:20, Diego Novillo wrote:
> Right, because you're using 4.8. These warnings disappear when using
> trunk and/or do not actually break the build. I suppose this is too
> much for the buildbot then? It won't have a recent trunk around, so
> perhaps restricting it to the tar
On Tue, 2013-11-19 13:20:41 -0500, Diego Novillo wrote:
> On Tue, Nov 19, 2013 at 1:11 PM, Jan-Benedict Glaw wrote:
> > On Tue, 2013-11-19 12:08:05 -0500, Diego Novillo
> > wrote:
> > [conffig-list.mk]
> >> Really, the only thing interesting about the script is the broad set
> >> of targets it
On Tue, Nov 19, 2013 at 1:11 PM, Jan-Benedict Glaw wrote:
> On Tue, 2013-11-19 12:08:05 -0500, Diego Novillo wrote:
> [conffig-list.mk]
>> Really, the only thing interesting about the script is the broad set
>> of targets it uses. If you just added them to the schedule of builds,
>> that should b
On Tue, 2013-11-19 12:08:05 -0500, Diego Novillo wrote:
[conffig-list.mk]
> Really, the only thing interesting about the script is the broad set
> of targets it uses. If you just added them to the schedule of builds,
> that should be sufficient. We could even decide not to add all of
> them. And c
On Tue, 2013-11-19 12:08:05 -0500, Diego Novillo wrote:
> On Tue, Nov 19, 2013 at 12:03 PM, Jan-Benedict Glaw wrote:
> > On Tue, 2013-11-19 10:20:48 -0500, Diego Novillo
> > wrote:
[config-list.mk]
> >> Would this be hard to set up in your buildbots?
> >
> > I haven't ever directly used config-
On Tue, Nov 19, 2013 at 12:03 PM, Jan-Benedict Glaw wrote:
> Hi Diego!
>
> On Tue, 2013-11-19 10:20:48 -0500, Diego Novillo wrote:
>> I've been thinking that it would be very useful for buildbots to run
>> contrib/config-list.mk. This tests stage1's all-gcc on a very wide
>> collection of targets
Hi Diego!
On Tue, 2013-11-19 10:20:48 -0500, Diego Novillo wrote:
> I've been thinking that it would be very useful for buildbots to run
> contrib/config-list.mk. This tests stage1's all-gcc on a very wide
> collection of targets. It builds everything with -Werror, so it
> requires a recent host
On Tue, Nov 19, 2013 at 4:20 PM, Diego Novillo wrote:
> Currently, many targets are broken because of -Werror. I was thinking
> of fixing them, but unless we keep them clean with a buildbot they
> will regress.
How nobel. But isn't this what we have port maintainers for?
I'd say: Let it be! If a
On Tue, Nov 19, 2013 at 10:29 AM, Sebastian Huber
wrote:
> On 2013-11-19 16:20, Diego Novillo wrote:
>>
>> I've been thinking that it would be very useful for buildbots to run
>> contrib/config-list.mk. This tests stage1's all-gcc on a very wide
>> collection of targets. It builds everything with
On 2013-11-19 16:20, Diego Novillo wrote:
I've been thinking that it would be very useful for buildbots to run
contrib/config-list.mk. This tests stage1's all-gcc on a very wide
collection of targets. It builds everything with -Werror, so it
requires a recent host compiler (ideally trunk or the l
I've been thinking that it would be very useful for buildbots to run
contrib/config-list.mk. This tests stage1's all-gcc on a very wide
collection of targets. It builds everything with -Werror, so it
requires a recent host compiler (ideally trunk or the latest release).
Currently, many targets are
12 matches
Mail list logo
