All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Yegor Yefremov <yegorslists@googlemail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/pkg-autotools.mk: LIBTOOL_PATCH_HOOK: also handle libtool 2.6.x
Date: Sat, 10 Oct 2026 17:17:57 +0200	[thread overview]
Message-ID: <aspXAp1ro_z_JWNK@windsurf> (raw)
In-Reply-To: <20260924134109.2415498-1-yegorslists@googlemail.com>

On Thu, Sep 24, 2026 at 03:41:09PM +0200, Yegor Yefremov via buildroot wrote:
> Fixes:
> https://autobuild.buildroot.org/results/e6159cee14f84569c85a61f77824b2b58d68a4bc/
> 
> Libtool 2.6.x is starting to be used by upstreams when generating
> release tarballs (e.g. cryptsetup-2.8.8). As LIBTOOL_PATCH_HOOK does
> not know about it, ltmain.sh is left unpatched, so libtool relinks
> libraries at install time and adds -L/usr/lib, which is rejected by
> the toolchain wrapper:
> 
> i686-buildroot-linux-gnu-gcc: ERROR: unsafe header/library path used in cross-compilation: '-L/usr/lib'
> 
> The v2.4.4 patch no longer applies cleanly, so add a v2.6 variant,
> rebased on libtool 2.6.2, and use it for 2.6.x versions.
> 
> Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
> Assisted-by: Claude:claude-opus-5

I've adjusted .checkpackageignore to silence some warnings, and
applied to master. Thanks!

Best regards,

Thomas Petazzoni
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2026-10-10 15:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-24 13:41 [Buildroot] [PATCH] package/pkg-autotools.mk: LIBTOOL_PATCH_HOOK: also handle libtool 2.6.x Yegor Yefremov via buildroot
2026-10-10 15:17 ` Thomas Petazzoni 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=aspXAp1ro_z_JWNK@windsurf \
    --to=buildroot@buildroot.org \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=yegorslists@googlemail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.