Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Neumann <s.neumann@raumfeld.com>
To: buildroot@busybox.net
Subject: [Buildroot] Question about libtool patching
Date: Mon, 05 Oct 2009 11:30:12 +0200	[thread overview]
Message-ID: <1254735012.5772.16.camel@sven> (raw)
In-Reply-To: <1254681715.25803.42.camel@coalu.atr>

On Sun, 2009-10-04 at 20:41 +0200, Lionel Landwerlin wrote:
> [PATCH] Prevent libtool patching before autoreconf when autoreconf is required
> 
> Signed-off-by: Lionel Landwerlin <lionel.landwerlin@openwide.fr>
> ---
>  package/Makefile.autotools.in |    3 ++-
>  1 files changed, 2 insertions(+), 1 deletions(-)
> 
> diff --git a/package/Makefile.autotools.in b/package/Makefile.autotools.in
> index c4c4b1c..d36c884 100644
> --- a/package/Makefile.autotools.in
> +++ b/package/Makefile.autotools.in
> @@ -188,7 +188,8 @@ $(BUILD_DIR)/%/.stamp_extracted:
>  $(BUILD_DIR)/%/.stamp_libtool_patch:
>  	$(call MESSAGE,"Patching libtool")
>  # if the package uses libtool, patch it for cross-compiling in buildroot
> -	$(Q)if test "$($(PKG)_LIBTOOL_PATCH)" = "YES"; then \
> +	$(Q)if test "$($(PKG)_LIBTOOL_PATCH)" = "YES" -a \
> +	"$($(PKG)_AUTORECONF)" != "YES"; then \
>  	for i in `find $(@D) -name ltmain.sh`; do \
>  		toolchain/patch-kernel.sh $${i%/*} package buildroot-libtool.patch; \
>  		done \

Totally makes sense to me and we also ran into problems because of this.
I have applied this in our tree and it seems to work fine. Actually, it
finally fixed a long-standing problem :)

Tested-By: Sven Neumann <s.neumann@raumfeld.com>


Sven

  reply	other threads:[~2009-10-05  9:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-04 18:40 [Buildroot] Question about libtool patching Lionel Landwerlin
2009-10-04 18:41 ` Lionel Landwerlin
2009-10-05  9:30   ` Sven Neumann [this message]
2009-10-05 12:00     ` Lionel Landwerlin
2009-10-05 12:12   ` Peter Korsgaard

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=1254735012.5772.16.camel@sven \
    --to=s.neumann@raumfeld.com \
    --cc=buildroot@busybox.net \
    /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