I downloaded the install script for Linux and then I got the vegastrike directory (the one with the ./configure script in it) from http://vegastrike.sourceforge.net/forum ... php?t=2922 (Scroll down a bit and you'll find a link to a tgz file) because the install script didn't doewnload that one right. I tried several times and it gives me an error.
EDIT: I started over (decompressing the tarball and compiling again) and now the configure says at the end: ".infig.status: error: cannot find input file: Makefile" It didn't say it previously.
So it's the case of the mysterious makefile!
By the way I changed the symlinks for config.guess config.sub depcomp and install-sh to fit my system; they point to my automake installation (/usr/share/automake-1.8/config.guess for instance)
Here's my config.log:
$ ./config.status Makefile
on localhost
config.status:429: error: invalid argument: Makefile
## ---------------------- ##
## Running config.status. ##
## ---------------------- ##
This file was extended by vegastrike config.status 0.4.0, which was
generated by GNU Autoconf 2.59. Invocation command line was
CONFIG_FILES =
CONFIG_HEADERS =
CONFIG_LINKS =
CONFIG_COMMANDS =
$ ./config.status Makefile
on localhost
config.status:429: error: invalid argument: Makefile[/url]
Compile Problem 0.4.2 for Linux
-
- Mercenary
- Posts: 118
- Joined: Sun Sep 12, 2004 10:47 am
- Location: Crucible/Enyo System
-
- Lead Network Developer
- Posts: 2560
- Joined: Sun Jan 12, 2003 9:13 am
- Location: Palo Alto CA
- Contact:
What's on the console is probably instead:
"config.status: error: cannot find input file: Makefile^M.in"
(the ^M character makes it overwrite what's at the beginning of the line)
The question is about where the mysterious ^M came from in one of the files.
They usually come from a file checked out from windows and then used on linux.
Last time I tried, the cvs worked fine for me, so I would try that again (It's been at 12-24 hours since it was tagged so the changes should work on the anonymous pserver).
Otherwise, maybe you could edit the config.status or configure.in and look for a ^M character somewhere.
"config.status: error: cannot find input file: Makefile^M.in"
(the ^M character makes it overwrite what's at the beginning of the line)
The question is about where the mysterious ^M came from in one of the files.
They usually come from a file checked out from windows and then used on linux.
Last time I tried, the cvs worked fine for me, so I would try that again (It's been at 12-24 hours since it was tagged so the changes should work on the anonymous pserver).
Otherwise, maybe you could edit the config.status or configure.in and look for a ^M character somewhere.