From: Trevor Woerner <twoerner@gmail.com>
To: yocto-patches@lists.yoctoproject.org
Subject: Re: [yocto-patches] [meta-rockchip][PATCH] linux-torvalds-next: ignore TMPDIR issues
Date: Mon, 15 Jul 2024 11:23:42 -0400 [thread overview]
Message-ID: <20240715152342.GA10926@localhost> (raw)
In-Reply-To: <5afa76ad9a887b364e4a4640959de3332330bd5a.camel@linuxfoundation.org>
On Mon 2024-07-15 @ 03:47:11 PM, Richard Purdie via lists.yoctoproject.org wrote:
> On Mon, 2024-07-15 at 10:31 -0400, Trevor Woerner via
> lists.yoctoproject.org wrote:
> > oe-core has raised the status of some checks from warnings to errors.
> > Ignore
> > the "...contains references to TMPDIR..." error when building the
> > torvalds-next kernel.
> >
> > Signed-off-by: Trevor Woerner <twoerner@gmail.com>
> > ---
> > recipes-kernel/linux/linux-torvalds-next_git.bb | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/recipes-kernel/linux/linux-torvalds-next_git.bb
> > b/recipes-kernel/linux/linux-torvalds-next_git.bb
> > index c0ac1de22005..6f3db7c61bdf 100644
> > --- a/recipes-kernel/linux/linux-torvalds-next_git.bb
> > +++ b/recipes-kernel/linux/linux-torvalds-next_git.bb
> > @@ -5,6 +5,7 @@ SECTION = "kernel"
> > LICENSE = "GPL-2.0-only"
> > LIC_FILES_CHKSUM =
> > "file://COPYING;md5=6bc538ed5bd9a7fc9398086aedcd7e46"
> >
> > +ERROR_QA:remove = "buildpaths"
> > DEFAULT_PREFERENCE = "-1"
> > COMPATIBLE_MACHINE = "^$"
> > COMPATIBLE_MACHINE:radxa-zero-3 = "radxa-zero-3"
>
> You may want to add that to WARN_QA so you remember to at least look at
> them a some point. They're a sign of non-reproducible builds for a
> start and break hash equivalence sstate reuse.
When I added support for these two MACHINEs in meta-rockchip
(radxa-zero-3{e|w}), support wasn't even yet available in linux-yocto-dev, I
had to use Linus' -next tree to get support (which is why I created a
linux-torvalds-next recipe). In time support will hopefully
trickle down into linux-yocto-dev, then linux-yocto, at which points I will
discard linux-torvalds-next for fully upstream oe-core support.
I could add a WARN for this, but I'm probably not going to get around to
looking into it and fixing it, I doubt anyone else will (since it's a recipe
specific to meta-rockchip), and fixing it won't be required once we switch to
something from oe-core.
>
> Cheers,
>
> Richard
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#430): https://lists.yoctoproject.org/g/yocto-patches/message/430
> Mute This Topic: https://lists.yoctoproject.org/mt/107232153/900817
> Group Owner: yocto-patches+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/yocto-patches/leave/13168745/900817/63955952/xyzzy [twoerner@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>
next prev parent reply other threads:[~2024-07-15 15:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 14:31 [meta-rockchip][PATCH] linux-torvalds-next: ignore TMPDIR issues Trevor Woerner
2024-07-15 14:42 ` [yocto-patches] " Quentin Schulz
2024-07-15 14:47 ` Richard Purdie
2024-07-15 15:23 ` Trevor Woerner [this message]
2024-07-16 15:07 ` Trevor Woerner
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=20240715152342.GA10926@localhost \
--to=twoerner@gmail.com \
--cc=yocto-patches@lists.yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.