RE: [Flightgear-devel] Change in Canonical Build Proceedure ???
Norman Vine writes: Erik Hofman writes: Norman Vine wrote: I have been fighting this one for 'awhile' with no success therefore my reccomendation for AC_PREREQ(2.13) It is probably a shell syntax mistake or somesuch :-( although this could be a cascade from autoconf failing with configure.in: 145: error: possibly undefined macro: AC_EXT_DAYLIGHT configure.in: 151: error AC_EXT_TIMEZONE Isn't this the problem where you have to to run: aclocal -I . Ah Ah - Thank you !! This solves the AC_PREREQ() 'hack' which should no longer be necessary The canonical set of configure commands are then aclocal -I . Of course running aclocal -I . breaks 'everything' if you are using autoconf-2.13 or earlier ... Perhaps the autogen script could detect the autoconf version and run with the appropriate options??? autoheader automake -a autoconf ./configure --with-LOCAL_OPTIONS Attached find a simple script to set the LOCAL_OPTIONS and write a bootstrap script. translations to alternative languages are expected :-) copy the script to your top FGFS source directory and enter % ./configurator.py then run the script it creates to configure your source tree Gotta love Open Source development and its MANY eyes :-) Cheers Norman -- Curtis Olson Intelligent Vehicles Lab FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Change in Canonical Build Proceedure ???
Norman Vine wrote: I have been fighting this one for 'awhile' with no success therefore my reccomendation for AC_PREREQ(2.13) It is probably a shell syntax mistake or somesuch :-( although this could be a cascade from autoconf failing with configure.in: 145: error: possibly undefined macro: AC_EXT_DAYLIGHT configure.in: 151: error AC_EXT_TIMEZONE Isn't this the problem where you have to to run: aclocal -I . Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Change in Canonical Build Proceedure ???
Erik Hofman writes: Norman Vine wrote: I have been fighting this one for 'awhile' with no success therefore my reccomendation for AC_PREREQ(2.13) It is probably a shell syntax mistake or somesuch :-( although this could be a cascade from autoconf failing with configure.in: 145: error: possibly undefined macro: AC_EXT_DAYLIGHT configure.in: 151: error AC_EXT_TIMEZONE Isn't this the problem where you have to to run: aclocal -I . Ah Ah - Thank you !! This solves the AC_PREREQ() 'hack' which should no longer be necessary The canonical set of configure commands are then aclocal -I . autoheader automake -a autoconf ./configure --with-LOCAL_OPTIONS Attached find a simple script to set the LOCAL_OPTIONS and write a bootstrap script. translations to alternative languages are expected :-) copy the script to your top FGFS source directory and enter % ./configurator.py then run the script it creates to configure your source tree Gotta love Open Source development and its MANY eyes :-) Cheers Norman configurator.py.gz Description: GNU Zip compressed data
Re: [Flightgear-devel] Change in Canonical Build Proceedure ???
Norman Vine wrote: It appears as if recent changes in the CVS requires a modification in the steps for building FGFS 1) for now, with Cygwin at least, you NEED to add AC_PREREQ(2.13) as the first REAL LINE in configure.in I am investigating this as it shouldn't be necessary 2) Everyone NEEDS to run autoheader as src/include/config.h.in is no longer in the CVS files Therefore the canonical sequence for building FGFS from a fresh CVS checkout is now % rm config.cache % aclocal % autoheader % automake -a % autoconf % ./configure --YOUR_CONFIGURE_OPTIONS % make I think its time to add an autogen.sh script to bootstrap the build process. Bernie ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Change in Canonical Build Proceedure ???
Curtis L. Olson writes: Norman Vine writes: It appears as if recent changes in the CVS requires a modification in the steps for building FGFS 1) for now, with Cygwin at least, you NEED to add AC_PREREQ(2.13) as the first REAL LINE in configure.in I am investigating this as it shouldn't be necessary Strange, what happens / what kind of error messages do you see when this is missing? The auto-tools do seem to suffer from mutually incompatible config file formats between versions which has been a problem for us ... :-( fails with checking for windows.h... yes /src/FlightGear/configure: 3187: Sybtax error: word unexpected (expecting( )) I have been fighting this one for 'awhile' with no success therefore my reccomendation for AC_PREREQ(2.13) It is probably a shell syntax mistake or somesuch :-( although this could be a cascade from autoconf failing with configure.in: 145: error: possibly undefined macro: AC_EXT_DAYLIGHT configure.in: 151: error AC_EXT_TIMEZONE I have committed autogen.sh scripts and updated the README.autoconf. Thanks :-) Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
