From: "Anton Kachalov" <rnouse@google.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Peter Kjellerstedt <peter.kjellerstedt@axis.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [poky][PATCH] bitbake: remove /usr from pseudo ignore paths
Date: Fri, 15 Jan 2021 20:54:14 +0100 [thread overview]
Message-ID: <CADVsX8_czjA4pVQ=WqG3WzSsNzphXz5bOVnZ5Pa=y2Pk85wYuA@mail.gmail.com> (raw)
In-Reply-To: <dd7b90af3a41bd76856c1610309e7657336db343.camel@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 1362 bytes --]
Perhaps, I'm doing something wrong, but setting this variable in
build/conf/local.conf makes packages fail to build (do_install): only those
which fail with pseudo before (linux-libc-headers and base-files).
On Fri, 15 Jan 2021 at 18:15, Richard Purdie <
richard.purdie@linuxfoundation.org> wrote:
> On Fri, 2021-01-15 at 17:09 +0000, Richard Purdie wrote:
> > On Fri, 2021-01-15 at 18:04 +0100, Anton Kachalov wrote:
> > > nope, setting the entire PSEUDO_IGNORE_PATHS without "/usr" doesn't
> > > work. The do_install task fails with error code 134 without any log
> > > file. Neither temp/run.do_install file exists. The pseudo.log doesn't
> > > have any errors.
> >
> > Right, Peter is correct and _remove is space delimited, the variable is
> > comma delimited. Sorry, I'm getting confused.
> >
> > There is the rather uglier:
> >
> > PSEUDO_IGNORE_PATHS :=
> "${@d.getVar('PSEUDO_IGNORE_PATHS').replace('/usr/,','')}"
> >
> > which should work (I did test this time!).
>
> Thinking more, this is safer:
>
> PSEUDO_IGNORE_PATHS := "${@d.getVar('PSEUDO_IGNORE_PATHS',
> False).replace('/usr/,','')}"
>
> I did test it parses and gave the right value with bitbake -e however I
> not expanding it will be much safer as I suspect the first version
> won't work in recipe context at build time.
>
> Cheers,
>
> Richard
>
>
[-- Attachment #2: Type: text/html, Size: 1859 bytes --]
prev parent reply other threads:[~2021-01-15 19:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210107215121.3901938-1-gmouse@google.com>
[not found] ` <CADVsX8-dMLvuccRjzU73=-reDjEBRq5PZZ+S6ZeugSvTy-iqog@mail.gmail.com>
2021-01-07 21:58 ` [poky][PATCH] bitbake: remove /usr from pseudo ignore paths Anton Kachalov
2021-01-07 22:16 ` [OE-core] " Richard Purdie
2021-01-08 0:56 ` Anton Kachalov
2021-01-08 8:26 ` Richard Purdie
2021-01-11 18:22 ` Peter Kjellerstedt
2021-01-15 17:04 ` Anton Kachalov
2021-01-15 17:09 ` Richard Purdie
2021-01-15 17:15 ` Richard Purdie
2021-01-15 19:54 ` Anton Kachalov [this message]
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='CADVsX8_czjA4pVQ=WqG3WzSsNzphXz5bOVnZ5Pa=y2Pk85wYuA@mail.gmail.com' \
--to=rnouse@google.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter.kjellerstedt@axis.com \
--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 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.