All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Antonin Godard" <antonin.godard@bootlin.com>
To: <liuyd.fnst@fujitsu.com>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] libcap-ng upgrade depends problem
Date: Wed, 14 Jan 2026 14:18:15 +0100	[thread overview]
Message-ID: <DFOCB6REM2EQ.2O1LSJOYV18PG@bootlin.com> (raw)
In-Reply-To: <DFOC9XA7U7FI.N5FIE3FOCY5E@bootlin.com>

On Wed Jan 14, 2026 at 2:16 PM CET, Antonin Godard via lists.openembedded.org wrote:
> Hi,
>
> On Tue Jan 13, 2026 at 8:01 AM CET, Yiding Liu (Fujitsu) via lists.openembedded.org wrote:
>> Hi All
>>
>> I tryed to upgrade libcap-ng from 0.8.5 to 0.9, but there is PKG_CHECK error during do_configure
>>
>> | checking for gawk... (cached) gawk
>> | ../sources/libcap-ng-0.9/configure: line 14862: syntax error near unexpected token `LIBBPF,libbpf,'
>> | ../sources/libcap-ng-0.9/configure: line 14862: `PKG_CHECK_MODULES(LIBBPF,libbpf,'
>> | NOTE: The following config.log files may provide further information.
>> | NOTE: /mnt/contribution/build_image/tmp/work/x86_64-linux/libcap-ng-native/0.9/build/config.log
>> | ERROR: configure failed
>> | WARNING: exit code 1 from a shell command.
>>
>> It seems like libbpf is needed as dependence.
>> But libbpf is in meta-oe not in oe-core.
>> Does any one has experience about this problem?
>
> This probably means that the libbpf recipe needs to be moved from meta-oe
> to openembedded-core. Can you send a series that adds this recipe first, and
> then updates libcap-ng?

Apologies, I just realized you sent a follow-up patch on this, so you can ignore
my email.

Antonin

-- 
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



  reply	other threads:[~2026-01-14 13:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-13  7:01 libcap-ng upgrade depends problem Yiding Liu (Fujitsu)
2026-01-14 13:16 ` [OE-core] " Antonin Godard
2026-01-14 13:18   ` Antonin Godard [this message]
2026-01-15  1:25     ` 回复: " Yiding Liu (Fujitsu)

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=DFOCB6REM2EQ.2O1LSJOYV18PG@bootlin.com \
    --to=antonin.godard@bootlin.com \
    --cc=liuyd.fnst@fujitsu.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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.