From: Peter Korsgaard <peter@korsgaard.com>
To: Arnout Vandecappelle via buildroot <buildroot@buildroot.org>
Cc: Bernd Kuhls <bernd.kuhls@t-online.de>,
Marcin Bis <marcin@bis.org.pl>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Gwenhael Goavec-Merou <gwenhael.goavec-merou@trabucayre.com>,
Fabrice Fontaine <fabrice.fontaine@orange.com>,
Maxim Kochetkov <fido_max@inbox.ru>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Fabio Urquiza <fabiorush@gmail.com>,
Romain Naour <romain.naour@gmail.com>,
Fabrice Fontaine <fontaine.fabrice@gmail.com>
Subject: Re: [Buildroot] [PATCH v2] package/boost: Boost.Atomic needs atomic intrinsics
Date: Fri, 09 Aug 2024 21:34:04 +0200 [thread overview]
Message-ID: <87sevdo5hv.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <3f2f76fc-6474-4054-8a60-a8223e3b0cd0@mind.be> (Arnout Vandecappelle via buildroot's message of "Sat, 13 Jul 2024 11:36:26 +0200")
>>>>> "Arnout" == Arnout Vandecappelle via buildroot <buildroot@buildroot.org> writes:
> On 23/12/2022 14:34, Michael Nosthoff via buildroot wrote:
>> From: Michael <buildroot@heine.tech>
>> similar to previous problems with nios2 and not-available atomic
>> ints
>> the build for Boost.Atomics also fails for ARC Targets which don't
>> have the ATOMICS_EXT flag set.
>> according to [0] "Boost.Atomic has a hard requirement of the native
>> atomic operations on bytes". The same tests mentioned there fail for
>> ARC.
> Based on that comment, the option
> BR2_TOOLCHAIN_SUPPORTS_ALWAYS_LOCKFREE_ATOMIC_INTS was introduced. So
> that one should have been used instead.
>> so introduce a dependency on BR2_ARC_ATOMIC_EXT for BR2_arc.
>> add depends clause for all packages using boost-atomic/filesystem.
>> Fixes:
>> http://autobuild.buildroot.net/results/4ca54a85672d7b9328b1909b457e548c6032a493
>> [0]
>> https://github.com/boostorg/atomic/issues/42#issuecomment-734130348
>> Signed-off-by: Michael Nosthoff <buildroot@heine.tech>
> I changed the entire patch to this:
> diff --git a/toolchain/Config.in b/toolchain/Config.in
> index 1aa17cbfbd..8acdc62fc2 100644
> --- a/toolchain/Config.in
> +++ b/toolchain/Config.in
> @@ -94,6 +94,7 @@ config BR2_TOOLCHAIN_SUPPORTS_ALWAYS_LOCKFREE_ATOMIC_INTS
> depends on !BR2_ARM_CPU_ARMV5
> depends on !BR2_sparc_v8
> depends on !BR2_m68k_cf5208
> + depends on !(BR2_arc && !BR2_ARC_ATOMIC_EXT)
> # GCC uses thunk functions to adjust the 'this' pointer when calling
> # C++ member functions in classes derived with multiple inheritance.
> and applied to master, thanks.
Committed to 2024.02.x and 2024.05.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-08-09 19:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 13:34 [Buildroot] [PATCH v2] package/boost: Boost.Atomic needs atomic intrinsics Michael Nosthoff via buildroot
2024-07-13 9:36 ` Arnout Vandecappelle via buildroot
2024-08-09 19:34 ` Peter Korsgaard [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=87sevdo5hv.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=bernd.kuhls@t-online.de \
--cc=brgl@bgdev.pl \
--cc=buildroot@buildroot.org \
--cc=fabiorush@gmail.com \
--cc=fabrice.fontaine@orange.com \
--cc=fido_max@inbox.ru \
--cc=fontaine.fabrice@gmail.com \
--cc=gwenhael.goavec-merou@trabucayre.com \
--cc=marcin@bis.org.pl \
--cc=romain.naour@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.