Or just make it easy on yourself and use Wine?

On 2/26/07, Dennis Schridde <[EMAIL PROTECTED]> wrote:
Am Montag, 26. Februar 2007 schrieb Giel van Schijndel:
> On Mon, 26 Feb 2007 11:37:13 +0100, Gerard Krol
<[EMAIL PROTECTED]> wrote:
> > 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/b
> >>in/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/b
> >>in/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/b
> >>in/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/b
> >>in/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/b
> >>in/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/b
> >>in/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/b
> >>in/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).
>
> Also keep in mind that the linker commandline isn't the only one containing
> -m32, every single source file is compiled with that.

Also keep in mind that Warzone 2.0 can not be compiled for 64bit. Even a
binary compiled from current svn will crash at some point, afaik.
If you want to play it and not go into fixing 64bit bugs, the best is probably
to create a 32bit system. I thought Gentoo did that automatically on
x86_64...

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




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

Reply via email to