Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] Reproducible build issues with buildpaths - take 2
Date: Fri, 08 Jul 2022 14:47:09 +0100	[thread overview]
Message-ID: <77dd3defcb6908755d06585d4cfb69a523626a22.camel@linuxfoundation.org> (raw)
In-Reply-To: <CADkTA4O0Ej3HKMPtwoq_iBue2P43gicwx8rfFKyLY5d3jNTP_A@mail.gmail.com>

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



  reply	other threads:[~2022-07-08 13:47 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 [this message]
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
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=77dd3defcb6908755d06585d4cfb69a523626a22.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --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