This is the mail archive of the
mailing list for the GCC project.
Re: Running contrib/config-list.mk from the buildbots
- From: Diego Novillo <dnovillo at google dot com>
- To: Jan-Benedict Glaw <jbglaw at lug-owl dot de>
- Cc: gcc <gcc at gcc dot gnu dot org>
- Date: Tue, 19 Nov 2013 13:20:41 -0500
- Subject: Re: Running contrib/config-list.mk from the buildbots
- Authentication-results: sourceware.org; auth=none
- References: <CAD_=9DSVuYfWm2+qnsNVrWKB7q5yfb62Rktfo2-Nv9tR5obq-w at mail dot gmail dot com> <20131119170312 dot GN30563 at lug-owl dot de> <CAD_=9DTrRKu2Zi_dw-W0LfKnOE+j8Fhk2+GHN8WffOjVOE9dOA at mail dot gmail dot com> <20131119181140 dot GP30563 at lug-owl dot de>
On Tue, Nov 19, 2013 at 1:11 PM, Jan-Benedict Glaw <firstname.lastname@example.org> wrote:
> On Tue, 2013-11-19 12:08:05 -0500, Diego Novillo <email@example.com> wrote:
>> 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 certainly take out the ones that just don't build as-is.
> With -Werror in place, I think not a single target will build right now, due to
> warnings/errors in common code. Just picking a recent s390x-linux as an
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 targets that actually build with 4.8 is
the way to go.