Re: optional features and AC_ARG_WITH

Hello, On Thu, Feb 17, 2005 at 11:28:08AM +0100, Gregorio Guidi wrote: > > actually, I believe that both my proposals will get actually implemented. > > But the AS_IF solution is already checked in to the autoconf CVS. > > If there will be another solution, I would prefer to avoid AS_IF. we cann

Re: how to set a default program-prefix whithin configure.ac

Hi, On Thu, Feb 17, 2005 at 06:18:14PM +0100, JRBCAST wrote: > My question is: How can I set a default progra-prefix [...] > ./configure --program-prefix=foopref_ case $program_prefix in NONE) program_prefix=my_default_ ;; esac should do the trick. Put it somewhere between AC_INIT and AC_OUTPUT

Re: AC_REQUIRE problems

On Fri, 18 Feb 2005, Stepan Kasal wrote: > when I was thinking about the issue, I imagined several #include's in one > file, > to detect the presence of headers. > We both come to the same conclusion: we can speed up the common case when all > headers are present, but we cannot get several ind

Re: dispatching

"awkward fit" because you are using Autoconf in an awkward way. Using a tool an an un-intened way. Like sweeping a walkway with a beach towel when you have a broom nearby - it would work buy it would be a bit awkward. You would be making to much work for yourself and the result would not be as rob

Re: multiline output variables.

On Wed, 9 Feb 2005, Dan Manthey wrote: > Okay, hopefully this is the last version of this patch, finally. Sadly, no, it wasn't. I've finally gotten to try this patch on a different machine, and I encountered two problems, now fixed. On my Solaris 10 machine, I found that `expr + 1` gives a syn

Re: dispatching

Hi, > "awkward fit" because you are using Autoconf in an awkward way. Using > a tool an an un-intened way. It's really not that "unintended" IMHO. After all, Autoconf is all about generating a Makefile from a template (Automake-generated or handwritten) adjusted with some configuration options (p

Re: dispatching

Hi, > | Somewhere early during ./configure, the host type is checked. If it > is | GNU (Hurd), an ordinary build is prepared. (Checking libs, using > | automake-generated makefile etc.) However, if it's Linux, the > behaviour | changes completely: All the ordinary checks are skipped; > instead of

[Patch] add AC_EGREP_RAW macro to acgeneral.m4

hey all- Pach to add AC_EGREP_RAW to acgeneral.m4. While working on an autoconf script I found that AC_EGREP_HEADER doesn't allow you to grep for #define-ed values, since AC_EGREP_HEADER passes input through cpp. The macro allows a standard, no preprocessing EGREP on a file. -- /**

bug report ???

Hi, I got the following message running a configure script on my Powerbook G4 under Mac OS X v10.3 - don't know if this is relevant, but ... Cheers, Martin checking resolv.h presence... yes configure: WARNING: resolv.h: present but cannot be compiled configure: WARNING: resolv.h: check for missin

(no subject)

During configuring amule tar -zxvf aMule-cvs-20050218.tar.bz2 cd amule-cvs/ ./configure --prefix=~/amule-cvs/ --with-wx-config=/usr/X11R6/bin/wx-config --with-wxbase-config=/usr/X11R6/bin/wx-config --disable-debug --with-curl-config=/usr/local/bin/curl-config --enable-optimize --x-libraries