Re: Running contrib/config-list.mk from the buildbots

[Jan-Benedict Glaw <jbglaw at lug-owl dot de>]

On Tue, 2013-11-19 13:20:41 -0500, Diego Novillo <dnovillo@google.com> wrote:
> On Tue, Nov 19, 2013 at 1:11 PM, Jan-Benedict Glaw <jbglaw@lug-owl.de> wrote:
> > On Tue, 2013-11-19 12:08:05 -0500, Diego Novillo <dnovillo@google.com> 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 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
> > example:
> 
> 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.

The Build Robot just uses whatever GCC is there, if no compiler is set
explicitely. (I tried that with eg. IBM's XL compiler, but that broke
horribly. Still lots of stuff to clean up.)

  In general, building with a trunk (or otherwise recent) GCC isn't
much of a problam if there's one around.

MfG, JBG

-- 
      Jan-Benedict Glaw      jbglaw@lug-owl.de              +49-172-7608481
Signature of:                 Gib Dein Bestes. Dann Ãbertriff Dich selbst!
the second  :

Attachment: signature.asc
Description: Digital signature