Re: updating the build matrix

["Dan Kegel" <dank at kegel dot com>]

On 2/21/06, Robert P. J. Day <rpjday@mindspring.com> wrote:
> http://kegel.com/crosstool/crosstool-0.40/buildlogs/
>
> 1) i'm a bit puzzled about some of the combinations shown.  the older
> gcc-3.4.5 is shown as having been built with glibc-2.3.6 in some
> cases, but the newer gcc-4.x are shown as having been built with only
> up to glibc-2.3.5 (and, in some cases, glibc-2.3.2 or even
> glibc-2.2.2).  wouldn't it be natural to try builds with the latest
> combinations of everything?

Sort of.  We should certainly test with the latest glibc release to
show their cpu support progress.  But 'classic' glibc versions are really
important to test, since very few systems actually run the latest glibc -
we're all stuck on various older glibc's.

I'll add at least the latest gcc/glibc combination next time I run.
But I can't add too many - running all those builds takes a lot of time!

> 2) how does one submit successful builds?

The build matrix is the output of crosstool/regtest-{run,report}.sh.

> i just used CT-0.40 to
> build an SH3eb toolchain out of the box, and it seems to compile your
> basic "hello, world".  i'm also pretty sure it will compile the latest
> 2.6.15 kernel with all of the SH-specific dropins (i'll verify that
> later today).  my combination:
>
>         gcc-4.0.2
>         glibc-2.3.6
>         binutils-2.16.1
>         linux-libc-headers-2.6.12.0

Good - but I can't add that into the build matrix unless I repeat it myself,
and that means adding that combination to regtest-run.sh (and lotsa cpu time).
- Dan

--
Wine for Windows ISVs: http://kegel.com/wine/isv

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.org