From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Schmidt, Adriaan" <adriaan.schmidt@siemens.com>,
Khem Raj <raj.khem@gmail.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Cc: "ross.burton@arm.com" <ross.burton@arm.com>
Subject: Re: [OE-core] [PATCH v2 1/1] libunwind: 1.8.1
Date: Thu, 10 Apr 2025 12:46:35 +0100 [thread overview]
Message-ID: <ca371ee8ce93c922cfa744c6ab7091979485cd68.camel@linuxfoundation.org> (raw)
In-Reply-To: <AS4PR10MB5318838632DD23699735E538EDB72@AS4PR10MB5318.EURPRD10.PROD.OUTLOOK.COM>
On Thu, 2025-04-10 at 09:43 +0000, Schmidt, Adriaan wrote:
> Khem Raj <raj.khem@gmail.com>,Freitag, 4. April 2025 03:03:
> > On 4/3/25 1:19 AM, Adriaan Schmidt via lists.openembedded.org
> > wrote:
> > >
> > > -COMPATIBLE_HOST:riscv32 = "null"
> > > +COMPATIBLE_HOST:ppc:libc-musl = "null"
> >
> > Why do we need this to do this ? I see that a patch is added and
> > one is
> > removed to support ppc32/musl support.
>
> After some more investigation: There are issues on ppc32/musl when
> building without "--disable-tests".
>
> Will post a v3 to:
> - drop this line
> - drop the "--disable-tests"
> - add "-latomic" to ppc32/musl LDFLAGS to fix the build
Sounds good thanks. The commit also needs a proper commit message and
signed off by line.
Cheers,
Richard
prev parent reply other threads:[~2025-04-10 11:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-03 8:19 [PATCH v2 0/1] libunwind: update 1.6.2 -> 1.8.1 Adriaan Schmidt
2025-04-03 8:19 ` [PATCH v2 1/1] libunwind: 1.8.1 Adriaan Schmidt
2025-04-04 1:03 ` [OE-core] " Khem Raj
2025-04-10 9:43 ` Adriaan Schmidt
2025-04-10 11:46 ` Richard Purdie [this message]
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=ca371ee8ce93c922cfa744c6ab7091979485cd68.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=adriaan.schmidt@siemens.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=ross.burton@arm.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