Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libtool: use a different way to avoid autoreconfiguration
Date: Thu, 20 Mar 2014 00:25:04 +0100	[thread overview]
Message-ID: <20140320002504.0cebf7d5@skate> (raw)
In-Reply-To: <1395270180-12701-1-git-send-email-arnout@mind.be>

Dear Arnout Vandecappelle (Essensium/Mind),

On Thu, 20 Mar 2014 00:03:00 +0100, Arnout Vandecappelle
(Essensium/Mind) wrote:
> In 4268d39, a patch was added to update libtool.m4 for MIPS n64 targets.
> However, this caused the configure script to be regenerated during the
> build steps, which in turn caused build failures on Fedora 12 hosts. In
> ed73d1d, this was fixed by patching the installed libtool.m4 file
> instead of the source file.
> 
> However, ed73d1d did not take into account that the target libtool will
> also install libtool.m4 to staging, and that that version has
> precedence over the one in HOST_DIR.
> 
> Therefore, this patch takes a different approach: the source file is
> patched in the usual way, and instead the reconfigure is avoided by
> touching the generated files.
> 
> On the target, we also cannot use the AUTORECONF mechanism because of
> some mysterious Makefile.inc file. So just use the same approach and
> wait for upstream to make a new release.

Shouldn't we mark libtool on the target as something deprecated? We
have already removed the support for autoconf and automake on the
target, so having libtool seems quite useless, no?

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2014-03-19 23:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-19 23:03 [Buildroot] [PATCH] libtool: use a different way to avoid autoreconfiguration Arnout Vandecappelle
2014-03-19 23:25 ` Thomas Petazzoni [this message]
2014-03-20  6:34   ` Arnout Vandecappelle
2014-03-20 14:54     ` Thomas Petazzoni
2014-03-20 16:16       ` Arnout Vandecappelle
2014-04-17 21:38 ` Thomas Petazzoni
2014-04-18  8:12   ` Arnout Vandecappelle
2014-04-18  8:20     ` Thomas Petazzoni

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=20140320002504.0cebf7d5@skate \
    --to=thomas.petazzoni@free-electrons.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