Setting up Binutils workers/builders on Solaris
Rainer Orth
ro@CeBiTec.Uni-Bielefeld.DE
Sat Jun 6 07:03:10 GMT 2026
Hi Mark,
> On Fri, Jun 05, 2026 at 09:58:22PM -0400, Frank Ch. Eigler wrote:
>> > The first build arrived and all solaris11 builders immediately
>> > succeeded without doing anything [...]
>> > Lets see how things go with those fixed as attached.
>>
>> It looks like the builders are now getting started all right, but
>> crashing during the make step, about 2-3 minutes into the build.
>
> The solaris11-amd64 worker disappeared completely. I did manually
> stopped the sparcv9 builders because they just kepts retrying and
> retrying.
there were two issues:
* Solaris SMF services restart by default whenever a subprocess dumps
core. While benign in the general case, for builders this occurs all
the time, either for configure tests or when running the testsuite.
This is what happened here: after the service had been restarted
several times shortly after another, it was stopped/put into
maintenance. I'm now ignoring that signal as I'd already done for the
llvm buildbot.
* configure was run with the default shell (/bin/sh, i.e. ksh93). While
this should work, it's both slower than bash and there's an issue with
creating the ld linker scripts. I've now put CONFIG_SHELL=/bin/bash
into the service environment to avoid this.
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.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
More information about the Buildbot
mailing list