This is the mail archive of the
mailing list for the GCC project.
Re: gcc 4.4.0 on Solaris 10 Sparc, some tests failed.
- From: Ian Lance Taylor <iant at google dot com>
- To: ad_101 at yahoo dot com
- Cc: Eric Botcazou <ebotcazou at adacore dot com>, gcc at gcc dot gnu dot org, "Kaveh R. GHAZI" <ghazi at caip dot rutgers dot edu>
- Date: Mon, 18 May 2009 07:50:50 -0700
- Subject: Re: gcc 4.4.0 on Solaris 10 Sparc, some tests failed.
- References: <email@example.com>
Amitava Dutta <firstname.lastname@example.org> writes:
> You mentioned that the "make -k # check" is broken on Solaris.
You mean -j, not -k. There is no problem with -k.
> I built the compiler using the -k option, is that a concern?
> or is it just the "check" target is broken?
> IOW, should I build the compiler without the "-k" option?
It's just the testsuite, which is relying on some GNU specific behaviour
of awk. There is no problem using make -j (or -k) when building the
> At this point, should I do the next build using the recently
> built gcc 4.4.0?
If you do a normal bootstrap, which is what happens if you follow the
installation instructions, then it doesn't matter very much which
compiler you start with.
> btw, is there a quick tutorial on running the tests against
> an arbitrary compiler, that's installed on a given machine ?
Unfortunately I don't know of one. I believe you can do it by fiddling
with the site.exp file which is generated when you run "make check".
Note that it's not very useful to run the testsuite of one version of
gcc against another version of gcc, as a number of irrelevant changes
will cause testsuite failures--different warning messages and the like.