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 08:08:47 -0500 [thread overview]
Message-ID: <de80b1e5-dc0e-cabc-409a-0c8c84bc8ef2@gmail.com> (raw)
In-Reply-To: <CANNYZj_zr9+LbbGfhtd46pnUBYgpSW5LL5pE_fuvhxwne6yPrA@mail.gmail.com>
On 8/27/19 7:56 AM, Alexander Kanavin wrote:
> On Tue, 27 Aug 2019 at 14:46, Joshua Watt <jpewhacker@gmail.com
> <mailto:jpewhacker@gmail.com>> wrote:
>
> perl is required to generate the OpenSSL documentation, and therefore
> should be present at do_compile. If not, OpenSSL will skip the
> documentation generation, which isn't reproducible
>
>
> I'm not sure I follow you. If perl is present, documentation is
> generated. If perl is not present, documentation is not generated.
> Where is the non-reproducibility in this?
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.
This is generally true of all RSS dependencies, and until it gets
resolved the best we can say for reproducible builds is that two builds
from stratch without sstate can be binary identical. It will have to be
resolved eventually, but my current plan is to do the reproducible build
test as two clean builds for now so if there is a lot of push back we
can drop it.
>
> Alex
next prev parent reply other threads:[~2019-08-27 13:08 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 [this message]
2019-08-27 13:25 ` Alexander Kanavin
2019-08-27 16:12 ` Joshua Watt
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=de80b1e5-dc0e-cabc-409a-0c8c84bc8ef2@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