From: Joshua Watt <jpewhacker@gmail.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] openssl: Fix documentation DEPENDS
Date: Tue, 27 Aug 2019 11:12:17 -0500 [thread overview]
Message-ID: <9a4134dd-dbf3-929f-379b-4ea8e3e098ee@gmail.com> (raw)
In-Reply-To: <CANNYZj95TRH_+XELYLHGaBrg5gFfgOrpV+pvL5EjfQiXXWavEA@mail.gmail.com>
On 8/27/19 8:25 AM, Alexander Kanavin wrote:
> On Tue, 27 Aug 2019 at 15:08, Joshua Watt <jpewhacker@gmail.com
> <mailto:jpewhacker@gmail.com>> wrote:
>
> RSS doesn't clear out the sysroots if it goes back and executes
> previous
> tasks as part of a rebuild. As such, if perl gets added by a later
> task,
> then bitbake goes back and re-executes the task (I don't remember
> exactly which one... do_configure maybe?), perl may be present
> when it
> wasn't before.
>
>
> I am still not understanding. The sysroot is populated once before
> anything in configure/compile/install/package executes. How would perl
> then magically appear later on in the sysroot?
It's not populated just once. Any task can add things to the RSS as the
build progresses. However, the RSS is only cleaned out at one specific
point early in the build, which I can't recall ATM.
>
> Alex
next prev parent reply other threads:[~2019-08-27 16:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-27 12:46 [PATCH] openssl: Fix documentation DEPENDS Joshua Watt
2019-08-27 12:56 ` Alexander Kanavin
2019-08-27 13:08 ` Joshua Watt
2019-08-27 13:25 ` Alexander Kanavin
2019-08-27 16:12 ` Joshua Watt [this message]
2019-08-27 16:16 ` Alexander Kanavin
2019-08-27 16:41 ` Richard Purdie
-- strict thread matches above, loose matches on Subject: below --
2019-06-27 13:55 Joshua Watt
2019-06-27 16:20 ` Burton, Ross
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=9a4134dd-dbf3-929f-379b-4ea8e3e098ee@gmail.com \
--to=jpewhacker@gmail.com \
--cc=alex.kanavin@gmail.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