Reproducible build issues with buildpaths - take 2

Reproducible build issues with buildpaths - take 2

[Richard Purdie]

Hi All,

We've made good progress and I appreciate the help from people. I ran a
fresh build on the autobuilder and I forced it to rerun the QA checks
for all recipes. The tricky bit about warnings is that they don't show
up for objects from sstate and the addition of the buildpaths QA check
doesn't cause the checks to rerun. Due to that a few more previsouly
unseen issues cropped up.

The list of issues now stands are:

qemuppc:
https://autobuilder.yoctoproject.org/typhoon/#/builders/63/builds/5428
WARNING: kernel-devsrc-1.0-r0 do_package_qa: QA Issue: File /lib/modules/5.15.48-yocto-standard/build/include/generated/.vdso32-offsets.h.cmd in package kernel-devsrc contains reference to TMPDIR [buildpaths]

meta-arm:
https://autobuilder.yoctoproject.org/typhoon/#/builders/113/builds/2629
stdio: WARNING: perl-5.36.0-r0 do_package_qa: QA Issue: File /usr/lib/perl/ptest/dist/threads-shared/Makefile.old in package perl-ptest contains reference to TMPDIR

meta-gplv2:
https://autobuilder.yoctoproject.org/typhoon/#/builders/75/builds/5460
WARNING: bash-3.2.57-r0 do_package_qa: QA Issue: File /usr/bin/bashbug in package bash contains reference to TMPDIR [buildpaths]
WARNING: tar-1.17-r3 do_package_qa: QA Issue: File /usr/src/debug/tar/1.17-r3/build/lib/string.h in package tar-src contains reference to TMPDIR
WARNING: diffutils-2.8.1-r7.0 do_package_qa: QA Issue: File /usr/bin/diff.diffutils in package diffutils contains reference to TMPDIR [buildpaths]
WARNING: findutils-4.2.31-r4 do_package_qa: QA Issue: File /usr/bin/updatedb in package findutils contains reference to TMPDIR [buildpaths]
WARNING: mc-4.7.5.2-r3 do_package_qa: QA Issue: File /usr/libexec/mc/extfs.d/iso9660 in package mc-helpers contains reference to TMPDIR [buildpaths]

There is a proposal on the oe-architecture list about simply disabling
this layer going forward. The increased number of issues reinforces my
view on that.

meta-virt:
https://autobuilder.yoctoproject.org/typhoon/#/builders/128/builds/292
WARNING: xen-tools-4.16+stableAUTOINC+f265444922-r0 do_package_qa: QA Issue: File /usr/lib/xen/boot/xen-shim in package xen-tools-shim contains reference to TMPDIR [buildpaths]
WARNING: xen-tools-4.16+stableAUTOINC+f265444922-r0 do_package_qa: QA Issue: File /usr/src/debug/xen-tools/4.16+stableAUTOINC+f265444922-r0/git/tools/libs/light/dsdt_pvh.c in package xen-tools-src contains reference to TMPDIR [buildpaths]
WARNING: xen-tools-4.16+stableAUTOINC+f265444922-r0 do_package_qa: QA Issue: File /usr/lib/libxenlight.so.4.16.0 in package xen-tools-libxenlight contains reference to TMPDIR [buildpaths]
WARNING: xen-tools-4.16+stableAUTOINC+f265444922-r0 do_package_qa: QA Issue: File /usr/lib/libxenlight.a in package xen-tools-staticdev contains reference to TMPDIR [buildpaths]
WARNING: xen-tools-4.16+stableAUTOINC+f265444922-r0 do_package_qa: QA Issue: File /usr/lib/debug/usr/lib/xen/boot/xen-shim-syms in package xen-tools-dbg contains reference to TMPDIR [buildpaths]

There is also still the lttng-modules issue if we enable .debug
checking. I disabled that for these tests to reduce the noise.

Cheers,

Richard

Re: [OE-core] Reproducible build issues with buildpaths - take 2

[Alex Kiernan]

On Fri, Jul 8, 2022 at 12:07 PM Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
>
> Hi All,
>
> We've made good progress and I appreciate the help from people. I ran a
> fresh build on the autobuilder and I forced it to rerun the QA checks
> for all recipes. The tricky bit about warnings is that they don't show
> up for objects from sstate and the addition of the buildpaths QA check
> doesn't cause the checks to rerun. Due to that a few more previsouly
> unseen issues cropped up.
>
> The list of issues now stands are:
>
> qemuppc:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/63/builds/5428
> WARNING: kernel-devsrc-1.0-r0 do_package_qa: QA Issue: File /lib/modules/5.15.48-yocto-standard/build/include/generated/.vdso32-offsets.h.cmd in package kernel-devsrc contains reference to TMPDIR [buildpaths]
>
> meta-arm:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/113/builds/2629
> stdio: WARNING: perl-5.36.0-r0 do_package_qa: QA Issue: File /usr/lib/perl/ptest/dist/threads-shared/Makefile.old in package perl-ptest contains reference to TMPDIR
>
> meta-gplv2:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/75/builds/5460
> WARNING: bash-3.2.57-r0 do_package_qa: QA Issue: File /usr/bin/bashbug in package bash contains reference to TMPDIR [buildpaths]
> WARNING: tar-1.17-r3 do_package_qa: QA Issue: File /usr/src/debug/tar/1.17-r3/build/lib/string.h in package tar-src contains reference to TMPDIR
> WARNING: diffutils-2.8.1-r7.0 do_package_qa: QA Issue: File /usr/bin/diff.diffutils in package diffutils contains reference to TMPDIR [buildpaths]
> WARNING: findutils-4.2.31-r4 do_package_qa: QA Issue: File /usr/bin/updatedb in package findutils contains reference to TMPDIR [buildpaths]
> WARNING: mc-4.7.5.2-r3 do_package_qa: QA Issue: File /usr/libexec/mc/extfs.d/iso9660 in package mc-helpers contains reference to TMPDIR [buildpaths]
>
> There is a proposal on the oe-architecture list about simply disabling
> this layer going forward. The increased number of issues reinforces my
> view on that.
>

I tried explicitly building all the recipes in there, the list is even
longer and there's two which don't build at all (msmtp - can't find
the source, rxvt-unicode - compiler is too new). I agree, think it's
time for it to get retired.

