From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2013-06-04
Date: Wed, 5 Jun 2013 18:48:36 +0200 [thread overview]
Message-ID: <20130605184836.6ea2b205@skate> (raw)
In-Reply-To: <20130605182924.71a07679@skate>
Hello,
On Wed, 5 Jun 2013 18:29:24 +0200, Thomas Petazzoni wrote:
> > host-libftdi-0.19 | 20
>
> Those issues are caused by the bump of libtool, from the testing I
> could do. Reverting libtool to the previous version "solves" the
> problem.
>
> The thing that happens is that libftdi (for the target) has
> AUTORECONF=YES, but not host-libftdi. So libftdi gets autoreconfigured,
> and then when host-libftdi is being built, even though we don't have
> AUTORECONF=YES, when starting the build, it does execute
> 'CDPATH="${ZSH_VERSION+.}:" && cd .
> && /bin/bash /home/test/outputs/libftdi/build/host-libftdi-0.19/missing
> --run aclocal-1.11 ' and it ends up failing.
Ok, the reason it does execute "missing" and does a kind of automatic
autoreconf is because we have one patch that modifies configure.in. So
configure.in is more recent than the configure script itself. When
libtool/autoconf/automake has not been built before host-libftdi, then
this automatic autoreconf cannot proceed:
CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/bash /home/test/outputs/toto/build/host-libftdi-0.19/missing --run aclocal-1.11
/home/test/outputs/toto/build/host-libftdi-0.19/missing: line 52: aclocal-1.11: command not found
WARNING: `aclocal-1.11' is missing on your system. You should only need it if
you modified `acinclude.m4' or `configure.in'. You might want
to install the `Automake' and `Perl' packages. Grab them from
any GNU archive site.
CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/bash /home/test/outputs/toto/build/host-libftdi-0.19/missing --run autoconf
cd . && /bin/bash /home/test/outputs/toto/build/host-libftdi-0.19/missing --run automake-1.11 --foreign
/home/test/outputs/toto/build/host-libftdi-0.19/missing: line 52: autoconf: command not found
/home/test/outputs/toto/build/host-libftdi-0.19/missing: line 52: automake-1.11: command not found
WARNING: `autoconf' is missing on your system. You should only need it if
you modified `configure.in'. You might want to install the
`Autoconf' and `GNU m4' packages. Grab them from any GNU
archive site.
and it in facts makes the thing work.
However, when this "automatic autoreconf" is done, and an
automake/autoconf/libtool set of tools, with the latest libtool, has
already been built and installed, then it generates some wrong stuff.
An easy fix is to add:
HOST_LIBFTDI_AUTORECONF = YES
to libftdi.mk. It doesn't really explain why it was working with
libtool 2.2 and no longer with libtool 2.4, but it works.
Thoughts?
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-06-05 16:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2013-06-04 Thomas Petazzoni
2013-06-05 16:29 ` Thomas Petazzoni
2013-06-05 16:48 ` Thomas Petazzoni [this message]
2013-06-05 18:52 ` Peter Korsgaard
2013-06-05 17:00 ` Yann E. MORIN
2013-06-05 17:05 ` Gustavo Zacarias
2013-06-05 17:17 ` Yann E. MORIN
2013-06-05 18:00 ` Yann E. MORIN
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=20130605184836.6ea2b205@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 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.