From: Baruch Siach via buildroot <buildroot@buildroot.org>
To: Martin Contamin <martin.contamin@murena.io>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] support/libtool: make v2.6 patch apply to libtool 2.6.0 ltmain.sh
Date: Wed, 21 Oct 2026 07:13:03 +0300 [thread overview]
Message-ID: <87v76vitdc.fsf@tarshish> (raw)
In-Reply-To: <9993a016-508d-49a8-977d-f5e712c12a6d@murena.io> (Martin Contamin's message of "Tue, 20 Oct 2026 10:13:49 +0200")
Hi Martin,
Please keep the buildroot list on Cc.
On Tue, Oct 20 2026, Martin Contamin wrote:
> Thanks for the pointer. The per-version split is indeed cleaner than
> my single version-agnostic patch, so I'm happy to drop mine in favor
> of his.
>
> See you on my next contribution!
Thanks for your contribution.
It would be nice if you modify the status of your patch in patchwork as
described in the Buildroot manual near the end of section 22.5.4 (Patch
revision changelog):
https://buildroot.org/downloads/manual/manual.html#submitting-patches
Thanks,
baruch
> Best regards,
>
> Martin Contamin
>
> Le 19/10/2026 à 20:30, Baruch Siach via buildroot a écrit :
>
> Hi Martin,
>
> On Mon, Oct 19 2026, Martin Contamin via buildroot wrote:
>
> Commit 5dbba2616f ("package/pkg-autotools.mk: also handle libtool 2.6.x")
> enabled the libtool 2.6 patch for packages shipping an ltmain.sh
> generated with libtool 2.6.0, such as libmodbus 3.1.12. But this patch
> was written against libtool 2.6.2, where the -static-libtool-libs
> pattern was merged with --static and -Bstatic. In libtool 2.6.0 the
> corresponding context line only reads "-static-libtool-libs)", so
> hunk #4 failed to apply and the build stopped at the "Patching libtool"
> step.
>
> Remove the context lines around this deletion so the hunk only relies
> on the deleted lines themselves, which are identical in both versions;
> the patch now applies to ltmain.sh from both libtool 2.6.0 and 2.6.2.
>
> Fixes: https://autobuild.buildroot.org/results/11f3c460407c816d9829f101f0ee55e4b03965cd/
>
> Signed-off-by: Martin Contamin <martin.contamin@murena.io>
>
>
> You might want to take a look at the patch Thomas suggested:
>
> https://patchwork.buildroot.org/project/buildroot/patch/20261011074658.1888569-1-thomas.petazzoni@bootlin.com/
>
> baruch
>
> ---
> support/libtool/buildroot-libtool-v2.6.patch | 8 +-------
> 1 file changed, 1 insertion(+), 7 deletions(-)
>
> diff --git a/support/libtool/buildroot-libtool-v2.6.patch b/support/libtool/buildroot-libtool-v2.6.patch
> index b3968b1289..060acaad5d 100644
> --- a/support/libtool/buildroot-libtool-v2.6.patch
> +++ b/support/libtool/buildroot-libtool-v2.6.patch
> @@ -42,19 +42,13 @@ Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
> if test yes = "$build_libtool_libs" && test -z "$link_static_flag"; then
> func_warning "complete static linking is impossible in this configuration"
> fi
> -@@ -7072,12 +7076,6 @@
> - fi
> - prefer_static_libs=yes
> - ;;
> +@@ -7072,6 +7076,0 @@
> - -static)
> - if test -z "$pic_flag" && test -n "$link_static_flag"; then
> - dlopen_self=$dlopen_self_static
> - fi
> - prefer_static_libs=built
> - ;;
> - -static-libtool-libs | --static | -Bstatic)
> - if test -z "$pic_flag" && test -n "$link_static_flag"; then
> - dlopen_self=$dlopen_self_static
> @@ -7393,7 +7391,8 @@
> prevarg=$arg
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-10-21 4:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 18:00 [Buildroot] [PATCH 0/1] first contribution: fix libtool v2.6 patch for libtool 2.6.0 Martin Contamin via buildroot
2026-10-19 18:00 ` [Buildroot] [PATCH 1/1] support/libtool: make v2.6 patch apply to libtool 2.6.0 ltmain.sh Martin Contamin via buildroot
2026-10-19 18:30 ` Baruch Siach via buildroot
[not found] ` <9993a016-508d-49a8-977d-f5e712c12a6d@murena.io>
2026-10-21 4:13 ` Baruch Siach via buildroot [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=87v76vitdc.fsf@tarshish \
--to=buildroot@buildroot.org \
--cc=baruch@tkos.co.il \
--cc=martin.contamin@murena.io \
/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