search path for AC_CHECK_HEADERS?

How can I specify a search path to try and find a 3rd party header in? I'm trying to add a --enable-dmalloc option to a program which will cause configure to search for dmalloc.h and link with -ldmalloc for debugging. I'll need a similar thing to look for libs for -ldmalloc and also for a --enab

make flavor checks?

Anyone have any good macros for checking characteristics of make? Ie, I'd like to see something like: checking for gmake... no checking for make... yes checking if make is GNU make... no checking if make accepts [foo]... etc. I'm wanting to use autoconf to produce a set of make file fragments

correctly using -R for X tests?

I'm having some troubles with checking for some X libraries using autoconf-2.52. The piece of the configure.ac file in question is: AC_PATH_XTRA # # uncommenting this makes it `work' on my system # but of course its not portable # X_LIBS="$X_LIBS -R/usr/X11R6/lib" # AC_CHECK_LIB(X11, XOpenD

configure.lineno leftover?

I'm ending up with a file called '=build/configure.lineno' after 'make distcheck' which of course causes the distcheck to fail. This is autoconf-2.53 and automake-1.6.2. Any suggestions? Thanks -Dan

"correct" way of handling several default settings

Whats the desired or recommended way to handle setting a bunch of variables which will turn into defines in a makefile as well as strings in some documentation and some X11 application default settings? I was thinking of putting stuff like this in configure.ac: FOO=${FOO:-some_default} AC_SUBS

--with-foo= vs. FOO=${FOO:-foo_default}

I'm working on autobuilding a program which currently uses imake. One thing I'm working on changing now is that there is a big .h file that has many defines for defaults like: #define EMERGENCY_NAME "/tmp/FOO.%i.save" /* %i --> pid */ #define BACKUP_NAME "/tmp/FOO.%i.

Re: --with-foo= vs. FOO=${FOO:-foo_default}

On Mon, 2 Sep 2002, Harlan Stenn wrote: > I could be mistaken but I think some of us are talking about "how do we > specify the default for X", and not "do we specify X at compile time or at > runtime". In my case I'm talking about how do I set some defaults at compile time. They can (i thin

how to AC_DEFINE* a fully evaluated variable?

I tried something like this in my configure.ac file: MYDIR=${datadir}/foo AC_DEFINE_UNQUOTED(MYDIR,"$MYDIR",[default search directory for foo]) but this ends up with: /* default search directory for foo */ #define MYDIR "${prefix}/share/foo" in config.h but what I really wanted is the fully e

app-defaults directory?

whats the correct way to specify an X11 app-default file in an automake file? Ie, I have something like: bin_PROGRAMS=foo foo_SOURCES= foo.c util.c util.h somedirectoryforappdefaults_DATA= Foo and I need to know what to put for "somedirectoryforappdefaults". Thanks -Dan

how to get -R path set for X11?

whats the correct way to have autoconf add the -Wl.-R/usr/X11R6/lib stuff thats needed? I've tried AC_PATH_XTRA which gives me the -I/usr/X11R6/include for compiling and -L/usr/X11R6/lib for linking, but I don't get the -Wl,-R/usr/X11R6/lib part which I need so that the program can find the X lib

ncurses/curses detection

Anyone know of a decent autoconf macro for detecting the right header and library for curses/ncurses? Here is the issue I have seen. Many systems ship curses.h and libcurses. Sometimes this may actually be ncurses, sometimes not. Then I sometimes on those same systems I see ncurses.h and li

dynamic strings in help text

I have a configure.ac file which has some shell commands to set a variable which I want to later use in a help string. The shell commands basically just enumerate modules contained in the source directory. # some shell commands which give a value for the # hid_guis variables AC_MSG_CHECKING(

error out with no yacc?

Right now AC_PROG_YACC seems to happily set YACC=yacc if it can't actually find a yacc program (bison -y or byacc). Is there a way to error out if there really is no yacc available? Thanks -Dan ___ Autoconf mailing list Autoconf@gnu.org http://l

correct check for -rdynamic

Anyone have a correct check to see if the compiler needs/accepts -rdynamic or maybe -Wl,--export-dynamic? We were using a test like: AC_MSG_CHECKING([If the compiler accepts -rdynamic]) old_LDFLAGS="$LDFLAGS" LDFLAGS="$LDFLAGS -rdynamic" AC_LINK_IFELSE([int main(){}], [AC_MSG_RESULT([y

Re: just one of a million reasons why autoconf is a worthless piece of shit (2)

Paul Smith wrote: Since your last post seemed to be a bit more willing to engage in a dialog, I'll send this then I'm done. Some of these points have been made already but maybe some concrete examples will help. I've heard various complaints about autoconf and automake over the years and he