From: Peter Korsgaard <peter@korsgaard.com>
To: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Romain Naour <romain.naour@smile.fr>,
Giulio Benetti <giulio.benetti@benettiengineering.com>,
Romain Naour <romain.naour@gmail.com>
Subject: Re: [Buildroot] [PATCH] toolchain/Config.in: refine BR2_TOOLCHAIN_HAS_LIBQUADMATH definition
Date: Tue, 25 Aug 2026 10:34:31 +0200 [thread overview]
Message-ID: <87fr02y4x4.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20260823191926.2684260-1-thomas.petazzoni@bootlin.com> (Thomas Petazzoni via buildroot's message of "Sun, 23 Aug 2026 21:19:25 +0200")
>>>>> "Thomas" == Thomas Petazzoni via buildroot <buildroot@buildroot.org> writes:
> In commit a2380157f6688c5c065fa19060a2c33145bab95b ("toolchain: enable
> libquadmath for PowerPC with VSX"), the definition of
> BR2_TOOLCHAIN_HAS_LIBQUADMATH has been extended to also be true when
> BR2_POWERPC_CPU_HAS_VSX.
> However, practical experiments show that when 64-bit VSX-capable cores
> are used in 32-bit mode, libquadmath is not built by GCC, causing
> build failures:
> cp: cannot stat
> '/home/autobuild/autobuild/instance-3/output-1/host/powerpc-buildroot-linux-musl/lib*/libquadmath*':
> No such file or directory
> We did an extensive testing, building the 27 combinations of:
> - GCC versions: 14, 15, 16
> - C library: glibc, uclibc, musl
> - PowerPC 32-bit, PowerPC 64-bit, PowerPC 64-bit little endian
Wow ;)
Committed, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-08-25 8:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-23 19:19 [Buildroot] [PATCH] toolchain/Config.in: refine BR2_TOOLCHAIN_HAS_LIBQUADMATH definition Thomas Petazzoni via buildroot
2026-08-25 8:34 ` Peter Korsgaard [this message]
2026-09-04 12:18 ` Thomas Perale via buildroot
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=87fr02y4x4.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=romain.naour@gmail.com \
--cc=romain.naour@smile.fr \
--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