[Buildroot] Toolchain issues on multiple architectures

From: Alistair Francis <alistair23@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Toolchain issues on multiple architectures
Date: Thu, 10 Sep 2020 16:17:46 -0700	[thread overview]
Message-ID: <CAKmqyKOSLH-VJc-72eyn=O_-nNwneb3Wqcm-Yb1qt6TzXdDS0g@mail.gmail.com> (raw)
In-Reply-To: <20200910120536.2431494d@windsurf.hq.k.grp>

On Thu, Sep 10, 2020 at 3:05 AM Thomas Petazzoni
<thomas.petazzoni@bootlin.com> wrote:
>
> Hello,
>
> As part of the https://toolchains.bootlin.com project, I've tried to
> rebuild 175 toolchains on top of Buildroot 2020.08, and encountered a
> number of failures, which are summarized below.
>
> Damien, Alistair: there is an issue with the RISC-V 32-bit toolchain.
> Could you have a look, and tell us if you have some suggestions?
>
> ARC maintainers: all ARC toolchains are failing to build due to the use
> of a recent gdb where gdbserver was moved to the top-level. However, it
> doesn't seem to be that easy to build just gdbserver in those recent
> gcc versions. I have posted a question about this on the gdb@ mailing
> list: https://sourceware.org/pipermail/gdb/2020-September/048888.html.
>
> Matt, there are some PowerPC64 build issues as well. Have you ever seen
> them, do you have any hints?
>
> There are also issues on other platforms, AArch64, x86-64, Microblaze, etc.
>
> See below the full details:
>
> AArch64
> =======
>
> - aarch64--musl--stable
>   https://gitlab.com/bootlin/toolchains-builder/-/jobs/729359478
>
>   build failure while building gdb, with redefinitions of C library
>   structures
>
> ARC
> ===
>
> All configurations are failing
>
> - https://gitlab.com/bootlin/toolchains-builder/-/jobs/729359481
> - https://gitlab.com/bootlin/toolchains-builder/-/jobs/729359482
> - https://gitlab.com/bootlin/toolchains-builder/-/jobs/729359483
> - https://gitlab.com/bootlin/toolchains-builder/-/jobs/729359484
> - https://gitlab.com/bootlin/toolchains-builder/-/jobs/729359485
> - https://gitlab.com/bootlin/toolchains-builder/-/jobs/729359487
>
> Issue is caused by the recent version of gdb, where gdbserver has been
> moved from gdb/gdbserver/ to gdbserver/. However, the story is not so
> simple: you can't simply go in gdbserver/ and run ./configure from it,
> that doesn't work anymore.
>
> ARMv7-M
> =======
>
> - https://gitlab.com/bootlin/toolchains-builder/-/jobs/729359529
>
> Build failures while building afboot-stm32, most likely due to gcc
> 10.x emitting calls to memcpy().
>
> Fixed by:
>
> https://patchwork.ozlabs.org/project/buildroot/patch/20200910094608.1251382-1-thomas.petazzoni at bootlin.com/
>
> Microblaze
> ==========
>
> All the "bleeding edge" configurations fail to boot under Qemu.
>
> - https://gitlab.com/bootlin/toolchains-builder/-/jobs/729359536
> - https://gitlab.com/bootlin/toolchains-builder/-/jobs/729359538
> - https://gitlab.com/bootlin/toolchains-builder/-/jobs/729359540
> - https://gitlab.com/bootlin/toolchains-builder/-/jobs/729359542
> - https://gitlab.com/bootlin/toolchains-builder/-/jobs/729359544
> - https://gitlab.com/bootlin/toolchains-builder/-/jobs/729359546
>
> PowerPC64 (big and little endian) Power 8
> =========================================
>
> Both the glibc stable and bleeding edge are failing to build libstdc++
> in host-gcc-final. Interesingly, the musl configurations work fine.
>
> - https://gitlab.com/bootlin/toolchains-builder/-/jobs/729359625
> - https://gitlab.com/bootlin/toolchains-builder/-/jobs/729359626
> - https://gitlab.com/bootlin/toolchains-builder/-/jobs/729359621
> - https://gitlab.com/bootlin/toolchains-builder/-/jobs/729359622
>
> RISC-V ILP32D
> =============
>
> The only configuration (glibc) fails to build in glibc, with a bunch
> of:
>
> ../sysdeps/unix/sysv/linux/riscv/sysdep.h:120:31: error: '__NR_futex' undeclared (first use in this function); did you mean '__futex'?
>   120 | #define SYS_ify(syscall_name) __NR_##syscall_name
>
> - https://gitlab.com/bootlin/toolchains-builder/-/jobs/729359659

Do you have any steps to reproduce this?

I tried `make qemu_riscv32_virt_defconfig; make` in buildroot and I
don't see any failures.

I tried `./build.sh riscv32-ilp32d--glibc--bleeding-edge testing
buildroot-toolchains/toolchains.bootlin.com-2020.08 2020.08-1` in the
toolchains-builder, but I'm missing
frags/riscv32-ilp32d--glibc--bleeding-edge.config.

I then tried `frags/riscv32-ilp32d--glibc--bleeding-edge.config` but
it doesn't generate a RV32 frag.

What am I missing?

Alistair