> meta-virt:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/128/builds/292
> WARNING: xen-tools-4.16+stableAUTOINC+f265444922-r0 do_package_qa: QA Issue: File /usr/lib/xen/boot/xen-shim in package xen-tools-shim contains reference to TMPDIR [buildpaths]
> WARNING: xen-tools-4.16+stableAUTOINC+f265444922-r0 do_package_qa: QA Issue: File /usr/src/debug/xen-tools/4.16+stableAUTOINC+f265444922-r0/git/tools/libs/light/dsdt_pvh.c in package xen-tools-src contains reference to TMPDIR [buildpaths]
> WARNING: xen-tools-4.16+stableAUTOINC+f265444922-r0 do_package_qa: QA Issue: File /usr/lib/libxenlight.so.4.16.0 in package xen-tools-libxenlight contains reference to TMPDIR [buildpaths]
> WARNING: xen-tools-4.16+stableAUTOINC+f265444922-r0 do_package_qa: QA Issue: File /usr/lib/libxenlight.a in package xen-tools-staticdev contains reference to TMPDIR [buildpaths]
> WARNING: xen-tools-4.16+stableAUTOINC+f265444922-r0 do_package_qa: QA Issue: File /usr/lib/debug/usr/lib/xen/boot/xen-shim-syms in package xen-tools-dbg contains reference to TMPDIR [buildpaths]
>
> There is also still the lttng-modules issue if we enable .debug
> checking. I disabled that for these tests to reduce the noise.
>
> Cheers,
>
> Richard
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#167819): https://lists.openembedded.org/g/openembedded-core/message/167819
> Mute This Topic: https://lists.openembedded.org/mt/92248896/3618097
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [alex.kiernan@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>


-- 
Alex Kiernan

Re: [OE-core] Reproducible build issues with buildpaths - take 2

[Bruce Ashfield]

On Fri, Jul 8, 2022 at 7:07 AM Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
>
> Hi All,
>
> We've made good progress and I appreciate the help from people. I ran a
> fresh build on the autobuilder and I forced it to rerun the QA checks
> for all recipes. The tricky bit about warnings is that they don't show
> up for objects from sstate and the addition of the buildpaths QA check
> doesn't cause the checks to rerun. Due to that a few more previsouly
> unseen issues cropped up.
>
> The list of issues now stands are:
>
> qemuppc:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/63/builds/5428
> WARNING: kernel-devsrc-1.0-r0 do_package_qa: QA Issue: File /lib/modules/5.15.48-yocto-standard/build/include/generated/.vdso32-offsets.h.cmd in package kernel-devsrc contains reference to TMPDIR [buildpaths]

I'll take this one. My fix was only for arch/arm, but I'll expand it
to cover ppc32.

>
> meta-arm:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/113/builds/2629
> stdio: WARNING: perl-5.36.0-r0 do_package_qa: QA Issue: File /usr/lib/perl/ptest/dist/threads-shared/Makefile.old in package perl-ptest contains reference to TMPDIR
>
> meta-gplv2:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/75/builds/5460
> WARNING: bash-3.2.57-r0 do_package_qa: QA Issue: File /usr/bin/bashbug in package bash contains reference to TMPDIR [buildpaths]
> WARNING: tar-1.17-r3 do_package_qa: QA Issue: File /usr/src/debug/tar/1.17-r3/build/lib/string.h in package tar-src contains reference to TMPDIR
> WARNING: diffutils-2.8.1-r7.0 do_package_qa: QA Issue: File /usr/bin/diff.diffutils in package diffutils contains reference to TMPDIR [buildpaths]
> WARNING: findutils-4.2.31-r4 do_package_qa: QA Issue: File /usr/bin/updatedb in package findutils contains reference to TMPDIR [buildpaths]
> WARNING: mc-4.7.5.2-r3 do_package_qa: QA Issue: File /usr/libexec/mc/extfs.d/iso9660 in package mc-helpers contains reference to TMPDIR [buildpaths]
>
> There is a proposal on the oe-architecture list about simply disabling
> this layer going forward. The increased number of issues reinforces my
> view on that.
>
> meta-virt:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/128/builds/292
> WARNING: xen-tools-4.16+stableAUTOINC+f265444922-r0 do_package_qa: QA Issue: File /usr/lib/xen/boot/xen-shim in package xen-tools-shim contains reference to TMPDIR [buildpaths]
> WARNING: xen-tools-4.16+stableAUTOINC+f265444922-r0 do_package_qa: QA Issue: File /usr/src/debug/xen-tools/4.16+stableAUTOINC+f265444922-r0/git/tools/libs/light/dsdt_pvh.c in package xen-tools-src contains reference to TMPDIR [buildpaths]
> WARNING: xen-tools-4.16+stableAUTOINC+f265444922-r0 do_package_qa: QA Issue: File /usr/lib/libxenlight.so.4.16.0 in package xen-tools-libxenlight contains reference to TMPDIR [buildpaths]
> WARNING: xen-tools-4.16+stableAUTOINC+f265444922-r0 do_package_qa: QA Issue: File /usr/lib/libxenlight.a in package xen-tools-staticdev contains reference to TMPDIR [buildpaths]
> WARNING: xen-tools-4.16+stableAUTOINC+f265444922-r0 do_package_qa: QA Issue: File /usr/lib/debug/usr/lib/xen/boot/xen-shim-syms in package xen-tools-dbg contains reference to TMPDIR [buildpaths]
>

Hopefully Christopher can chime in here. If not, I'll have a look
early next week (or over the weekend).

> There is also still the lttng-modules issue if we enable .debug
> checking. I disabled that for these tests to reduce the noise.

This is one I can pick up as well, if no one else gets there first.

Bruce

>
> Cheers,
>
> Richard
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#167819): https://lists.openembedded.org/g/openembedded-core/message/167819
> Mute This Topic: https://lists.openembedded.org/mt/92248896/1050810
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [bruce.ashfield@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>


-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II

Re: [OE-core] Reproducible build issues with buildpaths - take 2

[Richard Purdie]

On Fri, 2022-07-08 at 09:37 -0400, Bruce Ashfield wrote:
> On Fri, Jul 8, 2022 at 7:07 AM Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > 
> > Hi All,
> > 
> > We've made good progress and I appreciate the help from people. I ran a
> > fresh build on the autobuilder and I forced it to rerun the QA checks
> > for all recipes. The tricky bit about warnings is that they don't show
> > up for objects from sstate and the addition of the buildpaths QA check
> > doesn't cause the checks to rerun. Due to that a few more previsouly
> > unseen issues cropped up.
> > 
> > The list of issues now stands are:
> > 
> > qemuppc:
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/63/builds/5428
> > WARNING: kernel-devsrc-1.0-r0 do_package_qa: QA Issue: File /lib/modules/5.15.48-yocto-standard/build/include/generated/.vdso32-offsets.h.cmd in package kernel-devsrc contains reference to TMPDIR [buildpaths]
> 
> I'll take this one. My fix was only for arch/arm, but I'll expand it
> to cover ppc32.

Thanks.

I built qemuppc locally and got a different failure, I'd really like to
know why I saw that and the autobuilder did not. The failure was:

WARNING: linux-yocto-5.15.48+gitAUTOINC+b35d1d1e83_5aa3abf07b-r0 do_package_qa: QA Issue: File /usr/src/debug/linux-yocto/5.15.48+gitAUTOINC+b35d1d1e83_5aa3abf07b-r0/linux-qemuppc-standard-build/drivers/tty/vt/consolemap_deftbl.c in package linux-yocto-src contains reference to TMPDIR
File /usr/src/debug/linux-yocto/5.15.48+gitAUTOINC+b35d1d1e83_5aa3abf07b-r0/linux-qemuppc-standard-build/lib/oid_registry_data.c in package linux-yocto-src contains reference to TMPDIR [buildpaths]

sure enough, tmp/work/qemuppc-poky-linux/linux-yocto/5.15.48+gitAUTOINC+b35d1d1e83_5aa3abf07b-r0$ head package/usr/src/debug/linux-yocto/5.15.48+gitAUTOINC+b35d1d1e83_5aa3abf07b-r0/linux-qemuppc-standard-build/drivers/tty/vt/consolemap_deftbl.c 
/*
 * Do not edit this file; it was automatically generated by
 *
 * conmakehash /media/build1/poky/build/tmp/work-shared/qemuppc/kernel-source/drivers/tty/vt/cp437.uni > [this file]
 *
 */


I think the warning is saying there is a second issue in linux-qemuppc-
standard-build/lib/oid_registry_data.c too.

Sorry Bruce, not sure why several roads lead to the kernel :/

Cheers,

Richard

Re: [OE-core] Reproducible build issues with buildpaths - take 2

[Christopher Clark]

On Fri, Jul 8, 2022 at 6:37 AM Bruce Ashfield <bruce.ashfield@gmail.com> wrote:
>
> On Fri, Jul 8, 2022 at 7:07 AM Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> >
> > Hi All,
> >
> > We've made good progress and I appreciate the help from people. I ran a
> > fresh build on the autobuilder and I forced it to rerun the QA checks
> > for all recipes. The tricky bit about warnings is that they don't show
> > up for objects from sstate and the addition of the buildpaths QA check
> > doesn't cause the checks to rerun. Due to that a few more previsouly
> > unseen issues cropped up.
> >
> > The list of issues now stands are:
> >
> > qemuppc:
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/63/builds/5428
> > WARNING: kernel-devsrc-1.0-r0 do_package_qa: QA Issue: File /lib/modules/5.15.48-yocto-standard/build/include/generated/.vdso32-offsets.h.cmd in package kernel-devsrc contains reference to TMPDIR [buildpaths]
>
> I'll take this one. My fix was only for arch/arm, but I'll expand it
> to cover ppc32.
>
> >
> > meta-arm:
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/113/builds/2629
> > stdio: WARNING: perl-5.36.0-r0 do_package_qa: QA Issue: File /usr/lib/perl/ptest/dist/threads-shared/Makefile.old in package perl-ptest contains reference to TMPDIR
> >
> > meta-gplv2:
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/75/builds/5460
> > WARNING: bash-3.2.57-r0 do_package_qa: QA Issue: File /usr/bin/bashbug in package bash contains reference to TMPDIR [buildpaths]
> > WARNING: tar-1.17-r3 do_package_qa: QA Issue: File /usr/src/debug/tar/1.17-r3/build/lib/string.h in package tar-src contains reference to TMPDIR
> > WARNING: diffutils-2.8.1-r7.0 do_package_qa: QA Issue: File /usr/bin/diff.diffutils in package diffutils contains reference to TMPDIR [buildpaths]
> > WARNING: findutils-4.2.31-r4 do_package_qa: QA Issue: File /usr/bin/updatedb in package findutils contains reference to TMPDIR [buildpaths]
> > WARNING: mc-4.7.5.2-r3 do_package_qa: QA Issue: File /usr/libexec/mc/extfs.d/iso9660 in package mc-helpers contains reference to TMPDIR [buildpaths]
> >
> > There is a proposal on the oe-architecture list about simply disabling
> > this layer going forward. The increased number of issues reinforces my
> > view on that.
> >
> > meta-virt:
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/128/builds/292
> > WARNING: xen-tools-4.16+stableAUTOINC+f265444922-r0 do_package_qa: QA Issue: File /usr/lib/xen/boot/xen-shim in package xen-tools-shim contains reference to TMPDIR [buildpaths]
> > WARNING: xen-tools-4.16+stableAUTOINC+f265444922-r0 do_package_qa: QA Issue: File /usr/src/debug/xen-tools/4.16+stableAUTOINC+f265444922-r0/git/tools/libs/light/dsdt_pvh.c in package xen-tools-src contains reference to TMPDIR [buildpaths]
> > WARNING: xen-tools-4.16+stableAUTOINC+f265444922-r0 do_package_qa: QA Issue: File /usr/lib/libxenlight.so.4.16.0 in package xen-tools-libxenlight contains reference to TMPDIR [buildpaths]
> > WARNING: xen-tools-4.16+stableAUTOINC+f265444922-r0 do_package_qa: QA Issue: File /usr/lib/libxenlight.a in package xen-tools-staticdev contains reference to TMPDIR [buildpaths]
> > WARNING: xen-tools-4.16+stableAUTOINC+f265444922-r0 do_package_qa: QA Issue: File /usr/lib/debug/usr/lib/xen/boot/xen-shim-syms in package xen-tools-dbg contains reference to TMPDIR [buildpaths]
> >
>
> Hopefully Christopher can chime in here. If not, I'll have a look
> early next week (or over the weekend).

Ack - I will be working on this over this weekend and will let you know.

Christopher

>
> > There is also still the lttng-modules issue if we enable .debug
> > checking. I disabled that for these tests to reduce the noise.
>
> This is one I can pick up as well, if no one else gets there first.
>
> Bruce
>
> >
> > Cheers,
> >
> > Richard
> >
> >
> >
> >
>
>
> --
> - Thou shalt not follow the NULL pointer, for chaos and madness await
> thee at its end
> - "Use the force Harry" - Gandalf, Star Trek II
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#167824): https://lists.openembedded.org/g/openembedded-core/message/167824
> Mute This Topic: https://lists.openembedded.org/mt/92248896/3619037
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [christopher.w.clark@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>

Re: [OE-core] Reproducible build issues with buildpaths - take 2

[Christopher Clark]

On Fri, Jul 8, 2022 at 6:55 PM Christopher Clark via
lists.openembedded.org
<christopher.w.clark=gmail.com@lists.openembedded.org> wrote:
>
> On Fri, Jul 8, 2022 at 6:37 AM Bruce Ashfield <bruce.ashfield@gmail.com> wrote:
> >
> > On Fri, Jul 8, 2022 at 7:07 AM Richard Purdie
> > <richard.purdie@linuxfoundation.org> wrote:
> > >
> > > Hi All,
> > >
> > > We've made good progress and I appreciate the help from people. I ran a
> > > fresh build on the autobuilder and I forced it to rerun the QA checks
> > > for all recipes. The tricky bit about warnings is that they don't show
> > > up for objects from sstate and the addition of the buildpaths QA check
> > > doesn't cause the checks to rerun. Due to that a few more previsouly
> > > unseen issues cropped up.
> > >
> > > The list of issues now stands are:
> > >
> > > qemuppc:
> > > https://autobuilder.yoctoproject.org/typhoon/#/builders/63/builds/5428
> > > WARNING: kernel-devsrc-1.0-r0 do_package_qa: QA Issue: File /lib/modules/5.15.48-yocto-standard/build/include/generated/.vdso32-offsets.h.cmd in package kernel-devsrc contains reference to TMPDIR [buildpaths]
> >
> > I'll take this one. My fix was only for arch/arm, but I'll expand it
> > to cover ppc32.
> >
> > >
> > > meta-arm:
> > > https://autobuilder.yoctoproject.org/typhoon/#/builders/113/builds/2629
> > > stdio: WARNING: perl-5.36.0-r0 do_package_qa: QA Issue: File /usr/lib/perl/ptest/dist/threads-shared/Makefile.old in package perl-ptest contains reference to TMPDIR
> > >
> > > meta-gplv2:
> > > https://autobuilder.yoctoproject.org/typhoon/#/builders/75/builds/5460
> > > WARNING: bash-3.2.57-r0 do_package_qa: QA Issue: File /usr/bin/bashbug in package bash contains reference to TMPDIR [buildpaths]
> > > WARNING: tar-1.17-r3 do_package_qa: QA Issue: File /usr/src/debug/tar/1.17-r3/build/lib/string.h in package tar-src contains reference to TMPDIR
> > > WARNING: diffutils-2.8.1-r7.0 do_package_qa: QA Issue: File /usr/bin/diff.diffutils in package diffutils contains reference to TMPDIR [buildpaths]
> > > WARNING: findutils-4.2.31-r4 do_package_qa: QA Issue: File /usr/bin/updatedb in package findutils contains reference to TMPDIR [buildpaths]
> > > WARNING: mc-4.7.5.2-r3 do_package_qa: QA Issue: File /usr/libexec/mc/extfs.d/iso9660 in package mc-helpers contains reference to TMPDIR [buildpaths]
> > >
> > > There is a proposal on the oe-architecture list about simply disabling
> > > this layer going forward. The increased number of issues reinforces my
> > > view on that.
> > >
> > > meta-virt:
> > > https://autobuilder.yoctoproject.org/typhoon/#/builders/128/builds/292
> > > WARNING: xen-tools-4.16+stableAUTOINC+f265444922-r0 do_package_qa: QA Issue: File /usr/lib/xen/boot/xen-shim in package xen-tools-shim contains reference to TMPDIR [buildpaths]
> > > WARNING: xen-tools-4.16+stableAUTOINC+f265444922-r0 do_package_qa: QA Issue: File /usr/src/debug/xen-tools/4.16+stableAUTOINC+f265444922-r0/git/tools/libs/light/dsdt_pvh.c in package xen-tools-src contains reference to TMPDIR [buildpaths]
> > > WARNING: xen-tools-4.16+stableAUTOINC+f265444922-r0 do_package_qa: QA Issue: File /usr/lib/libxenlight.so.4.16.0 in package xen-tools-libxenlight contains reference to TMPDIR [buildpaths]
> > > WARNING: xen-tools-4.16+stableAUTOINC+f265444922-r0 do_package_qa: QA Issue: File /usr/lib/libxenlight.a in package xen-tools-staticdev contains reference to TMPDIR [buildpaths]
> > > WARNING: xen-tools-4.16+stableAUTOINC+f265444922-r0 do_package_qa: QA Issue: File /usr/lib/debug/usr/lib/xen/boot/xen-shim-syms in package xen-tools-dbg contains reference to TMPDIR [buildpaths]
> > >
> >
> > Hopefully Christopher can chime in here. If not, I'll have a look
> > early next week (or over the weekend).
>
> Ack - I will be working on this over this weekend and will let you know.

ok, I've just posted a patch for this with what I've found so far this
weekend -- it fixes all the warnings that I can see in testing with
both x86 and Arm builds, so hopefully it's OK now.

thanks,

Christopher

>
> >
> > > There is also still the lttng-modules issue if we enable .debug
> > > checking. I disabled that for these tests to reduce the noise.
> >
> > This is one I can pick up as well, if no one else gets there first.
> >
> > Bruce
> >
> > >
> > > Cheers,
> > >
> > > Richard
> > >
> > >
> > >
> > >
> >
> >
> > --
> > - Thou shalt not follow the NULL pointer, for chaos and madness await
> > thee at its end
> > - "Use the force Harry" - Gandalf, Star Trek II
> >
> >
> >
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#167834): https://lists.openembedded.org/g/openembedded-core/message/167834
> Mute This Topic: https://lists.openembedded.org/mt/92248896/3619037
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [christopher.w.clark@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>

Re: [OE-core] Reproducible build issues with buildpaths - take 2

[Bruce Ashfield]

On Fri, Jul 8, 2022 at 10:47 AM Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
>
> On Fri, 2022-07-08 at 09:37 -0400, Bruce Ashfield wrote:
> > On Fri, Jul 8, 2022 at 7:07 AM Richard Purdie
> > <richard.purdie@linuxfoundation.org> wrote:
> > >
> > > Hi All,
> > >
> > > We've made good progress and I appreciate the help from people. I ran a
> > > fresh build on the autobuilder and I forced it to rerun the QA checks
> > > for all recipes. The tricky bit about warnings is that they don't show
> > > up for objects from sstate and the addition of the buildpaths QA check
> > > doesn't cause the checks to rerun. Due to that a few more previsouly
> > > unseen issues cropped up.
> > >
> > > The list of issues now stands are:
> > >
> > > qemuppc:
> > > https://autobuilder.yoctoproject.org/typhoon/#/builders/63/builds/5428
> > > WARNING: kernel-devsrc-1.0-r0 do_package_qa: QA Issue: File /lib/modules/5.15.48-yocto-standard/build/include/generated/.vdso32-offsets.h.cmd in package kernel-devsrc contains reference to TMPDIR [buildpaths]
> >
> > I'll take this one. My fix was only for arch/arm, but I'll expand it
> > to cover ppc32.
>
> Thanks.
>
> I built qemuppc locally and got a different failure, I'd really like to
> know why I saw that and the autobuilder did not. The failure was:
>
> WARNING: linux-yocto-5.15.48+gitAUTOINC+b35d1d1e83_5aa3abf07b-r0 do_package_qa: QA Issue: File /usr/src/debug/linux-yocto/5.15.48+gitAUTOINC+b35d1d1e83_5aa3abf07b-r0/linux-qemuppc-standard-build/drivers/tty/vt/consolemap_deftbl.c in package linux-yocto-src contains reference to TMPDIR
> File /usr/src/debug/linux-yocto/5.15.48+gitAUTOINC+b35d1d1e83_5aa3abf07b-r0/linux-qemuppc-standard-build/lib/oid_registry_data.c in package linux-yocto-src contains reference to TMPDIR [buildpaths]

I have the devsrc fixed for qeumppc32, fix incoming shortly.

But for this one, I don't see it either. What do I need to enable to
get the linux-yocto-src package ? Mine is empty, hence no warning. Is
it one of the archiver modes ?

Bruce

>
> sure enough, tmp/work/qemuppc-poky-linux/linux-yocto/5.15.48+gitAUTOINC+b35d1d1e83_5aa3abf07b-r0$ head package/usr/src/debug/linux-yocto/5.15.48+gitAUTOINC+b35d1d1e83_5aa3abf07b-r0/linux-qemuppc-standard-build/drivers/tty/vt/consolemap_deftbl.c
> /*
>  * Do not edit this file; it was automatically generated by
>  *
>  * conmakehash /media/build1/poky/build/tmp/work-shared/qemuppc/kernel-source/drivers/tty/vt/cp437.uni > [this file]
>  *
>  */
>
>
> I think the warning is saying there is a second issue in linux-qemuppc-
> standard-build/lib/oid_registry_data.c too.
>
> Sorry Bruce, not sure why several roads lead to the kernel :/
>
> Cheers,
>
> Richard
>


-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II

Re: [OE-core] Reproducible build issues with buildpaths - take 2

[Bruce Ashfield]

On Sun, Jul 10, 2022 at 9:29 PM Bruce Ashfield via
lists.openembedded.org
<bruce.ashfield=gmail.com@lists.openembedded.org> wrote:
>
> On Fri, Jul 8, 2022 at 10:47 AM Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> >
> > On Fri, 2022-07-08 at 09:37 -0400, Bruce Ashfield wrote:
> > > On Fri, Jul 8, 2022 at 7:07 AM Richard Purdie
> > > <richard.purdie@linuxfoundation.org> wrote:
> > > >
> > > > Hi All,
> > > >
> > > > We've made good progress and I appreciate the help from people. I ran a
> > > > fresh build on the autobuilder and I forced it to rerun the QA checks
> > > > for all recipes. The tricky bit about warnings is that they don't show
> > > > up for objects from sstate and the addition of the buildpaths QA check
> > > > doesn't cause the checks to rerun. Due to that a few more previsouly
> > > > unseen issues cropped up.
> > > >
> > > > The list of issues now stands are:
> > > >
> > > > qemuppc:
> > > > https://autobuilder.yoctoproject.org/typhoon/#/builders/63/builds/5428
> > > > WARNING: kernel-devsrc-1.0-r0 do_package_qa: QA Issue: File /lib/modules/5.15.48-yocto-standard/build/include/generated/.vdso32-offsets.h.cmd in package kernel-devsrc contains reference to TMPDIR [buildpaths]
> > >
> > > I'll take this one. My fix was only for arch/arm, but I'll expand it
> > > to cover ppc32.
> >
> > Thanks.
> >
> > I built qemuppc locally and got a different failure, I'd really like to
> > know why I saw that and the autobuilder did not. The failure was:
> >
> > WARNING: linux-yocto-5.15.48+gitAUTOINC+b35d1d1e83_5aa3abf07b-r0 do_package_qa: QA Issue: File /usr/src/debug/linux-yocto/5.15.48+gitAUTOINC+b35d1d1e83_5aa3abf07b-r0/linux-qemuppc-standard-build/drivers/tty/vt/consolemap_deftbl.c in package linux-yocto-src contains reference to TMPDIR
> > File /usr/src/debug/linux-yocto/5.15.48+gitAUTOINC+b35d1d1e83_5aa3abf07b-r0/linux-qemuppc-standard-build/lib/oid_registry_data.c in package linux-yocto-src contains reference to TMPDIR [buildpaths]
>
> I have the devsrc fixed for qeumppc32, fix incoming shortly.
>
> But for this one, I don't see it either. What do I need to enable to
> get the linux-yocto-src package ? Mine is empty, hence no warning. Is
> it one of the archiver modes ?

I sent a series with a fix for qemuppc32 kernel-devsrc and a WIP fix
for the conmakehash issue, I'll have a look at oid_registry next.

Bruce

>
> Bruce
>
> >
> > sure enough, tmp/work/qemuppc-poky-linux/linux-yocto/5.15.48+gitAUTOINC+b35d1d1e83_5aa3abf07b-r0$ head package/usr/src/debug/linux-yocto/5.15.48+gitAUTOINC+b35d1d1e83_5aa3abf07b-r0/linux-qemuppc-standard-build/drivers/tty/vt/consolemap_deftbl.c
> > /*
> >  * Do not edit this file; it was automatically generated by
> >  *
> >  * conmakehash /media/build1/poky/build/tmp/work-shared/qemuppc/kernel-source/drivers/tty/vt/cp437.uni > [this file]
> >  *
> >  */
> >
> >
> > I think the warning is saying there is a second issue in linux-qemuppc-
> > standard-build/lib/oid_registry_data.c too.
> >
> > Sorry Bruce, not sure why several roads lead to the kernel :/
> >
> > Cheers,
> >
> > Richard
> >
>
>
> --
> - Thou shalt not follow the NULL pointer, for chaos and madness await
> thee at its end
> - "Use the force Harry" - Gandalf, Star Trek II
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#167851): https://lists.openembedded.org/g/openembedded-core/message/167851
> Mute This Topic: https://lists.openembedded.org/mt/92248896/1050810
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [bruce.ashfield@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>


-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II

Re: [OE-core] Reproducible build issues with buildpaths - take 2

[Bruce Ashfield]

On Sun, Jul 10, 2022 at 11:27 PM Bruce Ashfield via
lists.openembedded.org
<bruce.ashfield=gmail.com@lists.openembedded.org> wrote:
>
> On Sun, Jul 10, 2022 at 9:29 PM Bruce Ashfield via
> lists.openembedded.org
> <bruce.ashfield=gmail.com@lists.openembedded.org> wrote:
> >
> > On Fri, Jul 8, 2022 at 10:47 AM Richard Purdie
> > <richard.purdie@linuxfoundation.org> wrote:
> > >
> > > On Fri, 2022-07-08 at 09:37 -0400, Bruce Ashfield wrote:
> > > > On Fri, Jul 8, 2022 at 7:07 AM Richard Purdie
> > > > <richard.purdie@linuxfoundation.org> wrote:
> > > > >
> > > > > Hi All,
> > > > >
> > > > > We've made good progress and I appreciate the help from people. I ran a
> > > > > fresh build on the autobuilder and I forced it to rerun the QA checks
> > > > > for all recipes. The tricky bit about warnings is that they don't show
> > > > > up for objects from sstate and the addition of the buildpaths QA check
> > > > > doesn't cause the checks to rerun. Due to that a few more previsouly
> > > > > unseen issues cropped up.
> > > > >
> > > > > The list of issues now stands are:
> > > > >
> > > > > qemuppc:
> > > > > https://autobuilder.yoctoproject.org/typhoon/#/builders/63/builds/5428
> > > > > WARNING: kernel-devsrc-1.0-r0 do_package_qa: QA Issue: File /lib/modules/5.15.48-yocto-standard/build/include/generated/.vdso32-offsets.h.cmd in package kernel-devsrc contains reference to TMPDIR [buildpaths]
> > > >
> > > > I'll take this one. My fix was only for arch/arm, but I'll expand it
> > > > to cover ppc32.
> > >
> > > Thanks.
> > >
> > > I built qemuppc locally and got a different failure, I'd really like to
> > > know why I saw that and the autobuilder did not. The failure was:
> > >
> > > WARNING: linux-yocto-5.15.48+gitAUTOINC+b35d1d1e83_5aa3abf07b-r0 do_package_qa: QA Issue: File /usr/src/debug/linux-yocto/5.15.48+gitAUTOINC+b35d1d1e83_5aa3abf07b-r0/linux-qemuppc-standard-build/drivers/tty/vt/consolemap_deftbl.c in package linux-yocto-src contains reference to TMPDIR
> > > File /usr/src/debug/linux-yocto/5.15.48+gitAUTOINC+b35d1d1e83_5aa3abf07b-r0/linux-qemuppc-standard-build/lib/oid_registry_data.c in package linux-yocto-src contains reference to TMPDIR [buildpaths]
> >
> > I have the devsrc fixed for qeumppc32, fix incoming shortly.
> >
> > But for this one, I don't see it either. What do I need to enable to
> > get the linux-yocto-src package ? Mine is empty, hence no warning. Is
> > it one of the archiver modes ?
>
> I sent a series with a fix for qemuppc32 kernel-devsrc and a WIP fix
> for the conmakehash issue, I'll have a look at oid_registry next.


oid_registry is a perl script .. also capturing the full path of the
executable. I did a similar fix for linux-yocto 5.15 and used
'basename' versus the whole path.

If these hold up, we can expand the versions that get the fix.

Bruce

>
> Bruce
>
> >
> > Bruce
> >
> > >
> > > sure enough, tmp/work/qemuppc-poky-linux/linux-yocto/5.15.48+gitAUTOINC+b35d1d1e83_5aa3abf07b-r0$ head package/usr/src/debug/linux-yocto/5.15.48+gitAUTOINC+b35d1d1e83_5aa3abf07b-r0/linux-qemuppc-standard-build/drivers/tty/vt/consolemap_deftbl.c
> > > /*
> > >  * Do not edit this file; it was automatically generated by
> > >  *
> > >  * conmakehash /media/build1/poky/build/tmp/work-shared/qemuppc/kernel-source/drivers/tty/vt/cp437.uni > [this file]
> > >  *
> > >  */
> > >
> > >
> > > I think the warning is saying there is a second issue in linux-qemuppc-
> > > standard-build/lib/oid_registry_data.c too.
> > >
> > > Sorry Bruce, not sure why several roads lead to the kernel :/
> > >
> > > Cheers,
> > >
> > > Richard
> > >
> >
> >
> > --
> > - Thou shalt not follow the NULL pointer, for chaos and madness await
> > thee at its end
> > - "Use the force Harry" - Gandalf, Star Trek II
> >
> >
> >
>
>
> --
> - Thou shalt not follow the NULL pointer, for chaos and madness await
> thee at its end
> - "Use the force Harry" - Gandalf, Star Trek II
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#167856): https://lists.openembedded.org/g/openembedded-core/message/167856
> Mute This Topic: https://lists.openembedded.org/mt/92248896/1050810
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [bruce.ashfield@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>


-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II

Re: [OE-core] Reproducible build issues with buildpaths - take 2

[Richard Purdie]

On Mon, 2022-07-11 at 00:06 -0300, Bruce Ashfield wrote:
> On Sun, Jul 10, 2022 at 11:27 PM Bruce Ashfield via
> lists.openembedded.org
> <bruce.ashfield=gmail.com@lists.openembedded.org> wrote:
> > 
> > On Sun, Jul 10, 2022 at 9:29 PM Bruce Ashfield via
> > lists.openembedded.org
> > <bruce.ashfield=gmail.com@lists.openembedded.org> wrote:
> > > 
> > > On Fri, Jul 8, 2022 at 10:47 AM Richard Purdie
> > > <richard.purdie@linuxfoundation.org> wrote:
> > > > 
> > > > On Fri, 2022-07-08 at 09:37 -0400, Bruce Ashfield wrote:
> > > > > On Fri, Jul 8, 2022 at 7:07 AM Richard Purdie
> > > > > <richard.purdie@linuxfoundation.org> wrote:
> > > > > > 
> > > > > > Hi All,
> > > > > > 
> > > > > > We've made good progress and I appreciate the help from people. I ran a
> > > > > > fresh build on the autobuilder and I forced it to rerun the QA checks
> > > > > > for all recipes. The tricky bit about warnings is that they don't show
> > > > > > up for objects from sstate and the addition of the buildpaths QA check
> > > > > > doesn't cause the checks to rerun. Due to that a few more previsouly
> > > > > > unseen issues cropped up.
> > > > > > 
> > > > > > The list of issues now stands are:
> > > > > > 
> > > > > > qemuppc:
> > > > > > https://autobuilder.yoctoproject.org/typhoon/#/builders/63/builds/5428
> > > > > > WARNING: kernel-devsrc-1.0-r0 do_package_qa: QA Issue: File /lib/modules/5.15.48-yocto-standard/build/include/generated/.vdso32-offsets.h.cmd in package kernel-devsrc contains reference to TMPDIR [buildpaths]
> > > > > 
> > > > > I'll take this one. My fix was only for arch/arm, but I'll expand it
> > > > > to cover ppc32.
> > > > 
> > > > Thanks.
> > > > 
> > > > I built qemuppc locally and got a different failure, I'd really like to
> > > > know why I saw that and the autobuilder did not. The failure was:
> > > > 
> > > > WARNING: linux-yocto-5.15.48+gitAUTOINC+b35d1d1e83_5aa3abf07b-r0 do_package_qa: QA Issue: File /usr/src/debug/linux-yocto/5.15.48+gitAUTOINC+b35d1d1e83_5aa3abf07b-r0/linux-qemuppc-standard-build/drivers/tty/vt/consolemap_deftbl.c in package linux-yocto-src contains reference to TMPDIR
> > > > File /usr/src/debug/linux-yocto/5.15.48+gitAUTOINC+b35d1d1e83_5aa3abf07b-r0/linux-qemuppc-standard-build/lib/oid_registry_data.c in package linux-yocto-src contains reference to TMPDIR [buildpaths]
> > > 
> > > I have the devsrc fixed for qeumppc32, fix incoming shortly.
> > > 
> > > But for this one, I don't see it either. What do I need to enable to
> > > get the linux-yocto-src package ? Mine is empty, hence no warning. Is
> > > it one of the archiver modes ?
> > 
> > I sent a series with a fix for qemuppc32 kernel-devsrc and a WIP fix
> > for the conmakehash issue, I'll have a look at oid_registry next.
> 
> 
> oid_registry is a perl script .. also capturing the full path of the
> executable. I did a similar fix for linux-yocto 5.15 and used
> 'basename' versus the whole path.
> 
> If these hold up, we can expand the versions that get the fix.

Thanks. I spent a bit of time working out why I was seeing things the
autobuilder wasn't. It turns out:

https://git.yoctoproject.org/poky/commit/?id=c725bdb29b2669e53ea0f9d30f9683f094c9b326

broke kernel source handling (and hence SPDX license handling for the
kernel too). I was using an older build where that wasn't present,
hence I saw more kernel errors.

With your fixes and the above reverted, I ran another build overnight
and in that we saw:

beaglebone:
WARNING: linux-yocto-5.15.36+gitAUTOINC+f122fe59e7_4c875cf137-r0 do_package_qa: QA Issue: File /usr/src/debug/linux-yocto/5.15.36+gitAUTOINC+f122fe59e7_4c875cf137-r0/linux-beaglebone_yocto-standard-build/lib/oid_registry_data.c in package linux-yocto-src contains reference to TMPDIR

beaglebone-alt:
stdio: WARNING: linux-yocto-5.10.113+gitAUTOINC+5b3dacac6f_8038166b72-r0 do_package_qa: QA Issue: File /usr/src/debug/linux-yocto/5.10.113+gitAUTOINC+5b3dacac6f_8038166b72-r0/linux-beaglebone_yocto-standard-build/drivers/tty/vt/consolemap_deftbl.c in package linux-yocto-src contains reference to TMPDIR

edgerouter:
stdio: WARNING: linux-yocto-5.15.36+gitAUTOINC+f122fe59e7_b978686694-r0 do_package_qa: QA Issue: File /usr/src/debug/linux-yocto/5.15.36+gitAUTOINC+f122fe59e7_b978686694-r0/linux-edgerouter-standard-build/lib/oid_registry_data.c in package linux-yocto-src contains reference to TMPDIR

edgerouter-alt:
stdio: WARNING: linux-yocto-5.10.113+gitAUTOINC+5b3dacac6f_43577894d2-r0 do_package_qa: QA Issue: File /usr/src/debug/linux-yocto/5.10.113+gitAUTOINC+5b3dacac6f_43577894d2-r0/linux-edgerouter-standard-build/lib/oid_registry_data.c in package linux-yocto-src contains reference to TMPDIR

meta-intel:
tdio: WARNING: linux-intel-5.15.43+gitAUTOINC+ea948a0983_1ec5959a8f-r0 do_package_qa: QA Issue: File /usr/src/debug/linux-intel/5.15.43+gitAUTOINC+ea948a0983_1ec5959a8f-r0/linux-corei7-64-intel-common-standard-build/drivers/tty/vt/consolemap_deftbl.c in package linux-intel-src contains reference to TMPDIR

qemumips-alt:
tdio: WARNING: linux-yocto-5.10.128+gitAUTOINC+5b3dacac6f_cdec08a505-r0 do_package_qa: QA Issue: File /usr/src/debug/linux-yocto/5.10.128+gitAUTOINC+5b3dacac6f_cdec08a505-r0/linux-qemumips-standard-build/drivers/tty/vt/consolemap_deftbl.c in package linux-yocto-src contains reference to TMPDIR

qemuppc-alt:
stdio: WARNING: linux-yocto-5.10.128+gitAUTOINC+5b3dacac6f_c0821a7ab5-r0 do_package_qa: QA Issue: File /usr/src/debug/linux-yocto/5.10.128+gitAUTOINC+5b3dacac6f_c0821a7ab5-r0/linux-qemuppc-standard-build/drivers/tty/vt/consolemap_deftbl.c in package linux-yocto-src contains reference to TMPDIR

so thankfully that looks like the two errors we know about spread over
different kernel versions. I think a version bump for yocto-bsp would
fix some of them and backports to 5.10 some of the others?

I'm sharing the full info in case you spot any patterns I don't! :)

In summary, we're down to these and the lttng-modules issue which
appears when we start checking .debug files in buildpaths (patch added
and reverted in master-next currently).

Cheers,

Richard

Re: [OE-core] Reproducible build issues with buildpaths - take 2

[Bruce Ashfield]

On Tue, Jul 12, 2022 at 6:44 AM Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
>
> On Mon, 2022-07-11 at 00:06 -0300, Bruce Ashfield wrote:
> > On Sun, Jul 10, 2022 at 11:27 PM Bruce Ashfield via
> > lists.openembedded.org
> > <bruce.ashfield=gmail.com@lists.openembedded.org> wrote:
> > >
> > > On Sun, Jul 10, 2022 at 9:29 PM Bruce Ashfield via
> > > lists.openembedded.org
> > > <bruce.ashfield=gmail.com@lists.openembedded.org> wrote:
> > > >
> > > > On Fri, Jul 8, 2022 at 10:47 AM Richard Purdie
> > > > <richard.purdie@linuxfoundation.org> wrote:
> > > > >
> > > > > On Fri, 2022-07-08 at 09:37 -0400, Bruce Ashfield wrote:
> > > > > > On Fri, Jul 8, 2022 at 7:07 AM Richard Purdie
> > > > > > <richard.purdie@linuxfoundation.org> wrote:
> > > > > > >
> > > > > > > Hi All,
> > > > > > >
> > > > > > > We've made good progress and I appreciate the help from people. I ran a
> > > > > > > fresh build on the autobuilder and I forced it to rerun the QA checks
> > > > > > > for all recipes. The tricky bit about warnings is that they don't show
> > > > > > > up for objects from sstate and the addition of the buildpaths QA check
> > > > > > > doesn't cause the checks to rerun. Due to that a few more previsouly
> > > > > > > unseen issues cropped up.
> > > > > > >
> > > > > > > The list of issues now stands are:
> > > > > > >
> > > > > > > qemuppc:
> > > > > > > https://autobuilder.yoctoproject.org/typhoon/#/builders/63/builds/5428
> > > > > > > WARNING: kernel-devsrc-1.0-r0 do_package_qa: QA Issue: File /lib/modules/5.15.48-yocto-standard/build/include/generated/.vdso32-offsets.h.cmd in package kernel-devsrc contains reference to TMPDIR [buildpaths]
> > > > > >
> > > > > > I'll take this one. My fix was only for arch/arm, but I'll expand it
> > > > > > to cover ppc32.
> > > > >
> > > > > Thanks.
> > > > >
> > > > > I built qemuppc locally and got a different failure, I'd really like to
> > > > > know why I saw that and the autobuilder did not. The failure was:
> > > > >
> > > > > WARNING: linux-yocto-5.15.48+gitAUTOINC+b35d1d1e83_5aa3abf07b-r0 do_package_qa: QA Issue: File /usr/src/debug/linux-yocto/5.15.48+gitAUTOINC+b35d1d1e83_5aa3abf07b-r0/linux-qemuppc-standard-build/drivers/tty/vt/consolemap_deftbl.c in package linux-yocto-src contains reference to TMPDIR
> > > > > File /usr/src/debug/linux-yocto/5.15.48+gitAUTOINC+b35d1d1e83_5aa3abf07b-r0/linux-qemuppc-standard-build/lib/oid_registry_data.c in package linux-yocto-src contains reference to TMPDIR [buildpaths]
> > > >
> > > > I have the devsrc fixed for qeumppc32, fix incoming shortly.
> > > >
> > > > But for this one, I don't see it either. What do I need to enable to
> > > > get the linux-yocto-src package ? Mine is empty, hence no warning. Is
> > > > it one of the archiver modes ?
> > >
> > > I sent a series with a fix for qemuppc32 kernel-devsrc and a WIP fix
> > > for the conmakehash issue, I'll have a look at oid_registry next.
> >
> >
> > oid_registry is a perl script .. also capturing the full path of the
> > executable. I did a similar fix for linux-yocto 5.15 and used
> > 'basename' versus the whole path.
> >
> > If these hold up, we can expand the versions that get the fix.
>
> Thanks. I spent a bit of time working out why I was seeing things the
> autobuilder wasn't. It turns out:
>
> https://git.yoctoproject.org/poky/commit/?id=c725bdb29b2669e53ea0f9d30f9683f094c9b326
>
> broke kernel source handling (and hence SPDX license handling for the
> kernel too). I was using an older build where that wasn't present,
> hence I saw more kernel errors.
>
> With your fixes and the above reverted, I ran another build overnight
> and in that we saw:
>
> beaglebone:
> WARNING: linux-yocto-5.15.36+gitAUTOINC+f122fe59e7_4c875cf137-r0 do_package_qa: QA Issue: File /usr/src/debug/linux-yocto/5.15.36+gitAUTOINC+f122fe59e7_4c875cf137-r0/linux-beaglebone_yocto-standard-build/lib/oid_registry_data.c in package linux-yocto-src contains reference to TMPDIR
>
> beaglebone-alt:
> stdio: WARNING: linux-yocto-5.10.113+gitAUTOINC+5b3dacac6f_8038166b72-r0 do_package_qa: QA Issue: File /usr/src/debug/linux-yocto/5.10.113+gitAUTOINC+5b3dacac6f_8038166b72-r0/linux-beaglebone_yocto-standard-build/drivers/tty/vt/consolemap_deftbl.c in package linux-yocto-src contains reference to TMPDIR
>
> edgerouter:
> stdio: WARNING: linux-yocto-5.15.36+gitAUTOINC+f122fe59e7_b978686694-r0 do_package_qa: QA Issue: File /usr/src/debug/linux-yocto/5.15.36+gitAUTOINC+f122fe59e7_b978686694-r0/linux-edgerouter-standard-build/lib/oid_registry_data.c in package linux-yocto-src contains reference to TMPDIR
>
> edgerouter-alt:
> stdio: WARNING: linux-yocto-5.10.113+gitAUTOINC+5b3dacac6f_43577894d2-r0 do_package_qa: QA Issue: File /usr/src/debug/linux-yocto/5.10.113+gitAUTOINC+5b3dacac6f_43577894d2-r0/linux-edgerouter-standard-build/lib/oid_registry_data.c in package linux-yocto-src contains reference to TMPDIR
>
> meta-intel:
> tdio: WARNING: linux-intel-5.15.43+gitAUTOINC+ea948a0983_1ec5959a8f-r0 do_package_qa: QA Issue: File /usr/src/debug/linux-intel/5.15.43+gitAUTOINC+ea948a0983_1ec5959a8f-r0/linux-corei7-64-intel-common-standard-build/drivers/tty/vt/consolemap_deftbl.c in package linux-intel-src contains reference to TMPDIR
>
> qemumips-alt:
> tdio: WARNING: linux-yocto-5.10.128+gitAUTOINC+5b3dacac6f_cdec08a505-r0 do_package_qa: QA Issue: File /usr/src/debug/linux-yocto/5.10.128+gitAUTOINC+5b3dacac6f_cdec08a505-r0/linux-qemumips-standard-build/drivers/tty/vt/consolemap_deftbl.c in package linux-yocto-src contains reference to TMPDIR
>
> qemuppc-alt:
> stdio: WARNING: linux-yocto-5.10.128+gitAUTOINC+5b3dacac6f_c0821a7ab5-r0 do_package_qa: QA Issue: File /usr/src/debug/linux-yocto/5.10.128+gitAUTOINC+5b3dacac6f_c0821a7ab5-r0/linux-qemuppc-standard-build/drivers/tty/vt/consolemap_deftbl.c in package linux-yocto-src contains reference to TMPDIR
>
> so thankfully that looks like the two errors we know about spread over
> different kernel versions. I think a version bump for yocto-bsp would
> fix some of them and backports to 5.10 some of the others?

Yup, my fixes should hold for those as well.

I'll send bumps to 5.10 and the BSPs this morning.

Bruce

>
> I'm sharing the full info in case you spot any patterns I don't! :)
>
> In summary, we're down to these and the lttng-modules issue which
> appears when we start checking .debug files in buildpaths (patch added
> and reverted in master-next currently).
>
> Cheers,
>
> Richard
>
>


-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II

Re: [OE-core] Reproducible build issues with buildpaths - take 2

[Alejandro Enedino Hernandez Samaniego]

[-- Attachment #1: Type: text/plain, Size: 6988 bytes --]


On 7/12/22 06:31, Bruce Ashfield wrote:
> On Tue, Jul 12, 2022 at 6:44 AM Richard Purdie
> <richard.purdie@linuxfoundation.org>  wrote:
>> On Mon, 2022-07-11 at 00:06 -0300, Bruce Ashfield wrote:
>>> On Sun, Jul 10, 2022 at 11:27 PM Bruce Ashfield via
>>> lists.openembedded.org
>>> <bruce.ashfield=gmail.com@lists.openembedded.org>  wrote:
>>>> On Sun, Jul 10, 2022 at 9:29 PM Bruce Ashfield via
>>>> lists.openembedded.org
>>>> <bruce.ashfield=gmail.com@lists.openembedded.org>  wrote:
>>>>> On Fri, Jul 8, 2022 at 10:47 AM Richard Purdie
>>>>> <richard.purdie@linuxfoundation.org>  wrote:
>>>>>> On Fri, 2022-07-08 at 09:37 -0400, Bruce Ashfield wrote:
>>>>>>> On Fri, Jul 8, 2022 at 7:07 AM Richard Purdie
>>>>>>> <richard.purdie@linuxfoundation.org>  wrote:
>>>>>>>> Hi All,
>>>>>>>>
>>>>>>>> We've made good progress and I appreciate the help from people. I ran a
>>>>>>>> fresh build on the autobuilder and I forced it to rerun the QA checks
>>>>>>>> for all recipes. The tricky bit about warnings is that they don't show
>>>>>>>> up for objects from sstate and the addition of the buildpaths QA check
>>>>>>>> doesn't cause the checks to rerun. Due to that a few more previsouly
>>>>>>>> unseen issues cropped up.
>>>>>>>>
>>>>>>>> The list of issues now stands are:
>>>>>>>>
>>>>>>>> qemuppc:
>>>>>>>> https://autobuilder.yoctoproject.org/typhoon/#/builders/63/builds/5428
>>>>>>>> WARNING: kernel-devsrc-1.0-r0 do_package_qa: QA Issue: File /lib/modules/5.15.48-yocto-standard/build/include/generated/.vdso32-offsets.h.cmd in package kernel-devsrc contains reference to TMPDIR [buildpaths]
>>>>>>> I'll take this one. My fix was only for arch/arm, but I'll expand it
>>>>>>> to cover ppc32.
>>>>>> Thanks.
>>>>>>
>>>>>> I built qemuppc locally and got a different failure, I'd really like to
>>>>>> know why I saw that and the autobuilder did not. The failure was:
>>>>>>
>>>>>> WARNING: linux-yocto-5.15.48+gitAUTOINC+b35d1d1e83_5aa3abf07b-r0 do_package_qa: QA Issue: File /usr/src/debug/linux-yocto/5.15.48+gitAUTOINC+b35d1d1e83_5aa3abf07b-r0/linux-qemuppc-standard-build/drivers/tty/vt/consolemap_deftbl.c in package linux-yocto-src contains reference to TMPDIR
>>>>>> File /usr/src/debug/linux-yocto/5.15.48+gitAUTOINC+b35d1d1e83_5aa3abf07b-r0/linux-qemuppc-standard-build/lib/oid_registry_data.c in package linux-yocto-src contains reference to TMPDIR [buildpaths]
>>>>> I have the devsrc fixed for qeumppc32, fix incoming shortly.
>>>>>
>>>>> But for this one, I don't see it either. What do I need to enable to
>>>>> get the linux-yocto-src package ? Mine is empty, hence no warning. Is
>>>>> it one of the archiver modes ?
>>>> I sent a series with a fix for qemuppc32 kernel-devsrc and a WIP fix
>>>> for the conmakehash issue, I'll have a look at oid_registry next.
>>>
>>> oid_registry is a perl script .. also capturing the full path of the
>>> executable. I did a similar fix for linux-yocto 5.15 and used
>>> 'basename' versus the whole path.
>>>
>>> If these hold up, we can expand the versions that get the fix.
>> Thanks. I spent a bit of time working out why I was seeing things the
>> autobuilder wasn't. It turns out:
>>
>> https://git.yoctoproject.org/poky/commit/?id=c725bdb29b2669e53ea0f9d30f9683f094c9b326
>>
>> broke kernel source handling (and hence SPDX license handling for the
>> kernel too). I was using an older build where that wasn't present,
>> hence I saw more kernel errors.

Sorry about this, I will take a closer look on how we can fix the src paths with externalsrc without these breakages,
but reverting is probably the right path to take at the moment.

Alejandro


>>
>> With your fixes and the above reverted, I ran another build overnight
>> and in that we saw:
>>
>> beaglebone:
>> WARNING: linux-yocto-5.15.36+gitAUTOINC+f122fe59e7_4c875cf137-r0 do_package_qa: QA Issue: File /usr/src/debug/linux-yocto/5.15.36+gitAUTOINC+f122fe59e7_4c875cf137-r0/linux-beaglebone_yocto-standard-build/lib/oid_registry_data.c in package linux-yocto-src contains reference to TMPDIR
>>
>> beaglebone-alt:
>> stdio: WARNING: linux-yocto-5.10.113+gitAUTOINC+5b3dacac6f_8038166b72-r0 do_package_qa: QA Issue: File /usr/src/debug/linux-yocto/5.10.113+gitAUTOINC+5b3dacac6f_8038166b72-r0/linux-beaglebone_yocto-standard-build/drivers/tty/vt/consolemap_deftbl.c in package linux-yocto-src contains reference to TMPDIR
>>
>> edgerouter:
>> stdio: WARNING: linux-yocto-5.15.36+gitAUTOINC+f122fe59e7_b978686694-r0 do_package_qa: QA Issue: File /usr/src/debug/linux-yocto/5.15.36+gitAUTOINC+f122fe59e7_b978686694-r0/linux-edgerouter-standard-build/lib/oid_registry_data.c in package linux-yocto-src contains reference to TMPDIR
>>
>> edgerouter-alt:
>> stdio: WARNING: linux-yocto-5.10.113+gitAUTOINC+5b3dacac6f_43577894d2-r0 do_package_qa: QA Issue: File /usr/src/debug/linux-yocto/5.10.113+gitAUTOINC+5b3dacac6f_43577894d2-r0/linux-edgerouter-standard-build/lib/oid_registry_data.c in package linux-yocto-src contains reference to TMPDIR
>>
>> meta-intel:
>> tdio: WARNING: linux-intel-5.15.43+gitAUTOINC+ea948a0983_1ec5959a8f-r0 do_package_qa: QA Issue: File /usr/src/debug/linux-intel/5.15.43+gitAUTOINC+ea948a0983_1ec5959a8f-r0/linux-corei7-64-intel-common-standard-build/drivers/tty/vt/consolemap_deftbl.c in package linux-intel-src contains reference to TMPDIR
>>
>> qemumips-alt:
>> tdio: WARNING: linux-yocto-5.10.128+gitAUTOINC+5b3dacac6f_cdec08a505-r0 do_package_qa: QA Issue: File /usr/src/debug/linux-yocto/5.10.128+gitAUTOINC+5b3dacac6f_cdec08a505-r0/linux-qemumips-standard-build/drivers/tty/vt/consolemap_deftbl.c in package linux-yocto-src contains reference to TMPDIR
>>
>> qemuppc-alt:
>> stdio: WARNING: linux-yocto-5.10.128+gitAUTOINC+5b3dacac6f_c0821a7ab5-r0 do_package_qa: QA Issue: File /usr/src/debug/linux-yocto/5.10.128+gitAUTOINC+5b3dacac6f_c0821a7ab5-r0/linux-qemuppc-standard-build/drivers/tty/vt/consolemap_deftbl.c in package linux-yocto-src contains reference to TMPDIR
>>
>> so thankfully that looks like the two errors we know about spread over
>> different kernel versions. I think a version bump for yocto-bsp would
>> fix some of them and backports to 5.10 some of the others?
> Yup, my fixes should hold for those as well.
>
> I'll send bumps to 5.10 and the BSPs this morning.
>
> Bruce
>
>> I'm sharing the full info in case you spot any patterns I don't! :)
>>
>> In summary, we're down to these and the lttng-modules issue which
>> appears when we start checking .debug files in buildpaths (patch added
>> and reverted in master-next currently).
>>
>> Cheers,
>>
>> Richard
>>
>>
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#167925):https://lists.openembedded.org/g/openembedded-core/message/167925
> Mute This Topic:https://lists.openembedded.org/mt/92248896/4354175
> Group Owner:openembedded-core+owner@lists.openembedded.org
> Unsubscribe:https://lists.openembedded.org/g/openembedded-core/unsub  [alhe@linux.microsoft.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>

[-- Attachment #2: Type: text/html, Size: 9890 bytes --]