Ok thanks. Le ven. 31 mars 2023, 17:55, Alexander Kanavin <alex.kana...@gmail.com> a écrit :
> You need to set up two identical builds in different build directories > and verify that what gets installed and packaged is identical (in this > case it's not). The most common problem is build paths leaking into > the binaries or other installed artifacts, and it can be tricky to > narrow it down to a specific point where it happens in a build. > > The broader rationale for doing this is here > https://reproducible-builds.org/ > > Alex > > On Fri, 31 Mar 2023 at 17:01, Frédéric Martinsons > <frederic.martins...@gmail.com> wrote: > > > > Ok I'll take a look at this next week. But I don't know anything about > reproductability build so if you have any info that can point me to the > right direction, I'll be glad to read it. > > > > Le ven. 31 mars 2023, 15:50, Alexander Kanavin <alex.kana...@gmail.com> > a écrit : > >> > >> On Fri, 31 Mar 2023 at 15:26, Richard Purdie > >> <richard.pur...@linuxfoundation.org> wrote: > >> > > > We do have other reproducibility issues in rust and had to > exclude some > >> > > > packages from the test because of this. We do want to resolve > those > >> > > > issues though. > >> > > > >> > > But aren't recipes in meta-selftest exempted from reproducibility > requirement? > >> > > >> > I suspect we can put an EXCLUDE_FROM_WORLD = "1" in there and then > this > >> > will "go away" but shouldn't our output be reproducible and isn't this > >> > therefore actually a good test? > >> > >> That's true. There's also rust itself which continues to be the only > >> item in core that's in the reproducibility exception list. > >> > >> Alex >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#179452): https://lists.openembedded.org/g/openembedded-core/message/179452 Mute This Topic: https://lists.openembedded.org/mt/97967793/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
