From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Robert Yang <liezhi.yang@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] libarchive: set CLEANBROKEN
Date: Tue, 21 Apr 2015 08:39:03 +0100 [thread overview]
Message-ID: <1429601943.26983.74.camel@linuxfoundation.org> (raw)
In-Reply-To: <78a8e0beb1dd78a8461b994816267ec8848b2ca7.1427262046.git.liezhi.yang@windriver.com>
On Tue, 2015-03-24 at 22:41 -0700, Robert Yang wrote:
> Errors when rebuild:
> checking for xml2-config... /path/to/tmp/sysroots/qemux86-64/usr/bin/crossscripts/xml2-config
> checking for xmlInitParser in -lxml2... no
> configure: error: in `/path/to/tmp/work/core2-64-poky-linux/libarchive/3.1.2-r0/libarchive-3.1.2':
> configure: error: Missing xml2 library
>
> Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
> ---
> .../libarchive/libarchive_3.1.2.bb | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/meta/recipes-extended/libarchive/libarchive_3.1.2.bb b/meta/recipes-extended/libarchive/libarchive_3.1.2.bb
> index 96e2d50..2ac8c5e 100644
> --- a/meta/recipes-extended/libarchive/libarchive_3.1.2.bb
> +++ b/meta/recipes-extended/libarchive/libarchive_3.1.2.bb
> @@ -7,6 +7,8 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=b4e3ffd607d6686c6cb2f63394370841"
>
> DEPENDS = "e2fsprogs-native"
>
> +CLEANBROKEN = "1"
> +
> PACKAGECONFIG ?= "libxml2 zlib bz2"
>
> PACKAGECONFIG_append_class-target = "\
I just looked into this I will explain why this worries me. We patch
libarchive to remove the reference to xml2-config in SRC_URI. For this
error to appear, the patch must have been removed.
The question is therefore why does it get removed and why isn't that an
error? Does the CVE patch get removed too?
FWIW, "bitbake libarchive -c configure -f" does not reproduce the error
and the clean broken is therefore a workaround/hack.
Actually, I just found what does break it is "bitbake libarchive -C
unpack". Why? Running "make clean" triggers configure to run again since
after unpack, the configure timestamp is more recent that config.status.
So to fix this, we just need to touch config.status (if it exists)
before running make clean. We should probably do this in the autotools
class.
Cheers,
Richard
next prev parent reply other threads:[~2015-04-21 7:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-25 5:41 [PATCH 0/1] libarchive: set CLEANBROKEN Robert Yang
2015-03-25 5:41 ` [PATCH 1/1] " Robert Yang
2015-04-21 7:39 ` Richard Purdie [this message]
2015-04-21 9:11 ` Robert Yang
2015-04-30 5:43 ` Robert Yang
2015-05-05 15:44 ` Burton, Ross
2015-04-10 1:41 ` [PATCH 0/1] " Robert Yang
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=1429601943.26983.74.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=liezhi.yang@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox