Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Angelo Compagnucci <angelo.compagnucci@gmail.com>
To: buildroot@buildroot.org
Cc: Fabrice Fontaine <fontaine.fabrice@gmail.com>,
	Joseph Kogut <joseph.kogut@gmail.com>,
	Romain Naour <romain.naour@gmail.com>,
	Daniel Lang <dalang@gmx.at>,
	Valentin Korenblit <valentinkorenblit@gmail.com>
Subject: Re: [Buildroot] [PATCH 1/1] package/llvm-project/clang: link with -latomic if needed
Date: Sat, 21 Nov 2026 19:08:55 +0100	[thread overview]
Message-ID: <20261121180855.3595157-1-angelo.compagnucci@gmail.com> (raw)
In-Reply-To: <20231208231413.656734-1-fontaine.fabrice@gmail.com>

Hi Fabrice,

On 09/12/23 00:14, Fabrice Fontaine wrote:
> FileManager.cpp:(.text._ZN4llvm17TrackingStatisticppEv[_ZN4llvm17TrackingStatisticppEv]+0x20): undefined reference to `__atomic_fetch_add_8

I think this patch can be dropped: the problem is fixed upstream.

LLVM commit 20132d8eaa68 ("Link libclangBasic against libatomic when
necessary.") links libclangBasic, where FileManager.cpp is, with
libatomic when the target needs it. It is in LLVM 16.0.0 and later.

Buildroot has it since commit e29dae109a21 ("package/llvm-project: bump
to version 20.1.5"), and the autobuilder shows no clang failure after
it.

Not Applicable: https://patchwork.buildroot.org/project/buildroot/patch/20231208231413.656734-1-fontaine.fabrice@gmail.com/
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2026-11-21 18:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-08 23:14 [Buildroot] [PATCH 1/1] package/llvm-project/clang: link with -latomic if needed Fabrice Fontaine
2026-11-21 18:08 ` Angelo Compagnucci [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=20261121180855.3595157-1-angelo.compagnucci@gmail.com \
    --to=angelo.compagnucci@gmail.com \
    --cc=buildroot@buildroot.org \
    --cc=dalang@gmx.at \
    --cc=fontaine.fabrice@gmail.com \
    --cc=joseph.kogut@gmail.com \
    --cc=romain.naour@gmail.com \
    --cc=valentinkorenblit@gmail.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