All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Baruch Siach via buildroot <buildroot@buildroot.org>
Cc: buildroot@busybox.net, Matt Weber <matthew.weber@collins.com>
Subject: Re: [Buildroot] [PATCH] package/libcurl: fix build when !BR2_TOOLCHAIN_HAS_SYNC_1
Date: Fri, 12 Aug 2022 17:11:19 +0200	[thread overview]
Message-ID: <87fsi1ijjc.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <a91e52dc20742c251ac5fdc6ada81c499dfc1705.1658419808.git.baruch@tkos.co.il> (Baruch Siach via buildroot's message of "Thu, 21 Jul 2022 19:10:08 +0300")

>>>>> "Baruch" == Baruch Siach via buildroot <buildroot@buildroot.org> writes:

 > On platform that do not provide __atomic_exchange_1(), and when
 > libatomic is not available (e.g., threads support disabled) link of
 > libcurl.so fails. To solve this use an indirect way to make HAVE_ATOMIC
 > undefined. Add an upstream patch for checking the stdatomic.h header,
 > and seed the 'no' answer.

 > Fixes:
 > http://autobuild.buildroot.net/results/8f695d4dbb91cfde8e93ab38e837b0a0042b986b/
 > http://autobuild.buildroot.net/results/3b4712b0ace52da1650e88cdaafb6a20be135464/

 > Cc: Matt Weber <matthew.weber@collins.com>
 > Signed-off-by: Baruch Siach <baruch@tkos.co.il>

Committed to 2022.05.x and 2022.02.x, thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2022-08-12 15:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-21 16:10 [Buildroot] [PATCH] package/libcurl: fix build when !BR2_TOOLCHAIN_HAS_SYNC_1 Baruch Siach via buildroot
2022-07-23 11:49 ` Arnout Vandecappelle
2022-08-12 15:11 ` 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=87fsi1ijjc.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=buildroot@busybox.net \
    --cc=matthew.weber@collins.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.