Hi Paul,
Thanks for the review.
* Paul Eggert wrote on Fri, May 20, 2005 at 09:18:46PM CEST:
Ralf Wildenhues [EMAIL PROTECTED] writes:
+eval `./config.status --config`
+./config.status --recheck ./config.status
This doesn't look right to me. Shouldn't the argument to eval be
quoted?
Hi Ed,
* E. Rosten wrote on Mon, May 23, 2005 at 06:59:05PM CEST:
Based on my recent experience of learning to write autoconf for a new
library, I have written a brief autoconf tutorial which should be able to
get people in to a state where they can start hacking. Everything is
Hi,
On Tue, May 24, 2005 at 06:22:45PM +0200, Alexandre Duret-Lutz wrote:
Stepan OK. Alexandre, I'm new to this, could you please
Stepan suggest a name for the macro?
I'm not good at naming things. AC_SUBST_TRACE (like
AC_DEFINE_TRACE) or AC_OUTPUT_VARIABLE ?
OK, it'll be
Hi Ed,
Please keep the mailing list copied, this is interesting for others as
well. Thank you.
* E. Rosten wrote on Wed, May 25, 2005 at 10:53:13AM CEST:
On Wed, 25 May 2005, Ralf Wildenhues wrote:
* E. Rosten wrote on Mon, May 23, 2005 at 06:59:05PM CEST:
| M4 arguments are quoted with [
Hi Ed,
* Ed Hartnett wrote on Fri, May 20, 2005 at 04:51:41PM CEST:
I read somewhere in my autoconf researches on the web that tests
should not be run conditionally, based on earlier tests - they should
always run. In other words, don't try and optimize configure.ac.
Is this really good
Hi,
I'm currently developping a C++ software on FreeBSD. Since that software uses
stdlib.h's srandomdev() function, I added :
AC_CHECK_FUNCS([srandomdev])
in my configure.in file to detect it. The problem is that on other oses such
as Debian, there is no srandomdev() function in stdlib.h so
Hello, Ed!
There are many things that are considered bad practice. There are
many things that are old deprecated ways to do things.
For example, using the file name configure.in is outdated. You should
use configure.ac.
I guess (I don't really know) that the reason for this is that in is
On Thu, 2005-05-26 at 09:59 +0900, Andre Caldas wrote:
Hello, Ed!
There are many things that are considered bad practice. There are
many things that are old deprecated ways to do things.
For example, using the file name configure.in is outdated. You should
use configure.ac.
Ouch! That's a pretty major breakage; we should fix it right away.
I installed the patch enclosed at the end of this message; does
it fix things for you?
Stepan Kasal [EMAIL PROTECTED] writes:
awk '/^ \t*case/,/^ \t*esac/{if(/\[\^.*\)/) exit(1)}'
That code looks incorrect. \t* should be [
