Re: A GNU Binutils wiki

[Nick Clifton <nickc@redhat.com>]

Hi Mark,

>>> How are the current code snapshots created?
>>
>> I think that there is a cron job on sourceware that creates the snapshots.
> 
> I can find the gdbadmin cron job that creates gdb snapshots, but it
> looks like you create the binutils snapshots by hand and upload them
> to https://sourceware.org/pub/binutils/snapshots/

Ah - yes - that does indeed appear to be the case.  I think that in the
past there was a cron job that would create daily snapshots, but I guess
that it went away.

> It would be nice to automate this a bit more either with a real
> cronjob or a specific buildbot worker.

I would be happy for that to happen.  Can I just say "pretty please" ?
or do you need me to do something ?


> About
> 
>    12. Build various different toolchains, test them and nag
>        maintainers to fix any testsuite failures for their
>        architectures...
> 
> Which toolchains/architectures are that? Are any of them missing from:
> https://builder.sourceware.org/buildbot/#/builders?tags=binutils

Lots!  I build about 100 different combinations in my local test farm.
Most are slightly obscure configurations or targets however, so I would
not worry too much about them.  There are a few that would be nice to
see added to your buildbot farm however, should you have the capacity:

   aarch64-linux-gnu
   mipsel-linux-gnu
   riscv64-elf


>>> We can automate both and publish them on a special buildbot worker
>>> under something like snapshots.sourceware.org/bintuils to keep them
>>> current and so everybody can immediately see how the documentation
>>> looks.
>>
>> That would be nice.  Would it involve taking up a lot of disk space ?
>> (Ie for how long would these snapshots last ?)
> 
> binutils snapshots are ~24MB, documentation ~18MB. So if we do one a
> day that is ~1GB a month. And since it looks like you recently added
> the option to create reproducible tarballs we don't really need to
> keep all of them since people could recreate them from a git checkout.

That makes sense.  So if you are willing to make it happen that would be
grand.

Cheers
   Nick