From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: "wangmy" <wangmy@fujitsu.com>
Cc: <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] xcb-proto: upgrade 1.15 -> 1.15.2
Date: Wed, 22 Jun 2022 15:54:55 +0200 [thread overview]
Message-ID: <20220622155455.47ed5d6f@booty> (raw)
In-Reply-To: <1655884130-22843-5-git-send-email-wangmy@fujitsu.com>
Hello wangmy,
On Wed, 22 Jun 2022 15:48:50 +0800
"wangmy" <wangmy@fujitsu.com> wrote:
> Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
This patch triggers autobuilder failures in libxcb-native do_configure:
| checking for check >= 0.9.6... no
| checking for xcb-proto >= 1.14... no
| configure: error: Package requirements (xcb-proto >= 1.14) were not met:
|
| Variable 'libdir' not defined in '/home/pokybuild/yocto-worker/poky-tiny/build/build/tmp/work/x86_64-linux/libxcb-native/1.15-r0/recipe-sysroot-native/usr/share/pkgconfig/xcb-proto.pc'
Some logs:
https://autobuilder.yoctoproject.org/typhoon/#/builders/15/builds/5675/steps/11/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/50/builds/5419/steps/11/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/75/builds/5384/steps/11/logs/stdio
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2022-06-22 13:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 7:48 [OE-core] [PATCH] libproxy: upgrade 0.4.17 -> 0.4.18 Wang Mingyu
2022-06-22 7:48 ` [OE-core] [PATCH] python3-dbusmock: upgrade 0.27.5 -> 0.28.0 Wang Mingyu
2022-06-22 7:48 ` [OE-core] [PATCH] sbc: upgrade 1.5 -> 2.0 Wang Mingyu
2022-06-22 7:48 ` [OE-core] [PATCH] strace: upgrade 5.17 -> 5.18 Wang Mingyu
2022-06-22 7:48 ` [OE-core] [PATCH] xcb-proto: upgrade 1.15 -> 1.15.2 Wang Mingyu
2022-06-22 13:54 ` Luca Ceresoli [this message]
2022-06-23 0:38 ` wangmy
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=20220622155455.47ed5d6f@booty \
--to=luca.ceresoli@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=wangmy@fujitsu.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