Can someone please check this and tell me if it's ok?

Do you need help? Ask here!

Bug reporting belongs here: http://developer.wz2100.net/newticket
Island
New user
Posts: 2
Joined: 01 Dec 2010, 13:40

Can someone please check this and tell me if it's ok?

Post by Island »

Linux, kubuntu

Code: Select all

krishna@amba:~/warzone2100-2.3.6$ ./autogen.sh
+ checking for autoconf >= 2.56 ... 
You must have autoconf installed to compile Warzone2100.
Download the appropriate package for your distribution,
or get the source tarball at ftp://ftp.gnu.org/pub/gnu/autoconf/
+ checking for automake >= 1.10 ... 
You must have automake installed to compile Warzone2100.
Download the appropriate package for your distribution,
or get the source tarball at ftp://ftp.gnu.org/pub/gnu/automake/
krishna@amba:~/warzone2100-2.3.6$ ./autogen.sh
+ checking for autoconf >= 2.56 ... found 2.65, ok.
+ checking for automake >= 1.10 ... found 1.11.1, ok.
+ running aclocal ...
+ running autoheader ... 
+ running autoconf ... 
+ running automake ... 
+ removing config.cache ... 

Now type './configure && make' to compile.
krishna@amba:~/warzone2100-2.3.6$ ./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... /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... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking for gcc option to accept ISO C99... -std=gnu99
checking for gcc -std=gnu99 option to accept ISO Standard C... (cached) -std=gnu99
checking for ranlib... ranlib
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking for bison... no
checking for byacc... no
configure: error: Bison is not installed
krishna@amba:~/warzone2100-2.3.6$ make install
make: *** No rule to make target `install'. Stop.
krishna@amba:~/warzone2100-2.3.6$ ^C
krishna@amba:~/warzone2100-2.3.6$ cd '/home/krishna/warzone2100-2.3.6
> cd '/home/krishna/warzone2100-2.3.6
bash: cd: /home/krishna/warzone2100-2.3.6
cd /home/krishna/warzone2100-2.3.6: No such file or directory
krishna@amba:~/warzone2100-2.3.6$ sudo make install
[sudo] password for krishna: 
make: *** No rule to make target `install'. Stop.
How do I launch the game?
Cheers
User avatar
NoQ
Special
Special
Posts: 6226
Joined: 24 Dec 2009, 11:35
Location: /var/zone

Re: Can someone please check this and tell me if it's ok?

Post by NoQ »

Install bison, as your text says, and retry ./configure'ing ...
P.S. AFAIK, you don't need to do ./autogen.sh on official version tarballs. Only on master tarballs.
Island
New user
Posts: 2
Joined: 01 Dec 2010, 13:40

Re: Can someone please check this and tell me if it's ok?

Post by Island »

AFAIK? as for ...
I have 2.2.4-3 set up on the comp. It was in the repository, installed in a few minutes and then I could play. Question, why does 2.3.6 need flex bison libpng12-dev libsdl1.2-dev libopenal-dev libphysfs-dev libvorbis-dev libtheora-dev libglc-dev, libpopt-dev package, and bisonc++, OpenGLC, QuesoGLC, FreeType2, Fontconfig, POSIX threads and GNU Make tool.
Just curious. Here is where I got to so far:

Code: Select all

krishna@amba:~/warzone2100-2.3.6$ ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /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... i686-pc-linux-gnu                                                               
checking host system type... i686-pc-linux-gnu                                                                
checking for style of include used by make... GNU                                                             
checking for gcc... gcc                                                                                       
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking for gcc option to accept ISO C99... -std=gnu99
checking for gcc -std=gnu99 option to accept ISO Standard C... (cached) -std=gnu99
checking for ranlib... ranlib
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking for bison... bison -y
checking for bison >= 1.31... found 2.4.1, ok
checking for flex... flex
checking lex output file root... lex.yy
checking lex library... -lfl
checking whether yytext is a pointer... yes
checking for flex >= 2.5.33... found 2.5.35, ok
checking for flex != 2.5.34... not found, good
checking whether perl executable path has been provided... no
checking for perl... /usr/bin/perl
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for perl version... 5.10.1
checking for gawk... (cached) gawk
checking for zip... zip
checking for unzip... unzip
.
checking how to run the C preprocessor... gcc -std=gnu99 -E
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking for strlcpy... no
checking for strlcat... no
checking whether gcc -std=gnu99 accepts -fstack-protector... yes
checking whether g++ accepts -fstack-protector... yes
checking alloca.h usability... yes
checking alloca.h presence... yes
checking for alloca.h... yes
checking whether NLS is requested... yes
checking for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/msgfmt
checking for xgettext... /usr/bin/xgettext
checking for msgmerge... /usr/bin/msgmerge
checking for ld used by GCC... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for shared library run path origin... done
checking for CFPreferencesCopyAppValue... no
checking for CFLocaleCopyCurrent... no
checking for GNU gettext in libc... yes
checking whether to use NLS... yes
checking where the gettext function comes from... libc
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for pkg-config >= 0.9... found 0.22, ok
checking whether to build NSIS installer... no
checking whether to compile in debug mode... no
checking whether the C compiler accepts the -Werror -Wno-switch flag... yes
checking whether the C compiler accepts the -Werror -Wno-enum-compare flag... no
checking for SDL... yes
checking for PNG... yes
checking for THEORA... yes
checking for OPENAL... yes
checking for OGGVORBIS... yes
checking for GLee... no
checking for GLee.h... 
checking for GLee.h with -I/usr/local/include/GL... no
checking for GLee.h with -I/usr/include/GL... no
checking GLee.h usability... no
checking GLee.h presence... no
checking for GLee.h... no
configure: Using integrated GLee
checking for nearbyint in -lm... yes
checking for XSetSelectionOwner in -lX11... yes
checking Xm/Xm.h usability... no
checking Xm/Xm.h presence... no
checking for Xm/Xm.h... no
checking for XmCreateErrorDialog in -lXm... no
checking popt.h usability... yes
checking popt.h presence... yes
checking for popt.h... yes
checking for poptGetContext in -lpopt... yes
checking physfs.h usability... yes
checking physfs.h presence... yes
checking for physfs.h... yes
checking for PHYSFS_init in -lphysfs... yes
checking SDL_opengl.h usability... yes
checking SDL_opengl.h presence... yes
checking for SDL_opengl.h... yes
checking for main in -lGL... yes
checking for main in -lGLU... yes
checking GL/glc.h usability... no
checking GL/glc.h presence... no
checking for GL/glc.h... no
configure: error: OpenGLC header not found. Please install QuesoGLC: http://quesoglc.sourceforge.net/
And then for quesoglc you need what I listed above, after it, to make it work, right?
Cheers
User avatar
lav_coyote25
Professional
Professional
Posts: 3434
Joined: 08 Aug 2006, 23:18

Re: Can someone please check this and tell me if it's ok?

Post by lav_coyote25 »

Island wrote:AFAIK? as for ...

As Far As I Know
User avatar
NoQ
Special
Special
Posts: 6226
Joined: 24 Dec 2009, 11:35
Location: /var/zone

Re: Can someone please check this and tell me if it's ok?

Post by NoQ »

Come on, they've even posted a command in that guide to install all build-time dependencies especially for debian-based-distro users:

Code: Select all

apt-get build-dep warzone2100
Question, why does 2.3.6 need flex bison libpng12-dev libsdl1.2-dev libopenal-dev libphysfs-dev libvorbis-dev libtheora-dev libglc-dev, libpopt-dev package, and bisonc++, OpenGLC, QuesoGLC, FreeType2, Fontconfig, POSIX threads and GNU Make tool.
Just curious.
Because compiling an executable is a more complicated process than running a compiled executable. You need only libraries to run a game, but you also need their header files and different development tools to compile it. Did i answer it?