> * Update cube_unix so that it uses the exact path to linux_client

It already does:

> CUBE_DIR=~/cube
> [...]
> cd ${CUBE_DIR}
> exec ${CUBE_DIR}/bin_unix/${MACHINE_PREFIX}${SYSTEM_PREFIX}client $*

And it has nothing to do with the problem with Ryzom, where the executed file is a binary, not a shell script. Like I said, Cube isn't all that important.


> I've seen similar errors on another architecture when the dynamic linker
> specified in the binaries was missing. Missing 32-bit libraries might
> cause it when running 32-bit programs on 64-bit x86 systems.
>
> ("objdump -sj .interp" shows what dynamic linker the binary uses.)

Well, I'm using the 64-bit version, but I was using the 64-bit version on Trisquel 5.5 too. I'd still like to check this, but I don't really understand what I'm supposed to do with "objdump -sj .interp" (that exact command just gives an error).


> A free (at least from what I can see, some sources say it's non-free in the
> same sense as well) alternative to Cube is Red Eclipse, in case you're
> interested.

I already know about Red Eclipse and have it installed. Like I said, I don't much like Cube, but what I like in Cube 2 is the single-player, not the multi-player; Red Eclipse doesn't have this. The only completely free FPS I'm aware of with a proper single-player campaign is Freedoom; all the others just have multiplayer, which is particularly annoying when they have so few people playing at any given time that the only way to play multiplayer is to be opportunistic (this applies to every free FPS that I know of except for AssaultCube and OpenArena).

Reply via email to