Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: mathieu.dubois-briand@bootlin.com,
	Jaipaul Cheernam <jaipaul.cheernam@est.tech>,
	openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] libtool: upgrade 2.5.4 -> 2.6.2
Date: Wed, 05 Aug 2026 14:37:46 +0100	[thread overview]
Message-ID: <304c833b3d0bae2b9013a34f775f2d0bb405b2ff.camel@linuxfoundation.org> (raw)
In-Reply-To: <DKH1HUP3GM0Z.2U848KFCSC5C0@bootlin.com>

On Wed, 2026-08-05 at 15:20 +0200, Mathieu Dubois-Briand via
lists.openembedded.org wrote:
> On Tue Aug 4, 2026 at 2:05 PM CEST, Jaipaul Cheernam wrote:
> > - Upgrade to first stable release of 2.6 series:
> >   https://savannah.gnu.org/news/?id=10914
> > 
> > - Notable changes since 2.5.4:
> >   - New libtool-next-version tool for guiding library version
> > updates
> >   - Objective-C and Objective-C++ tagging support (OBJC, OBJCXX)
> >   - Allow statically linking clang_rt archives by absolute path
> >   - Fix overlinking of dependency libraries on ELF systems
> >   - Pass --target architecture flag and resource-dir for Clang
> >   - SlimCC compiler support
> >   - MSVC and MSYS2 improvements
> > 
> > - Drop 0005-libtool-Check-for-static-libs-for-internal-compiler-
> > .patch
> >   has been merged upstream.
> > 
> > - Refresh 0003-libtool-remove-help2man-dependency.patch for new
> > line
> >   offsets and to also remove the libtoolnextv_1 man page target
> > added
> >   in 2.6.2.
> > 
> > Signed-off-by: Jaipaul Cheernam <jaipaul.cheernam@est.tech>
> > ---
> 
> Hi Jaipaul,
> 
> Thanks for the upgrade.
> 
> It looks like this breaks build for ricv platforms (qemuriscv64
> MACHINE):
> 
> ERROR: libunwind-1.8.3-r0 do_compile: Execution of
> '/srv/pokybuild/yocto-
> worker/qemuriscv64/build/build/tmp/work/riscv64imafdc-poky-
> linux/libunwind/1.8.3/temp/run.do_compile.1756282' failed with exit
> code 1
> ...
> > riscv64-poky-linux-gcc: error: unrecognized command-line option '-
> > WCClinker'; did you mean '-Xlinker'?
> > make[2]: *** [Makefile:4151: libunwind.la] Error 1
> > make[2]: Leaving directory '/srv/pokybuild/yocto-
> > worker/qemuriscv64/build/build/tmp/work/riscv64imafdc-poky-
> > linux/libunwind/1.8.3/build/src'
> > make[1]: *** [Makefile:2932: all] Error 2
> > make[1]: Leaving directory '/srv/pokybuild/yocto-
> > worker/qemuriscv64/build/build/tmp/work/riscv64imafdc-poky-
> > linux/libunwind/1.8.3/build/src'
> > make: *** [Makefile:625: all-recursive] Error 1
> > ERROR: oe_runmake failed
> > WARNING: exit code 1 from a shell command.
> 
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/45/builds/2039
> 
> Can you have a look at the issue?

I have a fix for this in master-next which tested successfully
overnight. Khem also agreed with it so I'll get it sent out.

Cheers,

Richard


      reply	other threads:[~2026-08-05 13:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-04 12:05 [PATCH] libtool: upgrade 2.5.4 -> 2.6.2 Jaipaul Cheernam
2026-08-05 13:20 ` [OE-core] " Mathieu Dubois-Briand
2026-08-05 13:37   ` 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=304c833b3d0bae2b9013a34f775f2d0bb405b2ff.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=jaipaul.cheernam@est.tech \
    --cc=mathieu.dubois-briand@bootlin.com \
    --cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox