Ah, that's good. Thanks. It works. I have now found a proper description of the situation in this announcement of the combined (new and old) version: http://sources.redhat.com/ml/cygwin/2001-12/msg00100.html
So there are two ways to fix our problem: 1. Fix the "'=' before '+='" to make our files compatible with both old and new versions. This seems like a good idea anyway if it can be done in a sensible way (and I don't know if it can). 2. Add "AC_PREREQ(2.13)" at the top of SimGear/configure.in and FlightGear/configure.in. This should cause the very new wrapper scripts to use the old versions of the autotools. But will this work on older versions like 2.10? If we put "AC_PREREQ(1.0)" would that work on V2.13 and some lower versions as well? - Julian Norman Vine wrote: > > Julian Foad writes: > > > >Does anyone know how to sort out the Makefile.am syntax so it > >is compatible with current versions of automake? Or is it a > >CygWin-specific problem? For the last six months or more I > >have been able to keep using an old version which works > >(autoconf 2.52-1 and automake 1.4-4), but I lose it when I > >update my CygWin installation. (Must talk to CygWin about > >that.) The new version (autoconf 2.52-5 and automake 1.5a-1) > >is supposed to heuristically decide whether to use an old or > >new version, but it doesn't seem to work for me. > > Until we update our configure scripts to be 2.52 compatable > add this line to the top of configure.in > and then run > % rm config.cache; aclocal; automake -a; autodonf; ./configure > > < actually anything less then 2.13 will work too > > > AC_PREREQ(2.13) > > FWIW > This should probably work for systems that use autoconf > _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
