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 12:08:05 -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>
On Tue, Nov 19, 2013 at 12:03 PM, Jan-Benedict Glaw <email@example.com> wrote:
> Hi Diego!
> On Tue, 2013-11-19 10:20:48 -0500, Diego Novillo <firstname.lastname@example.org> 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 latest release).
>> 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.
>> Would this be hard to set up in your buildbots?
> I haven't ever directly used config-list.mk, so I'm just guessing
> around here :)
> Starting from making it work, different host-local options may need
> to be set (cf. "host_options='--with-mpc=/opt/cfarm/mpc' # gcc10"
> found in that file.)
Well, you need that for your other builds anyway, right? Everything
needs a working gmp/mpfr/mpc. Anything that is optional does not need
to be done with this script.
> Additional to that, it needs a combined tree, right? Shouldn't be
> much of a problem.
No. It just needs a relatively recent set of tools on the host (gcc,
> With Ada and Go (as well as `all' languages), there are quite a few
> more dependencies, so I guess I wouldn't like to run it on all hosts.
We don't need to test Ada and Go with the buildbots.
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.