From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: "Khem Raj" <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 3/3] ccache: Upgrade to 4.6.2
Date: Thu, 25 Aug 2022 12:02:48 +0200 [thread overview]
Message-ID: <20220825120248.66f9b613@booty> (raw)
In-Reply-To: <CAMKF1src=s9CWjps=i1PBNw=Q6BuEwE=FpJi9O9R2en3A+3BCA@mail.gmail.com>
Hi Khem,
On Wed, 24 Aug 2022 09:57:13 -0700
"Khem Raj" <raj.khem@gmail.com> wrote:
> On Wed, Aug 24, 2022 at 9:52 AM Luca Ceresoli <luca.ceresoli@bootlin.com> wrote:
> >
> > Hi Khem,
> >
> > On Tue, 23 Aug 2022 11:01:51 -0700
> > "Khem Raj" <raj.khem@gmail.com> wrote:
> >
> > > Fix build with musl
> > >
> > > Signed-off-by: Khem Raj <raj.khem@gmail.com>
> >
> > AB testing with these 3 patches I got an error in test_ccache_tool. Not
> > sure these patches are guilty, but they are the only ones
> > ccache-related.
> >
> > Maybe you can have a look?
> >
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/79/builds/4037/steps/15/logs/stdio
> >
>
> drop the upgrade patch
>
> [3/3] ccache: Upgrade to 4.6.2
>
> and see if that helps. We dont really need that for gcc 12 issue.
My build with the first two patches + the gcc 12.2.0 upgrade succeeded.
Thanks!
Luca
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2022-08-25 10:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 18:01 [PATCH 1/3] ccache: Update the patch status Khem Raj
2022-08-23 18:01 ` [PATCH 2/3] ccache: Fix build with gcc12 on musl Khem Raj
2022-08-23 18:01 ` [PATCH 3/3] ccache: Upgrade to 4.6.2 Khem Raj
2022-08-24 16:52 ` [OE-core] " Luca Ceresoli
2022-08-24 16:57 ` Khem Raj
2022-08-24 17:04 ` Khem Raj
2022-08-25 10:02 ` Luca Ceresoli [this message]
2022-08-25 14:36 ` Khem Raj
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=20220825120248.66f9b613@booty \
--to=luca.ceresoli@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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