Re: documentation through doxygen stopped working

Hi Ralf, thanks for replying. I don't understand much the m4 code. I can say that it stopped working after upgrading autotools. Part of the macro (the one that fails) is: AC_DEFUN([DX_REQUIRE_PROG], [ AC_PATH_TOOL([$1], [$2]) if test "$DX_FLAG_[]DX_CURRENT_FEATURE$$1" = 1; then AC_MSG_WARN([$

Re: using atlocal variables in autotest macros

* John Wohlbier wrote on Mon, Mar 02, 2009 at 04:51:27AM CET: > m4_define([AT_MPIRUN_PROGRAM], > [echo "$MPI_LIBS" > AS_IF([test -n "$MPI_LIBS"], >[AT_BANNER([executing mpirun -n $2 $1]) > AT_TESTED([$1]) > AT_SETUP([$1]) > AT_CHECK([mpirun -n $2 $1],[0],[ignore],[i

Re: documentation through doxygen stopped working

* aaragon wrote on Tue, Mar 03, 2009 at 06:54:35AM CET: > > aara...@~/Workspace/080427 cpputils$./autogen.sh > configure.ac:58: error: AC_SUBST: `DX_FLAG_[]DX_CURRENT_FEATURE' is not a > valid shell variable name > acinclude.m4:77: DX_REQUIRE_PROG is expanded from... > acinclude.m4:117: DX_ARG_AB

Re: make distcheck

* Patrick Welche wrote on Tue, Mar 03, 2009 at 12:04:00AM CET: > On Mon, Mar 02, 2009 at 09:57:28PM +0100, Ralf Wildenhues wrote: > > Not sure if "srcdir" is a directory name here, but config.h should not > > be created in the source tree, but in the build tree, to facilitate > > having several dis

documentation through doxygen stopped working

Hello everyone, I was wondering if someone face the same issue. I used to work with the ax_prog_doxygen macro but now it stopped working and I have no clue what's going on. The error is as follows. aara...@~/Workspace/080427 cpputils$./autogen.sh configure.ac:58: error: AC_SUBST: `DX_FLAG_[]DX

Re: overwriting default make rules

satyakam>Is it the right thing to do if i overwrite this rule as follows: > $(PROGRAM): $(OBJECTS) $(LIBS) > $(LD) $(LD_FLAGS) $(OBJECTS) $(LIBS) -o $static_link_file > # some more intermediate steps here... > $(POSLINK) $(PL_FLAGS) $static_link_file -o $@ In those situations (ie: Em

Re: make distcheck

On Mon, Mar 02, 2009 at 09:57:28PM +0100, Ralf Wildenhues wrote: > * Patrick Welche wrote on Mon, Mar 02, 2009 at 08:52:26PM CET: > > > > I thought that running make distcheck in the source directory should > > fail? > > Not sure why you think that. distcheck does a build with build tree != > so

Re: make distcheck

On Mon, Mar 02, 2009 at 03:11:34PM -0500, Peter Johansson wrote: > Patrick Welche wrote: >> The project was broken due to liberal use of #include "../../config.h". >> configure will pop config.h in the builddir, so the source file will >> never see ../../config.h. >> >> > It is often a good idea

Re: make distcheck

* Patrick Welche wrote on Mon, Mar 02, 2009 at 08:52:26PM CET: > > I thought that running make distcheck in the source directory should > fail? Not sure why you think that. distcheck does a build with build tree != source tree. But nothing in Automake prohibits packages from allowing both trees

Re: make distcheck

Patrick Welche wrote: The project was broken due to liberal use of #include "../../config.h". configure will pop config.h in the builddir, so the source file will never see ../../config.h. It is often a good idea to #include see http://www.gnu.org/software/autoconf/manual/autoconf.html#Co

Re: make distcheck

On Mon, Mar 02, 2009 at 08:01:59PM +0100, Ralf Wildenhues wrote: > > In a project, using autoconf 2.61, automake 1.10.1, libtool 1.5.26, > > make distcheck succeeds. If I untar the created .tar.bz2 file, and > > /path/to/untar/configure && make, I get errors - somehow the manual > > "check build fr

Re: make distcheck

Hi Patrick, * Patrick Welche wrote on Mon, Mar 02, 2009 at 01:10:44PM CET: > Just a quick "Am I doing something silly?" N! > In a project, using autoconf 2.61, automake 1.10.1, libtool 1.5.26, > make distcheck succeeds. If I untar the created .tar.bz2 file, and > /path/to/untar/configure && make

Re: overwriting default make rules

Hello, Please ignore my previous mail. It wasn't complete and i am sorry for the inconvenience.   I am trying to use autoconf to build for Symbian platform that involves more than 1 step at the linking stage, i.e., it has a static linking stage, followed by a post-linking stage. While the defaul

overwriting default make rules

Hello, I am trying to use autoconf to build for Symbian platform that involves more than 1 step at the linking stage, i.e., it has a static linking stage, followed by a post-linking stage. While the default make rule to produce an executable is just a linking stage e.g., the default rule may loo

overwriting default make rules

Hello, I am trying to use autoconf to build for Symbian platform that involves more than 1 step at the linking stage, i.e., it has a static linking stage, followed by a post-linking stage. While the default make rule to produce an executable is just a linking stage e.g., the default rule may loo

Re: bug when installing with fink in Os/X

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to KURT PETERS on 3/1/2009 7:12 AM: Hello Kurt, [your mailer has a nasty habit of mangling newlines, making your report harder to read] > The software asked me to report this bug:configure: WARNING: > X11/Xmu/Editres.h: present but cannot

Re: [GNU Autoconf 2.63] testsuite: 51 failed

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Ralf Wildenhues on 2/28/2009 10:46 AM: > Guys, this is > > right? Indeed it is! Thanks for digging up the prior reference. Still to be determined, then, is why

make distcheck

Just a quick "Am I doing something silly?" In a project, using autoconf 2.61, automake 1.10.1, libtool 1.5.26, make distcheck succeeds. If I untar the created .tar.bz2 file, and /path/to/untar/configure && make, I get errors - somehow the manual "check build from buildir != srcdir" fails, but I th