From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: Khem Raj <raj.khem@gmail.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] binutils: Upgrade to 2.38 release
Date: Sun, 13 Feb 2022 17:45:48 +0000 [thread overview]
Message-ID: <9e65fd13504219c3b84fe17e844a368176cfcb6d.camel@linuxfoundation.org> (raw)
In-Reply-To: <CADkTA4N-yxzSMuhVpPWyddcaOLkmBpEwgs4TECr8SNup8tE__Q@mail.gmail.com>
On Sun, 2022-02-13 at 11:27 -0500, Bruce Ashfield wrote:
> On Sun, Feb 13, 2022 at 9:27 AM Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> >
> > On Sat, 2022-02-12 at 20:25 -0500, Bruce Ashfield wrote:
> > > On Sat, Feb 12, 2022 at 12:27 PM Khem Raj <raj.khem@gmail.com> wrote:
> > > >
> > > > On Sat, Feb 12, 2022 at 5:27 AM Richard Purdie
> > > > <richard.purdie@linuxfoundation.org> wrote:
> > > > >
> > > > > On Thu, 2022-02-10 at 10:37 -0800, Khem Raj wrote:
> > > > > > Release Notes are here [1]
> > > > > >
> > > > > > [1] https://lists.gnu.org/archive/html/info-gnu/2022-02/msg00009.html
> > > > > >
> > > > > > Signed-off-by: Khem Raj <raj.khem@gmail.com>
> > > > >
> > > > > So far there was a mingw failure:
> > > > >
> > > > > https://autobuilder.yoctoproject.org/typhoon/#/builders/89/builds/4729
> > > >
> > > > This seems a race
> > > >
> > > > > i686-w64-mingw32-dlltool: lib32/libd3dcompiler_35.a: error reading
> > > > D3DCompiler_dll_t.o: No such file or directory
> > > > > Assembler messages:
> > > > > Error: can't open D3DCompiler_dll_h.s for reading: No such file or directory
> > > > > i686-w64-mingw32-dlltool: i686-w64-mingw32-as exited with status 1
> > > > > i686-w64-mingw32-dlltool: failed to open temporary head file:
> > > > D3DCompiler_dll_h.o: No such file or directory
> > > > > Makefile:82403: recipe for target 'lib32/libd3dcompiler_35.a' failed
> > > > > make[1]: *** [lib32/libd3dcompiler_35.a] Error 1
> > > >
> > > >
> > > >
> > > > >
> > > > > and a qemuppc kernel build issue:
> > > > >
> > > > > https://autobuilder.yoctoproject.org/typhoon/#/builders/63/builds/4688
> > > > > https://autobuilder.yoctoproject.org/typhoon/#/builders/107/builds/2632
> > > > >
> > > >
> > > > this needs a kernel patch backported ( looking towards Bruce to include it)
> > > >
> > > > https://lore.kernel.org/lkml/20220211005113.1361436-1-anders.roxell@linaro.org/T/
> > >
> > > I've grabbed this change, and the riscv one, and applied them to 5.10 and 5.15.
> > >
> > > The pull request is on the list for the binutils fixes and -stable updates.
> >
> > Thanks Bruce. Unfortunately this doesn't seem to fix the qemuppc build issues:
> >
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/63/builds/4691
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/107/builds/2634
>
> I see a patch from January on lkml with the shortlog: "powerpc/mm:
> Switch obsolete dssall to .long", which may be related.
>
> But I'm not setup to see the build issues myself this weekend, but can
> start looking more closely on Monday.
FWIW that sounds highly likely. If I get time I'll try and add a patch to the
build, see if it helps.
Cheers,
Richard
next prev parent reply other threads:[~2022-02-13 17:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 18:37 [PATCH] binutils: Upgrade to 2.38 release Khem Raj
2022-02-10 19:19 ` Khem Raj
2022-02-10 19:31 ` Bruce Ashfield
2022-02-12 13:27 ` [OE-core] " Richard Purdie
2022-02-12 17:27 ` Khem Raj
2022-02-13 1:25 ` Bruce Ashfield
2022-02-13 14:27 ` Richard Purdie
2022-02-13 16:27 ` Bruce Ashfield
2022-02-13 17:45 ` Richard Purdie [this message]
2022-02-13 20:30 ` Richard Purdie
2022-02-15 14:31 ` Bruce Ashfield
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=9e65fd13504219c3b84fe17e844a368176cfcb6d.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bruce.ashfield@gmail.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