From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: Romain Naour <romain.naour@gmail.com>,
Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/2] package/htop: fix build failure due to gcc bug 109809
Date: Tue, 6 Aug 2024 22:28:43 +0200 [thread overview]
Message-ID: <20240806222843.58ae10a0@windsurf> (raw)
In-Reply-To: <20240205172327.2537523-2-giulio.benetti@benettiengineering.com>
Hello Giulio,
On Mon, 5 Feb 2024 18:23:27 +0100
Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:
> The htop package exhibits gcc bug 109809 when built for the RISCV64
> architecture with optimization enabled, which causes a build failure.
>
> As done for other packages in Buildroot work around this gcc bug by
> setting optimization to -O0 if BR2_TOOLCHAIN_HAS_GCC_BUG_109809=y.
>
> Fixes:
> still not happened. It shows up while building under docker-run this
> pending patch-set:
> https://patchwork.ozlabs.org/project/buildroot/list/?series=384841
Unfortunately, this is not very useful, because this patch series is no
longer there. I just did a build like this:
BR2_riscv=y
BR2_TOOLCHAIN_EXTERNAL=y
BR2_INIT_NONE=y
BR2_SYSTEM_BIN_SH_NONE=y
# BR2_PACKAGE_BUSYBOX is not set
BR2_PACKAGE_HTOP=y
# BR2_TARGET_ROOTFS_TAR is not set
it uses gcc 13.x, on RISC-V 64-bit and it builds fine.
So for issues that have not been reported in the autobuilders, what is
good is to provide a defconfig that allows to reproduce the problem, so
that we can reproduce it again in the future.
Could you look into this, and submit a v2 if relevant?
Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-08-06 20:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 17:23 [Buildroot] [PATCH 1/2] toolchain: introduce BR2_TOOLCHAIN_HAS_GCC_BUG_109809 Giulio Benetti
2024-02-05 17:23 ` [Buildroot] [PATCH 2/2] package/htop: fix build failure due to gcc bug 109809 Giulio Benetti
2024-08-06 20:28 ` Thomas Petazzoni via buildroot [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240806222843.58ae10a0@windsurf \
--to=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=romain.naour@gmail.com \
--cc=thomas.de_schampheleire@nokia.com \
--cc=thomas.petazzoni@bootlin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox