From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Jaipaul Cheernam <jaipaul.cheernam@est.tech>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Cc: Khem Raj <raj.khem@gmail.com>
Subject: Re: [OE-core] [PATCH 5/9] libtool: 2.5.4 -> 2.6.2
Date: Thu, 06 Aug 2026 22:26:31 +0100 [thread overview]
Message-ID: <8569f35daf6584ca49d9d7b0a599847266494869.camel@linuxfoundation.org> (raw)
In-Reply-To: <DU7PPF66507B2D7F686F5CF25824702B130F3D42@DU7PPF66507B2D7.EURP189.PROD.OUTLOOK.COM>
On Tue, 2026-08-04 at 21:36 +0000, Jaipaul Cheernam wrote:
> Actually , I also sent a patch for lib tool upgrade on
> masterhttps://lists.openembedded.org/g/openembedded-core/message/2427
> 34
>
> I reproduced it locally and dug into why. The root cause is that -
> WCClinker was never a valid libtool flag (only -XCClinker is).
> It worked in 2.5.4 by accident, but 2.6.2 widened the passthrough
> pattern from -Wa,*|-Werror|-Werror=* to -W* (for LTO warnings),
> so now -WCClinker gets passed directly to gcc which rejects it.
It was fixed upstream here:
https://github.com/libunwind/libunwind/commit/8e6a348b94a1b8e77ec2a086ff27ea9b78357d71
> I'd go with --disable-cxx-exceptions for riscv64 — consistent with
> all other arches. The -WCClinker typo can be reported upstream to
> libunwind separately.
>
and upstream do unconditionally disable it now:
https://github.com/libunwind/libunwind/commit/bda7a2267b8385b869b4eef6a2fcdd696b887ed8
:)
Cheers,
Richard
next prev parent reply other threads:[~2026-08-06 21:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 12:23 [PATCH 1/9] libva-utils: 2.23.0 -> 2.24.0 Richard Purdie
2026-08-04 12:23 ` [PATCH 2/9] xvinfo: Upgrade 1.1.5 -> 1.1.6 Richard Purdie
2026-08-04 12:23 ` [PATCH 3/9] xwininfo: Upgrade 1.1.6 -> 1.1.7 Richard Purdie
2026-08-04 12:23 ` [PATCH 4/9] xmodmap: Upgrade 1.0.11 -> 1.0.12 Richard Purdie
2026-08-04 12:36 ` Patchtest results for " patchtest
2026-08-04 12:23 ` [PATCH 5/9] libtool: 2.5.4 -> 2.6.2 Richard Purdie
2026-08-04 12:23 ` [PATCH 6/9] ffmpeg: upgrade 8.1.2 -> 9.0 Richard Purdie
2026-08-04 12:23 ` [PATCH 7/9] libadwaita: upgrade 1.9.2 -> 1.9.3 Richard Purdie
2026-08-04 12:23 ` [PATCH 8/9] python3-cffi: upgrade 2.1.0 -> 2.1.1 Richard Purdie
2026-08-04 12:36 ` Patchtest results for " patchtest
2026-08-04 12:23 ` [PATCH 9/9] python3-pyproject-metadata: upgrade 0.11.0 -> 0.12.1 Richard Purdie
2026-08-04 12:36 ` Patchtest results for [PATCH 1/9] libva-utils: 2.23.0 -> 2.24.0 patchtest
[not found] ` <18C899AE0F118A3D.1990914@lists.openembedded.org>
2026-08-04 17:00 ` [OE-core] [PATCH 5/9] libtool: 2.5.4 -> 2.6.2 Richard Purdie
[not found] ` <18C8A8C4FB56E625.3417489@lists.openembedded.org>
2026-08-04 20:12 ` Richard Purdie
2026-08-04 21:36 ` Jaipaul Cheernam
2026-08-06 21:26 ` Richard Purdie [this message]
2026-08-04 21:58 ` 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=8569f35daf6584ca49d9d7b0a599847266494869.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=jaipaul.cheernam@est.tech \
--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