Host tools can influence reproducibility of target items too, so I
would not want to use the same set in both builds. Checking for
reproducibility is simply something that needs a powerful machine.

Alex

On Tue, 23 Jan 2024 at 19:52, Joakim Tjernlund
<joakim.tjernl...@infinera.com> wrote:
>
> On Mon, 2024-01-22 at 21:39 +0100, Alexander Kanavin wrote:
> > On Mon, 22 Jan 2024 at 17:49, Joakim Tjernlund
> > <joakim.tjernl...@infinera.com> wrote:
> > >
> > > On Mon, 2024-01-22 at 17:19 +0100, Alexander Kanavin wrote:
> > > > On Mon, 22 Jan 2024 at 16:59, Joakim Tjernlund
> > > > <joakim.tjernl...@infinera.com> wrote:
> > > > > Maybe but what about the missing reproducibleA/tmp and 
> > > > > reproducibleB/tmp ?
> > > > > Would these be missing if sstate is used for both?
> > > > > In the log there is this:
> > > > >   INFO - Building reproducibleB (sstate NOT allowed)...
> > > >
> > > > It's possible your local/distro config somehow overrides all of the
> > > > test settings, including the separate TMPDIR directories, and simply
> > > > builds things twice in the same directory. The log does seem to
> > > > indicate that:
> > >
> > > That was my though too but I cannot find what is doing that, grepping
> > > has not found TMPDIR changes. Is there something else that might influence
> > > TMPDIR ?
> >
> > You can find out with 'bitbake -e' perhaps.
> >
> > Alex
>
> Finally found it, was:
> -       @echo 'BBPATH = "${BINARY_DIR}"' >> $@
> +       @echo 'BBPATH = "$${TOPDIR}"' >> $@
>
> Now it at least does the right thing: Tanks!
> Off to try optimizing the build somehow, don't want to rebuild all host tools 
> etc.
>
> Seems like I should be able to use OEQA_REPRODUCIBLE_TEST_SSTATE_TARGETS but
> unclear how to populate that list, any pointers?
>
>  Jocke
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#194248): 
https://lists.openembedded.org/g/openembedded-core/message/194248
Mute This Topic: https://lists.openembedded.org/mt/103887646/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to