Re: autoreconf vs autogen.sh

2007-08-27 Thread Roman Rybalko
when I have to include some m4s in m4 dir how I can specify -I m4 option to aclocal through autoreconf ? >> I've inherited an autotools-using project and am trying to learn more >> about >> autoconf and automake. The project has used the following brief >> autogen.sh: >> >> aclocal && autoheader &

Re: autoreconf vs autogen.sh

2007-08-27 Thread Roman Rybalko
> aclocal will use the value of ACLOCAL_AMFLAGS in your top-level > Makefile.am, so you can do something like: > ACLOCAL_AMFLAGS = -I build-aux Is it really works ? I tried this somewhen, but it wasn't working. Anybody, tell me plz the docs about this. I've red some docs, but don't found any info

AC_TRY_LINK with static libraries (*.a)

2007-08-27 Thread Roman Rybalko
When I try to compile some prog with some lib, generally it's unknown whether it is static or dynamic library. Compile with dynamic libraries hasn't problems, but with static - it is. e.g. AC_TRY_LINK( [ #include ], [ mysql_shutdown(0, 0); ], AC_DEFINE(HAVE_MYSQL_SHUTDOWN_LEVEL_ARG, 1,

Re: autoreconf vs autogen.sh

2007-08-27 Thread Roman Rybalko
Ralf Wildenhues wrote: > If there is something you tried and it did not work as expected, then > please show what you did so we can try to reproduce it. > > Here it is: I invoked aclocal and expect it will respect ACLOCAL_AMFLAGS in Makefile.am - but it doesn't. So, as I can see, ACLOCAL_AMFLAG

Re: AC_PATH_PROG or m4 bug

2007-08-28 Thread Roman Rybalko
> M4 1.4.4 and earlier have known bugs that interfere with correct autoconf > operation. We recommend upgrading to M4 1.4.5 or later (M4 is currently > at 1.4.10). While you are at it, you may also want to look at upgrading > to autoconf 2.61, although for this issue, the out-of-date m4 is most