On Fri, Aug 22, 2025 at 10:12:19PM +0100, Adriano Carvalho wrote:
> On Fri, 22 Aug 2025 at 01:04, Adriano Carvalho
> <adrianocarvalho...@gmail.com> wrote:
> >
> > On Wed, 20 Aug 2025 at 22:08, Heinrich Schuchardt <xypron.g...@gmx.de> 
> > wrote:
> > >
> > > On 11.08.25 01:37, Adriano Carvalho wrote:
> > > > Signed-off-by: Adriano Carvalho <adrianocarvalho...@gmail.com>
> > > > ---
> > > >   tools/buildman/buildman.rst | 3 ++-
> > > >   1 file changed, 2 insertions(+), 1 deletion(-)
> > > >
> > > > diff --git a/tools/buildman/buildman.rst b/tools/buildman/buildman.rst
> > > > index d5d22732088..7944adcd867 100644
> > > > --- a/tools/buildman/buildman.rst
> > > > +++ b/tools/buildman/buildman.rst
> > > > @@ -478,7 +478,8 @@ Setting up
> > > >
> > > >      At the time of writing, U-Boot has these architectures:
> > > >
> > > > -      arc, arm, m68k, microblaze, mips, nios2, powerpc, sandbox, sh, 
> > > > x86, xtensa
> > > > +      arc, arm, m68k, microblaze, mips, nios2, powerpc, riscv, 
> > > > sandbox, sh, x86,
> > > > +      xtensa
> > >
> > > The output examples above this line should also be updated to show RISC-V.
> >
> > Do you mean what's under "Check the available toolchains"?
> >
> > To reproduce, I would need to install quite a few toolchains. If
> > anyone already has all those toolchains they could just send me the
> > output. Do you know someone who can do that? Can you do that? Or
> > should I just install all those toolchains and reproduce?
> > [...]
> 
> With docker.io/trini/u-boot-gitlab-ci-runner:jammy-20250714-25Jul2025,
> I got the following:
> 
> $ ./tools/buildman/buildman --list-tool-chains
> List of available toolchains (17):
> aarch64   : /opt/gcc-14.2.0-nolibc/aarch64-linux/bin/aarch64-linux-gcc
> arc       : /opt/gcc-14.2.0-nolibc/arc-linux/bin/arc-linux-gcc
> arm       : /opt/gcc-14.2.0-nolibc/arm-linux-gnueabi/bin/arm-linux-gnueabi-gcc
> c89       : /usr/bin/c89-gcc
> c99       : /usr/bin/c99-gcc
> i386      : /opt/gcc-14.2.0-nolibc/i386-linux/bin/i386-linux-gcc
> m68k      : /opt/gcc-14.2.0-nolibc/m68k-linux/bin/m68k-linux-gcc
> microblaze: /opt/gcc-14.2.0-nolibc/microblaze-linux/bin/microblaze-linux-gcc
> mips      : /opt/gcc-14.2.0-nolibc/mips-linux/bin/mips-linux-gcc
> nios2     : /opt/gcc-14.2.0-nolibc/nios2-linux/bin/nios2-linux-gcc
> powerpc   : /opt/gcc-14.2.0-nolibc/powerpc-linux/bin/powerpc-linux-gcc
> riscv32   : /opt/gcc-14.2.0-nolibc/riscv32-linux/bin/riscv32-linux-gcc
> riscv64   : /opt/gcc-14.2.0-nolibc/riscv64-linux/bin/riscv64-linux-gcc
> sandbox   : /usr/bin/gcc
> sh2       : /opt/gcc-14.2.0-nolibc/sh2-linux/bin/sh2-linux-gcc
> x86_64    : /opt/gcc-14.2.0-nolibc/x86_64-linux/bin/x86_64-linux-gcc
> xtensa    : /opt/2020.07/xtensa-dc233c-elf/bin/xtensa-dc233c-elf-gcc
> 
> Compare to the original:
> - a few architectures are missing (e.g., alpha, am33_2.0, bfin, frv, h8300)
> - No "Scanning for tool chains" at the beginning
> - No "Tool chain test"
> 
> Have the missing architectures been removed since? All those in the
> arch folder and some more are listed.
> 
> Has the output for Buildman changed to not include those lines?

There's a few things well out date at this point:
- The output from '--fetch-arch list' shows what can be downloaded from
  kernel.org. Keep in mind these are public toolchains, for the Linux
  kernel and are also fine for us. That's why it lists so many more.
- The section "Check the available toolchains" should be replaced with
  modern output, and you need to pass -v to get such verbose details now
  rather than simply a list of what would be used.
- The section "Install new toolchains if needed" should be replaced with
  output from using an architecture U-Boot still supports such as arm64
  or riscv.
- The "toolchain-alias" parts don't list what aliases one needs and
  since 'riscv = riscv64' is needed, rephrasing that earlier part of the
  document should be done too.

Thanks for working on this area!

-- 
Tom

Attachment: signature.asc
Description: PGP signature

Reply via email to