From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@gmail.com>,
Alejandro Hernandez Samaniego <Alejandro.Hernandez@microsoft.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] Reproducible build issues with buildpaths - take 2
Date: Tue, 12 Jul 2022 11:44:14 +0100 [thread overview]
Message-ID: <ce91dc24e3a6d7c011c6b3f0bb79ac404f597a1f.camel@linuxfoundation.org> (raw)
In-Reply-To: <CADkTA4P=BDAYiZUCN+hhqpyUUAoOckX+RMphyZiwmci3nFrkOA@mail.gmail.com>
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
next prev parent reply other threads:[~2022-07-12 10:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 11:07 Reproducible build issues with buildpaths - take 2 Richard Purdie
2022-07-08 13:23 ` [OE-core] " Alex Kiernan
2022-07-08 13:37 ` Bruce Ashfield
2022-07-08 13:47 ` Richard Purdie
2022-07-11 0:29 ` Bruce Ashfield
[not found] ` <17009EE9B42D5D4F.21011@lists.openembedded.org>
2022-07-11 2:27 ` Bruce Ashfield
[not found] ` <1700A558F3D5D3E4.14864@lists.openembedded.org>
2022-07-11 3:06 ` Bruce Ashfield
2022-07-12 10:44 ` Richard Purdie [this message]
2022-07-12 12:31 ` Bruce Ashfield
2022-07-12 20:26 ` Alejandro Enedino Hernandez Samaniego
2022-07-09 1:55 ` Christopher Clark
[not found] ` <170006698A73A72B.21011@lists.openembedded.org>
2022-07-10 5:54 ` Christopher Clark
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=ce91dc24e3a6d7c011c6b3f0bb79ac404f597a1f.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=Alejandro.Hernandez@microsoft.com \
--cc=bruce.ashfield@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