Ok, you guys lost me about 5 posts back, but since I
started this I figured I better report back...
> Norman Vine wrote:
> > 
> [snip]
>cd $FG_SRC
>rm config.cache
>rm -f *.lnk   #  remove symlinked auto* files
>ls -la *.lnk   # just to make sure they got removed
># you might have to remove them one at a time
># then try the standard
>aclocal
>automake -a
>autoconf
>./configure

Tried this, didnt help - it was a virgin FGFS-0.7.8
install and didnt seem to have any *.lnk files

>>Maybe Im back to looking at mounting binary volumes
>>to be able to use the older automake 
>>and autoconf versions?

>Well I would reccomend doing this anyway esp. if you

Turns out I already DID have a unix (as opposed to
DOS) filesystem on the Cygwin install (I didnt
understand that this was what was meant by a binary
volume?) but,

I bit the bullet, and did a clean re-install of the
latest Cygwin, and also the latest FGFS-0.7.8, and
then added (using vim) the AC_PREREQ( 2.13 ) as the
first line in configure.in, did 
rm config.cache
aclocal
automake -a
autoconf
./configure

And then.. it worked fine. 0 errors.

If I was to guess, I think I probably had some DOS
formatted files in the Cygwin installation.
I normally use a W2k text editor that asks before it
will convert unix text files to DOS, but its quite
possible I slipped up at some point when opening a
file to try and figure out what was going on after the
intial problems with the "INCLUDES +=" errors.

I didnt realize (but I now assume) that the Cygwin
configure/make process would be sensitive to
the text file format?

Thank you very much for the help; now at least I can
start fighting bugs that are (more directly) of my own
creation.
 
 - Derek Lisoski

__________________________________________________
Do You Yahoo!?
Send your FREE holiday greetings online!
http://greetings.yahoo.com

_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel

Reply via email to