Setting up Binutils workers/builders on Solaris
Rainer Orth
ro@CeBiTec.Uni-Bielefeld.DE
Sat Jun 6 08:02:01 GMT 2026
Hi Mark,
> The x86 builds are starting up now, however, for the amd64 builder
> configure fails with
>
> configure: error: unrecognized option: `--buildamd64-sun-solaris2.11'
>
> The i386 builder finished, but several of the logs (gprof, libsframe,
> libctf) are empty. I'll check why this happened.
There are several issues here:
* In my local testing, I've always run make -k -j<N> check as is
customary to avoid failure of one testsuite to break the others. This
is what happens here: make check-gprof fails, so the two others
(libctf, libsframe) aren't even run though they pass just fine
locally.
* gprof, unlike the others, doesn't use a DejaGnu testsuite, but one of
its own. So failure to build or run the tests causes make check to
fail.
* In my own testing, I've always used the toplevel mail-report.log
target, which runs contrib/test_summary -t, to generate a easy to
digest report of testsuite results, as is done over in gcc. The gprof
failures didn't show up there as FAILs, so this went unnoticed.
I'll look into the gprof failures, but I guess it would be best for the
build master to use make -k check as is done elsewhere.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
More information about the Buildbot
mailing list