From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Pierre-Jean Texier <texier.pj2@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/numactl: link with -latomic if needed
Date: Thu, 3 Nov 2022 22:12:44 +0100 [thread overview]
Message-ID: <20221103221244.17f40c1a@windsurf> (raw)
In-Reply-To: <20221102123500.311904-1-fontaine.fabrice@gmail.com>
On Wed, 2 Nov 2022 13:35:00 +0100
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> Fix the following build failure raised since bump to version 2.0.16 in
> commit e9bc980d93a189a16e7320bd254b906c87ca9f87:
>
> /nvmedata/autobuild/instance-7/output-1/per-package/numactl/host/bin/../lib/gcc/sparc-buildroot-linux-uclibc/10.4.0/../../../../sparc-buildroot-linux-uclibc/bin/ld: ./.libs/libnuma.a(libnuma.o): in function `numa_police_memory':
> libnuma.c:(.text+0xe28): undefined reference to `__atomic_fetch_and_1'
>
> Fixes:
> - http://autobuild.buildroot.org/results/a92c1c60518d3fe08f3f808f9cc812031e85a4e9
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> ...01-link-with-latomic-if-needed-again.patch | 41 +++++++++++++++++++
> package/numactl/numactl.mk | 2 +
> 2 files changed, 43 insertions(+)
> create mode 100644 package/numactl/0001-link-with-latomic-if-needed-again.patch
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-11-03 21:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 12:35 [Buildroot] [PATCH 1/1] package/numactl: link with -latomic if needed Fabrice Fontaine
2022-11-02 20:02 ` Thomas Petazzoni via buildroot
2022-11-02 22:14 ` Fabrice Fontaine
2022-11-03 21:12 ` 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=20221103221244.17f40c1a@windsurf \
--to=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=texier.pj2@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox