Hi

I am running Opensuse 10.3 64 bit.

I am unable to get the 64 bit version to run (32bit works fine btw).

All previous versions have been fine...

if I run nexuiz-linux-x86_64-glx or nexuiz-linux-x86_64-sdl

I get - No such file or directory

I.e :-

./nexuiz-linux-glx.sh
./nexuiz-linux-glx.sh: line 121: /home/morgan/Nexuiz/nexuiz-linux-x86_64-glx: No such file or directory
./nexuiz-linux-glx.sh: line 121: /home/morgan/Nexuiz/nexuiz-linux-x86_64-glx: Success

Can anyone help ?

Works fine here - both script and binary directly.

What if you try to run the binary directly?

If i run the 64 bit binaries directly the same thing - i.e :-

/home/morgan/Nexuiz/nexuiz-linux-x86_64-glx: No such file or directory

However as a weird update to this - the exact same .zip file works in gentoo 64bit.

I.e gentoo works fine, suse doesn't (No such file or directory error)

I have re-unziped it ( i had re-downloaded the zip file from another mirror)

Anyone any ideas ?

Yes, build system was a too new distro, so the binaries don't run on your stone age system Try the binaries in the preliminary http://emptyset.endoftheinternet.org/~p ... hotfix.zip

HI.

I actually got it working by compiling the source (found in another thread)

i.e:-

-----------------------
cd Nexuiz
cd sources
unzip engine*
cd darkplaces
make nexuiz
mv nexuiz-glx nexuiz-dedicated nexuiz-sdl ../..
-----------------------

Opensuse 10.3 is not old btw - its the latest version (although gentoo generally has later versions of libraries ...) - what libraries are out of date on the latest opensuse ?

thank you yossarianuk

I had the same problem. Suse10.3 64bit.
Thought I'm blind. The executable was there but the strange error message told me that it's not.
I followed your steps except that I had to install SDL-devel package to get it compiled. Then changed to ~/Nexuiz and could start the cool game with ./nexuiz-glx

Just an idea.. can you tell us if you have /lib64 on suse? I get the impression some distributions use /lib64 for the 64bit stuff while some use /lib for the 64 bit stuff and /lib32 for the 32 bit stuff.
Maybe this makes Nexuiz load the wrong lib which then fails??

Yes, I do have a /lib64 directory.

I get the impression some distributions use /lib64 for the 64bit stuff while some use /lib for the 64 bit stuff and /lib32 for the 32 bit stuff.

Right. My Arch Linux uses /lib for all 64Bit libs and /opt/lib32 for 32Bit libs... However that distro isn't really meant to have multilib support. This structure also confuses the NVidia driver... So yay for packages. Where Nexuiz is also in Arch's package tree.

I welcome our new Lib32/64-Horror overlord!!!

I welcome our new Lib32/64-Horror overlord!!! Very Happy

Uum - thank you - you can sit down again.

Actually I do not even know which system would be the right choice. However having a x86_64 distro where the "actual" libs are located in /lib64 makes no real sense for me. Dunno what matches the LFS. :/
However also no problems with the official Nexuiz package here (just to make sure).

esteel wrote:Just an idea.. can you tell us if you have /lib64 on suse? I get the impression some distributions use /lib64 for the 64bit stuff while some use /lib for the 64 bit stuff and /lib32 for the 32 bit stuff.
Maybe this makes Nexuiz load the wrong lib which then fails??

No, the error message when a 64bit library is compiled in the wrong place, is different to the one reported here.

As a rough guess, I'm betting RPM based distros use /lib64 (SuSE and Fedora are both RPM based, I think).

Just thought I'd chime in on this. Slamd64, a 64-bit port of Slackware, also has the main libs in /lib64. I can confirm that this is not a problem with 2.3, but I did run into it with 2.4. I imagine a simple recompile will fix the problem, but it's still quite annoying.

As far as the LFS goes, there isn't a hard-and-fast rule. That's unfortunate.

Would all of you please test the latest hotfix to see if it helps/breaks or whatever?

http://forums.alientrap.local/viewtopic.php?t=2824

I just found this: https://bugzilla.redhat.com/show_bug.cgi?id=438752

It seems the "which library path should I use" debate is caused by libtool. Depending on what version your distro has decided to include will determine where they're found, and the ability to use libraries in other directories.

I'll keep an eye on this, but it would appear that for the short term, Fedora 9 will still use the ol' /usr/lib64 approach.