Re: [Warzone-dev] [Fwd: warzone2100-2.0.5 fails to compile on Gentoo/amd64]

2007-02-27 Thread Dmitrij Czarkoff

On 2/26/07, Gerard Krol <[EMAIL PROTECTED]> wrote:

Your link command line:

gcc  -g -O2  -DNDEBUG -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT
-I/usr/X11R6/include/SDL -m32 -DYY_STATIC
-DDEFAULT_DATADIR=\"/usr/local/share/warzone2100\"   


<...>


I suggest you just compile warzone for 64 bit (so without the -m32),
works fine for me (amd64, Debian).


Thank You!

After executing changing all -m32 entries to -m64 I've finally got
warzone2100 compiled, but it segfaults each time I try to run it less
then in a second.

Could that be because I use DRI 3D acceleration for my ATi Mobility
X700 adapter? If so, is there any way to tune down the visual effects
in warzone2100 _before_ launching the game?

--
.0.
..0
000

___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev


Re: [Warzone-dev] [Fwd: warzone2100-2.0.5 fails to compile on Gentoo/amd64]

2007-02-26 Thread Gerard Krol

Kamaze wrote:

 Original-Nachricht 
Betreff: warzone2100-2.0.5 fails to compile on Gentoo/amd64
Datum: Mon, 26 Feb 2007 00:34:24 +0300
Von: Dmitrij Czarkoff <[EMAIL PROTECTED]>
An: [EMAIL PROTECTED]

Tried to compile warzone2100 on my amd64 machine (both via portage and
manually). After autogen.sh and configure run OK it fails to make. See
the log (make -dk --warn-undefined-variables &> ../warzone2100.log)
attached.

About my computer:
CPU: Turion64 MT28
Chipset: ATi RX480M + ATi SB400
RAM: 1Gb (I don't know vendor, but no bugs were discovered)
OS: Gentoo

I've got all the demands (as listed in COMPILE instruction) met. As
You don't name the versions of software needed, I'm reporting mines
(output of emerge -pv):

[ebuild   R   ] sys-devel/autoconf-2.61  USE="-emacs" 0 kB
[ebuild   R   ] sys-devel/gcc-4.1.2  USE="gtk nls (-altivec)
-bootstrap -build -doc -fortran -gcj (-hardened) -ip28 -ip32r10k
-mudflap (-multilib) -multislot (-n32) (-n64) -nocxx -objc -objc++
-objc-gc -test -vanilla" 0 kB
[ebuild   R   ] sys-devel/make-3.81  USE="nls -static" 0 kB
[ebuild   R   ] media-libs/libsdl-1.2.11-r1  USE="X aalib alsa opengl
xv -arts -dga -directfb -esd -fbcon -ggi -libcaca -nas -noaudio
-noflagstrip -nojoystick -novideo -oss (-svga) -xinerama" 0 kB
[ebuild   R   ] media-libs/sdl-net-1.2.6  0 kB
[ebuild   R   ] media-libs/libvorbis-1.1.2  USE="-aotuv" 0 kB
[ebuild   R   ] media-libs/libmad-0.15.1b-r2  USE="-debug" 0 kB
[ebuild   R   ] sys-libs/zlib-1.2.3-r1  USE="-build" 0 kB
[ebuild   R   ] dev-games/physfs-1.0.1  0 kB
[ebuild   R   ] media-libs/openal-0.0.8-r1  USE="alsa mp3 sdl vorbis
-arts -debug -esd" 0 kB
[ebuild   R   ] media-libs/libpng-1.2.16  USE="-doc" 0 kB
[ebuild   R   ] media-libs/jpeg-6b-r8  0 kB

What could be the problem here?

  

Your link command line:

gcc  -g -O2  -DNDEBUG -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT 
-I/usr/X11R6/include/SDL -m32 -DYY_STATIC 
-DDEFAULT_DATADIR=\"/usr/local/share/warzone2100\"   


Notice the -m32? You are compiling warzone to a 32 bit executable. Now 
look at this:


/usr/lib/gcc/x86_64-pc-linux-gnu/4.1.2/../../../../x86_64-pc-linux-gnu/bin/ld: 
skipping incompatible /usr/X11R6/lib/libphysfs.so when searching for 
-lphysfs
/usr/lib/gcc/x86_64-pc-linux-gnu/4.1.2/../../../../x86_64-pc-linux-gnu/bin/ld: 
skipping incompatible /usr/X11R6/lib/libphysfs.a when searching for -lphysfs
/usr/lib/gcc/x86_64-pc-linux-gnu/4.1.2/../../../../x86_64-pc-linux-gnu/bin/ld: 
skipping incompatible 
/usr/lib/gcc/x86_64-pc-linux-gnu/4.1.2/../../../libphysfs.so when 
searching for -lphysfs
/usr/lib/gcc/x86_64-pc-linux-gnu/4.1.2/../../../../x86_64-pc-linux-gnu/bin/ld: 
skipping incompatible 
/usr/lib/gcc/x86_64-pc-linux-gnu/4.1.2/../../../libphysfs.a when 
searching for -lphysfs
/usr/lib/gcc/x86_64-pc-linux-gnu/4.1.2/../../../../x86_64-pc-linux-gnu/bin/ld: 
skipping incompatible /usr/lib/libphysfs.so when searching for -lphysfs
/usr/lib/gcc/x86_64-pc-linux-gnu/4.1.2/../../../../x86_64-pc-linux-gnu/bin/ld: 
skipping incompatible /usr/lib/libphysfs.a when searching for -lphysfs
/usr/lib/gcc/x86_64-pc-linux-gnu/4.1.2/../../../../x86_64-pc-linux-gnu/bin/ld: 
cannot find -lphysfs


You seem to have the 64 bit lib of physfs.

I suggest you just compile warzone for 64 bit (so without the -m32), 
works fine for me (amd64, Debian).


- Gerard

___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev


Re: [Warzone-dev] [Fwd: warzone2100-2.0.5 fails to compile on Gentoo/amd64]

2007-02-26 Thread Per Inge Mathisen

On 2/26/07, Kamaze <[EMAIL PROTECTED]> wrote:

Tried to compile warzone2100 on my amd64 machine (both via portage and
manually). After autogen.sh and configure run OK it fails to make. See
the log (make -dk --warn-undefined-variables &> ../warzone2100.log)
attached.


How about just posting the error message you get from make? I am not
going to read all that insanely long log.

 - Per

___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev