From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org,
Clayton Shotwell <clayton.shotwell@collins.com>,
Fabrice Fontaine <fontaine.fabrice@gmail.com>,
Giulio Benetti <giulio.benetti@benettiengineering.com>,
Norbert Lange <nolange79@gmail.com>
Subject: Re: [Buildroot] [PATCH v2 1/1] package/libcap-ng: bump version to 0.9.3
Date: Thu, 23 Apr 2026 22:06:34 +0200 [thread overview]
Message-ID: <dbd41814b2d0fedf7f37c9bd619df2b7@free.fr> (raw)
In-Reply-To: <20260420165548.2998453-1-bernd@kuhls.net>
On 20/04/2026 18:55, Bernd Kuhls wrote:
> https://github.com/stevegrubb/libcap-ng/blob/v0.9.3/ChangeLog
>
> The source tarball is not distributed on the project site anymore so we
> switch to the github helper and need to enable autoreconf.
>
> Added dependency to BR2_TOOLCHAIN_HAS_SYNC_4 to fix a build error:
>
> /home/bernd/buildroot/test-libcap/bootlin-sparc-uclibc/host/opt/ext-toolchain/bin/../lib/gcc/sparc-buildroot-linux-uclibc/14.3.0/../../../../sparc-buildroot-linux-uclibc/bin/ld:
> ../src/.libs/libcap-ng.so: undefined reference to
> `__sync_bool_compare_and_swap_4'
>
> due to this upstream commit added in version 0.9.2:
> https://github.com/stevegrubb/libcap-ng/commit/ba2e9e03199541b1c07f3e925ffc5b23774bd18f
>
> Added _POST_EXTRACT_HOOKS and dependency to host-pkgconf to fix
> autoreconf errors.
>
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
Applied to master, thanks.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-04-23 20:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-20 16:55 [Buildroot] [PATCH v2 1/1] package/libcap-ng: bump version to 0.9.3 Bernd Kuhls
2026-04-23 20:06 ` Julien Olivain via buildroot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-04-17 7:59 Bernd Kuhls
2026-04-19 21:08 ` Julien Olivain via buildroot
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=dbd41814b2d0fedf7f37c9bd619df2b7@free.fr \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.net \
--cc=clayton.shotwell@collins.com \
--cc=fontaine.fabrice@gmail.com \
--cc=giulio.benetti@benettiengineering.com \
--cc=ju.o@free.fr \
--cc=nolange79@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