[Buildroot] [PATCH] libtool: use a different way to avoid autoreconfiguration

Thomas Petazzoni thomas.petazzoni at free-electrons.com
Wed Mar 19 23:25:04 UTC 2014


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



More information about the buildroot mailing list