All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] squid: fix automake breakage
Date: Mon, 12 Jan 2015 17:05:06 -0300	[thread overview]
Message-ID: <54B428F2.9010102@zacarias.com.ar> (raw)
In-Reply-To: <20150112205811.6cb75c60@free-electrons.com>

On 01/12/2015 04:58 PM, Thomas Petazzoni wrote:

> Even though I am not too happy about the fix, I applied it in order to
> fix the autobuilder issues.
> 
> I'd like to understand better why the libltdl bundled in Squid thinks
> it should autoreconf itself.

I couldn't find the why yet, but i did find that the fact that we don't
autoreconf libtool causes it since libtool 2.4.4 is packaged with
automake 1.14.1.
In a project where host-libtool (i.e. autoreconfs) see:

output/target/usr/share/libtool/aclocal.m4 ->
[AM_AUTOMAKE_VERSION([1.14.1])dnl
(circa line 54)

Since libtoolize blindly copies this at some point libltdl
automatically-triggered autoreconf uses this version (actually
am__api_version='1.14' in line 35) to call it, hence breaking.

One solution would be to autoreconf libtool which doesn't seem
straightforward.
Another is to "hack" libtool and s/1.14.1/1.15/ + s/1.14/1.15/ that file
(tested to work).
We could also define ACLOCAL & co in the autotools infra, it shouldn't
hurt any package, though i haven't tested this.

In any case it seems to be a problem limited to squid only or we would
have seen more of these.

Regards.

      reply	other threads:[~2015-01-12 20:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-08  1:09 [Buildroot] [PATCH] squid: fix automake breakage Gustavo Zacarias
2015-01-08  8:28 ` Thomas Petazzoni
2015-01-08 17:34   ` Gustavo Zacarias
2015-01-10 21:30 ` Bernd Kuhls
2015-01-12 19:58 ` Thomas Petazzoni
2015-01-12 20:05   ` Gustavo Zacarias [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=54B428F2.9010102@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --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.