Nexuiz 2.4 - x86_64 broken ?

[Zico]

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).

[LaughingBoy]

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).

[Spinlock]

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.

[esteel]

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

[LaughingBoy]

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.