Re: [OE-core] [PATCH] libtool: upgrade 2.5.4 -> 2.6.2

["Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>]

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?

Thanks,
Mathieu

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com