[SOLVED] configure: error: cannot guess build type; you must specify one

[hlfmanhlfamzng]

The new beta 11 of WZ2100 was released recently.

http://developer.wz2100.net/wiki/Dow...WarzoneonLinux

http://developer.wz2100.net/wiki/CompileGuideLinux

I don't think this is a bug with their software. I think I'm missing something. There's a bug in their system for building with automake 1.12 being broken, so it's verified to work with 1.11 http://developer.wz2100.net/ticket/3538

Anybody know what I need? I'm running Fedora 17, all latest updates installed.

[root@localhost warzone2100-3.1_beta11]# ./autogen.sh
+ checking for autoconf >= 2.56 ... found 2.68, ok.
+ checking for automake >= 1.10 ... found 1.11.3, ok.
+ running aclocal ...
+ running autoheader ...
+ running autoconf ...
+ running automake ...
+ removing config.cache ...

Now type './configure && make' to compile.

[root@localhost warzone2100-3.1_beta11]# ./configure && make
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking how to create a ustar tar archive... gnutar
checking build system type... ./config.guess: unable to guess system type

This script, last modified 2009-06-10, has failed to recognize
the operating system you are using. It is advised that you
download the most up to date version of the config scripts from

http://git.savannah.gnu.org/gitweb/?....guess;hb=HEAD
and
http://git.savannah.gnu.org/gitweb/?...ig.sub;hb=HEAD

If the version you run (./config.guess) is already up to date, please
send the following data and any information you think might be
pertinent to <config-patches@gnu.org> in order to provide the needed
information to handle your system.

config.guess timestamp = 2009-06-10

uname -m = i686
uname -r = 3.3.7-1.fc17.i686
uname -s = Linux
uname -v = #1 SMP Mon May 21 22:50:24 UTC 2012

/usr/bin/uname -p = i686
/bin/uname -X =

hostinfo =
/bin/universe =
/usr/bin/arch -k =
/bin/arch = i686
/usr/bin/oslevel =
/usr/convex/getsysinfo =

UNAME_MACHINE = i686
UNAME_RELEASE = 3.3.7-1.fc17.i686
UNAME_SYSTEM = Linux
UNAME_VERSION = #1 SMP Mon May 21 22:50:24 UTC 2012
configure: error: cannot guess build type; you must specify one

So I tried:

[root@localhost warzone2100-3.1_beta11]# ./configure --host=i686-pc-linux
configure: WARNING: if you wanted to set the --build type, don't use --host.
If a cross compiler is detected then cross compile mode will be used
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for i686-pc-linux-strip... no
checking for strip... no
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking how to create a ustar tar archive... gnutar
checking build system type... ./config.guess: unable to guess system type

This script, last modified 2009-06-10, has failed to recognize
the operating system you are using. It is advised that you
download the most up to date version of the config scripts from

http://git.savannah.gnu.org/gitweb/?....guess;hb=HEAD
and
http://git.savannah.gnu.org/gitweb/?...ig.sub;hb=HEAD

If the version you run (./config.guess) is already up to date, please
send the following data and any information you think might be
pertinent to <config-patches@gnu.org> in order to provide the needed
information to handle your system.

config.guess timestamp = 2009-06-10

uname -m = i686
uname -r = 3.3.7-1.fc17.i686
uname -s = Linux
uname -v = #1 SMP Mon May 21 22:50:24 UTC 2012

/usr/bin/uname -p = i686
/bin/uname -X =

hostinfo =
/bin/universe =
/usr/bin/arch -k =
/bin/arch = i686
/usr/bin/oslevel =
/usr/convex/getsysinfo =

UNAME_MACHINE = i686
UNAME_RELEASE = 3.3.7-1.fc17.i686
UNAME_SYSTEM = Linux
UNAME_VERSION = #1 SMP Mon May 21 22:50:24 UTC 2012
configure: error: cannot guess build type; you must specify one

I don't know what it wants. I know that the old 2.3.9 is in the repositories, but just for testing purposes I downloaded the source for 2.3.9, and it doesn't compile either. Same error message.

[george_toolan]

You know how to read?

config.guess timestamp = 2009-06-10

This script is from 2009. So why don't you download these two files which are dated 2012-06-17 (or newer)

http://git.savannah.gnu.org/gitweb/?....guess;hb=HEAD and http://git.savannah.gnu.org/gitweb/?...ig.sub;hb=HEAD

Try to right click on the links and select "Save Link As..." or use wget.

configure: error: cannot guess build type; you must specify one
[root@localhost warzone2100-3.1_beta11]# ./configure --host=i686-pc-linux
configure: WARNING: if you wanted to set the --build type, don't use --host.

It says not to use --host ;-)

[jpollard]

You also have the option to look at the configure script (and a bit of tracing) look at what it is testing for.

Sometimes, the test has a bug in it - In the current case, it may be expecting something like a 2.6.x.y-patch version number, where the current is 3.4.2-patch number which will fail the match format.

[PabloTwo]

If you have the redhat-rpm-config package installed (also possibly the rpmdevtools package), you can find your "build system type" easily. In my case, on F16.x86_64:

BASH:~/-> rpm --eval %{_host}
x86_64-unknown-linux-gnu

Then,

./configure --build=x86_64-unknown-linux-gnu

[hlfmanhlfamzng]

Originally Posted by george_toolan

You know how to read?

Now that wasn't necessary. I missed that part.

Originally Posted by george_toolan

This script is from 2009. So why don't you download these two files which are dated 2012-06-17 (or newer)

It's odd that F17 would ship with such an old script in it when newer ones are available. I got it to work though, without messing with the scripts.

Originally Posted by george_toolan

It says not to use --host ;-)

That did the trick. Wish I would've seen it earlier. For the benefit of others:

./configure --build=i686-pc-linux

(I was asked for other development headers, but they were all in the repositories)

Then

./make

Then to launch the game:

./src/warzone2100

Because this is a beta build, it's been purposely designed to stay within this folder, without being installed, at least that's what it seems like to me based on what it says on the warzone site for 3.1.