From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/gnutls: fix build on sparc
Date: Sun, 04 Aug 2019 22:11:49 +0200 [thread overview]
Message-ID: <877e7sr8qi.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20190715163608.1903-1-fontaine.fabrice@gmail.com> (Fabrice Fontaine's message of "Mon, 15 Jul 2019 18:36:08 +0200")
>>>>> "Fabrice" == Fabrice Fontaine <fontaine.fabrice@gmail.com> writes:
> gnutls source code uses the C++11 <atomic> functionality since
> https://github.com/gnutls/gnutls/commit/7978a733460f92b31033affd0e487c86d66c643d,
> which internally is implemented using the __atomic_*() gcc built-ins
> On certain architectures, the __atomic_*() built-ins are implemented in
> the libatomic library that comes with the rest of the gcc runtime. Due
> to this, code using <atomic> might need to link against libatomic,
> otherwise one hits build issues such as:
> ../lib/.libs/libgnutls.so: undefined reference to `__atomic_fetch_sub_4'
> on an architecture like SPARC.
> To solve this, link against libatomic if BR2_PACKAGE_HAS_LIBATOMIC is set.
> This fix gnutls build failures as well as cups, gnupg and libmicrohttpd
> Fixes:
> - http://autobuild.buildroot.org/results/1c7541fc6ac4b52d1dfe02a9a7d61db90f4521eb
> - http://autobuild.buildroot.org/results/42c8803b98e38ebd48870fe6b1a20a1d6c351e5f
> - http://autobuild.buildroot.org/results/a1e96d02d41f7fec0f5327f65fb34405f963a1e9
> - http://autobuild.buildroot.org/results/59c92706457a9da29dd44425e546a7c80c18b454
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Committed to 2019.02.x and 2019.05.x, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2019-08-04 20:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-15 16:36 [Buildroot] [PATCH 1/1] package/gnutls: fix build on sparc Fabrice Fontaine
2019-07-17 6:39 ` Thomas Petazzoni
2019-08-04 20: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=877e7sr8qi.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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