From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/3] acl: Make it compatible with externalsrc
Date: Tue, 25 Sep 2018 09:17:12 +0000 [thread overview]
Message-ID: <a042a2e4c0464b4d81e4ada72f76fe77@XBOX02.axis.com> (raw)
In-Reply-To: <7083c560991d491f0e8b8b70eee611c1187b58d0.camel@linuxfoundation.org>
> -----Original Message-----
> From: openembedded-core-bounces@lists.openembedded.org <openembedded-
> core-bounces@lists.openembedded.org> On Behalf Of Richard Purdie
> Sent: den 25 september 2018 10:13
> To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>; openembedded-
> core@lists.openembedded.org
> Subject: Re: [OE-core] [PATCH 1/3] acl: Make it compatible with
> externalsrc
>
> On Mon, 2018-09-24 at 21:03 +0200, Peter Kjellerstedt wrote:
> > Make the subdir fetch path for configure.ac relative. This avoids the
> > following error after having done `devtool modify acl`:
> >
> > ERROR: acl-2.2.52-r0 do_unpack: Unpack failure for URL:
> > 'file://configure.ac;subdir=.../builds/qemux86-
> > 64/workspace/sources/acl'.
> > subdir argument isn't a subdirectory of unpack root
> > .../builds/qemux86-64/tmp/work/core2-64-poky-linux/acl/2.2.52-r0
> >
> > Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
> > ---
> > meta/recipes-support/attr/acl_2.2.52.bb | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/meta/recipes-support/attr/acl_2.2.52.bb b/meta/recipes-
> > support/attr/acl_2.2.52.bb
> > index 8f3dc45cf7..8b89de9b42 100644
> > --- a/meta/recipes-support/attr/acl_2.2.52.bb
> > +++ b/meta/recipes-support/attr/acl_2.2.52.bb
> > @@ -11,7 +11,7 @@ LIC_FILES_CHKSUM = "file://doc/COPYING;md5=c781d70e
> > d2b4d48995b790403217a249 \
> > DEPENDS = "attr"
> >
> > SRC_URI = "${SAVANNAH_GNU_MIRROR}/acl/${BP}.src.tar.gz \
> > - file://configure.ac;subdir=${S} \
> > + file://configure.ac;subdir=${BP} \
> > file://run-ptest \
> > file://acl-fix-the-order-of-expected-output-of-getfacl.patch \
> > file://test-fix-insufficient-quoting-of.patch \
>
> This isn't making sense to me. Doesn't externalsrc set ${S} to the
> external source location?
Yes, it does, but it does not change ${WORKDIR}. So when it tries
to unpack to the absolute path ${S}, which is outside ${WORKDIR}
when externalsrc is in use, then the above error occurs. Using a
relative path avoids the problem.
> Also, doesn't it remove the do_unpack task?
No, it keeps the task but removes everything except file:// URLs
and URLs with type=kmeta from the SRC_URI. This is also why I had
to check for externalsrc in the do_unpack task of lsof.
> Cheers,
>
> Richard
//Peter
next prev parent reply other threads:[~2018-09-25 9:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-24 19:03 [PATCH 1/3] acl: Make it compatible with externalsrc Peter Kjellerstedt
2018-09-24 19:03 ` [PATCH 2/3] lsof: " Peter Kjellerstedt
2018-09-24 19:03 ` [PATCH 3/3] libxml2: " Peter Kjellerstedt
2018-09-25 8:13 ` [PATCH 1/3] acl: " Richard Purdie
2018-09-25 9:17 ` Peter Kjellerstedt [this message]
2018-10-02 10:25 ` Peter Kjellerstedt
2018-10-10 8:21 ` Peter Kjellerstedt
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=a042a2e4c0464b4d81e4ada72f76fe77@XBOX02.axis.com \
--to=peter.kjellerstedt@axis.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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