From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] squid: fix automake breakage
Date: Thu, 08 Jan 2015 14:34:38 -0300 [thread overview]
Message-ID: <54AEBFAE.2020706@zacarias.com.ar> (raw)
In-Reply-To: <20150108092820.09875bec@free-electrons.com>
On 01/08/2015 05:28 AM, Thomas Petazzoni wrote:
> We seem to have the same problem with host-guile:
> http://autobuild.buildroot.org/results/634/634e342f7f384fc6eba11872aa2d680c0d8dc98a/build-end.log.
> So I'm not sure a package-specific solution is appropriate here, no?
For guile the problem is different, it's the fact that we're patching
configure.ac without enabling AUTORECONF, hence autoreconf is triggered
internally and breaks.
For squid it seems related to the bundled libltdl (libtool). I've
already tried to unbundle it without much success, seems to be pretty
tied up.
I've sent a patch to fix guile.
Regards.
next prev parent reply other threads:[~2015-01-08 17:34 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 [this message]
2015-01-10 21:30 ` Bernd Kuhls
2015-01-12 19:58 ` Thomas Petazzoni
2015-01-12 20:05 ` Gustavo Zacarias
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=54AEBFAE.2020706@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox