[RESEND - apologies if you see this twice... no echo from the list after 10
hours or so]
On 1 Aug 2010, at 04:31, Bob Friesenhahn wrote:
On Sat, 31 Jul 2010, Ralf Wildenhues wrote:
I'd rather avoid (3), and I know (2) is going to be quite some work, but
should be done. What things go wrong
On Sat, 2010-07-31 at 17:23 +0200, Ralf Wildenhues wrote:
1) Autoconf should have macros for delayed error reporting.
Example: wget foo-1.tar.gz, run configure, find out it needs bar.
Install bar, only to find out foo also needs baz, etc.
So, we should have something that allows an error
On 1 Aug 2010, at 04:31, Bob Friesenhahn wrote:
On Sat, 31 Jul 2010, Ralf Wildenhues wrote:
I'd rather avoid (3), and I know (2) is going to be quite some work, but
should be done. What things go wrong with pkg-config? (Please adjust
the Subject: when replying to this, thanks!)
The main
On Thu, 2010-07-08 at 21:48 -0700, Sam Silla wrote:
Hello,
I would like to create an array of values to use in configure.ac and am
unsure what the best way to accomplish this is. I was wondering if Autoconf
comes with native support for constructing and iterating through arrays.
Thanks,
Hello Dave,
Thanks for your feedback!
On Fri, 30 Jul 2010 20:03:28 +
Dave Hart daveh...@gmail.com wrote:
Neither, I'm afraid. On their own, both work correctly, including
with a configuration cache file. The error is in sharing the
configuration cache across independently-maintained
Hello Thomas,
* Thomas Petazzoni wrote on Mon, Aug 02, 2010 at 03:33:53AM CEST:
So the ability of sharing the cache between execution of
different configure scripts is a documented feature. Is it just that in
reality it doesn't work that well ?
You should be able to modify both configure
Hi Rainer,
* Rainer Tammer wrote on Sun, Aug 01, 2010 at 05:09:01PM CEST:
this are the failures of autoconf 2.67 make check on AIX V7BETA:
213: AC_CACHE_CHECK FAILED (base.at:478)
240: Signal handling FAILED (torture.at:1263)
I have included the testsuite.log for a
Autoconf 2.66 added '+' to the set of allowed characters in --enable-*
Why?
So, my question is: could standards.texi document the set of allowed
characters?
Can you make a proposal?
Current Autoconf has -+. mapped to _ and otherwise wants characters
eligible for shell
* Karl Berry wrote on Mon, Aug 02, 2010 at 12:00:21AM CEST:
Autoconf 2.66 added '+' to the set of allowed characters in --enable-*
Why?
So gnulib could have --enable-c++.
So, my question is: could standards.texi document the set of allowed
characters?
Can you make a
