From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Nicolas Cavallari <nicolas.cavallari@green-communications.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v3 1/2] package/libgit2: link with -latomic if needed
Date: Sun, 14 Aug 2022 12:06:15 +0200 [thread overview]
Message-ID: <20220814120615.24bfbaaa@windsurf> (raw)
In-Reply-To: <20220812145652.24342-1-nicolas.cavallari@green-communications.fr>
On Fri, 12 Aug 2022 16:56:51 +0200
Nicolas Cavallari <nicolas.cavallari@green-communications.fr> wrote:
> libgit2 is currently a library without any reverse dependencies so the
> missing atomic symbols do not cause build failures yet.
>
> libgit2 uses the atomics intrinsics on gcc >= 4.7 and the sync
> intrinsics on previous gcc versions. Since gcc 4.9 is the new
> minimum, ignore the sync intrinsics requirements.
>
> The next version of libgit2 will also build a binary, which will
> expose the problem.
>
> Signed-off-by: Nicolas Cavallari <nicolas.cavallari@green-communications.fr>
>
> ---
> v3: first series with this patch
> ---
> package/libgit2/libgit2.mk | 5 +++++
> 1 file changed, 5 insertions(+)
Applied to master, thanks. I will also cherry-pick in next.
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-08-14 10:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 14:56 [Buildroot] [PATCH v3 1/2] package/libgit2: link with -latomic if needed Nicolas Cavallari
2022-08-12 14:56 ` [Buildroot] [PATCH v3 2/2] package/libgit2: bump to 1.5.0 Nicolas Cavallari
2022-08-14 10:07 ` Thomas Petazzoni via buildroot
2022-08-14 10:06 ` 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=20220814120615.24bfbaaa@windsurf \
--to=buildroot@buildroot.org \
--cc=nicolas.cavallari@green-communications.fr \
--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.