Setting up Binutils workers/builders on Solaris

Mark Wielaard mark@klomp.org
Wed Jun 3 14:38:50 GMT 2026


Hi Rainer,

On Wed, 2026-05-13 at 11:55 +0200, Rainer Orth wrote:
> I'd like to set up a couple of workers/builders on Solaris, initially
> for Binutils.  My current plan is to have two workers, one each for
> Solaris/x86 and Solaris/SPARC.  Both should support two builders, one
> for 32 and another for 64-bit.  The initial configuration would be
> something like this:
> 
> * Each worker has
> 
>   ncpus: 4
>   maxcpus: 4
>   max_builds: 1
> 
>   to start with.  Maybe this can be increased later as need be.
>   However, in local builds/checks from scratch, build/check times are
>   between 6 min (x86) and 10 min (sparc).
> 
>   The Solaris kernel zones (VMs effectively) are shared with other
>   builders, one for LLVM, another for Golang.
> 
>   I'd like to run each of those as different users, adding a new user
>   for the new binutils ones.  If/when I extend this to gdb in the
>   future, those workers should run under a different user and most
>   likely will have a differing environment (like PATH, resource
>   controls, and ncpus).
> 
>   I'm unsure how to name those workers: they probably should include
>   solaris11-sparcv9 and solaris11-amd64 respectively, maybe with a
>   binutils prefix or suffix to allow for later extension to gdb.

As you describe below workers can support multiple builders. So in
theory adding e.g. gdb builds would just assign more builders to these
existing workers. But see below for path/environment setup.

> * The builders could be named something like
> 
>   binutils-solaris11-sparcv9
>   binutils-solaris11-sparc
> 
>   binutils-solaris11-amd64
>   binutils-solaris11-i386
> 
>   matching what my current LLVM builders use.
> 
>   The builders need to run configure with one of
> 
> 	--build sparc{v9,}-sun-solaris2.11
>   or
> 
> 	--build {amd64,i386}-pc-solaris2.11
> 
>   since config.guess has been broken on Solaris beyond recognition ;-(
> 
>   One complication is that the 32 and 64-bit builders need to use a
>   different PATH (prefix): they need their own special gcc, configured
>   to default to either 32 or 64 bit and use gas/gld from PATH, rather
>   than specified with --with-as/--with-ld.
> 
>   I believe this can be done in the buildbot configuration, setting the
>   environment per builder.
> 
> Do you think this can be done?

Yes, attached is the patch to do it. What are the different PATHs used
for the different builders? You could also setup 4 workers and match
each builder with a specific worker (that already has the PATH setup).

You might want to install ccache (and put the ccache compilers on the
PATH) which really helps with these builders since most patches only
change a few files.

I'll sent you the buildbot-worker setup and passwords offlist.

Cheers,

Mark
-------------- next part --------------
A non-text attachment was scrubbed...
Name: p
Type: text/x-patch
Size: 10500 bytes
Desc: 
URL: <https://sourceware.org/pipermail/buildbot/attachments/20260603/ccf240d4/attachment.bin>


More information about the Buildbot mailing list