[Nexus-developers] NeXus autotools
Jens.Krueger at frm2.tum.de
Fri Feb 20 15:50:57 GMT 2004
Am Freitag, 20. Februar 2004 16:12 schrieb Ray Osborn:
> On 2/20/04 7:05, "Akeroyd, FA (Freddie)" <F.A.Akeroyd at rl.ac.uk> wrote:
> > Jens has submitted back his modifications and all seems to work well as
> > far as I can tell.
> > I have tagged the previous non-autotools release
> > NEXUS_PRE_AUTOTOOLS_20040120
> > and will now delete the automatically generated files (*.in etc) from the
> > CVS repository to avoid
> > any confusion
please try the autogen.sh script if you have checked out the current sources from
the CVS and then try it again to run configure [options].
> I assume that I now have to type autoconf to generate the configure script.
> When I do that, I get
> configure.ac:37: error: possibly undefined macro: AM_INIT_AUTOMAKE
> If this token and others are legitimate, please use m4_pattern_allow.
> See the Autoconf documentation.
> configure.ac:39: error: possibly undefined macro: AM_CONFIG_HEADER
> configure.ac:42: error: possibly undefined macro: AC_PROG_LIBTOOL
> configure.ac:68: error: possibly undefined macro: AC_CHECK_C_OPTION
> configure.ac:163: error: possibly undefined macro: AM_CONDITIONAL
> This is running the default Mac OS X autoconf in /usr/bin and I seem to be
> running the following versions (I can't get the libtool command to give me
> a version number):
> autoconf (GNU Autoconf) 2.57
> automake (GNU automake) 1.6.3
> "autoconf" does generate a configure script, but it fails with
> $ ./configure --with-hdf4=/sw --with-hdf5=/sw
> ../configure: line 1305: syntax error near unexpected token `1.6'
> ../configure: line 1305: `AM_INIT_AUTOMAKE(1.6)'
If it does not work you may install the autotools from sources:
The should also work under Mac OS X (Darwin, Fink, ...)
> Do I need a later version of autoconf, because it might be a problem? A
> later version is not available under Fink.
Technische Universität München
Tel: + 49 89 289 14 716
Fax: + 49 89 289 14 666
mailto:jens.krueger at frm2.tum.de
More information about the NeXus-developers