Hi all, not entirely sure if this should fit into bugs, development or newb questions as I can't quite figure out what the actual problem is.
First off, congrats on a very very nice T4 - and the new engine is brilliant! My productivity this week has hit an all time low.
So the issue is this, got it to compile on my 32 bit ubuntu 10.04 work machine just fine, had to go get all the sdl libraries but no issues whatsoever when compiling or playing. Then I decided it'd be more reasonable to only have it at home. Tried the same thing, this time on a 64 bit machine (same OS) and came up with this error:
ljit_dasm.c
src/luajit/ljit_dasm.c(35): catastrophic error: #error directive: "No support for this architecture (yet)"
#error "No support for this architecture (yet)"
^
compilation aborted for src/luajit/ljit_dasm.c (code 4)
make[1]: *** [obj/Debug/luajitx86/ljit_dasm.o] Error 4
make: *** [luajitx86] Error 2
After a quick poke about on the net it seems luajit didnt have support for 64 bit systems for quite a while but that issue seems to have been resolved now. Ive downloaded all the sdl libraries, and even downloaded the ubuntu repository binaries for luajit in the hopes I could compile all but luajit and still run. But no changes. Am I missing something?
Many thanks!
64 bit Linux
Moderator: Moderator
Re: 64 bit Linux
Yes luajit1 does not support 64bit.
Luajit 2 does but it's still beta and lacks a very important feature that TE4 uses: dumping a function as bytecode.
So you have three options:
- compile as 32bits (no idea how I dont have a 64bits system)
- compile without luajit
- help luajit2 improve ;>
Luajit 2 does but it's still beta and lacks a very important feature that TE4 uses: dumping a function as bytecode.
So you have three options:
- compile as 32bits (no idea how I dont have a 64bits system)
- compile without luajit
- help luajit2 improve ;>
[tome] joylove: You can't just release an expansion like one would release a Kraken XD
--
[tome] phantomfrettchen: your ability not to tease anyone is simply stunning
--
[tome] phantomfrettchen: your ability not to tease anyone is simply stunning

Re: 64 bit Linux
I might have to go with options one and two and post what I find here... Being a biologist, my coding's pretty shoddy and I don't think I'd help luajit improve much
Thanks!

Thanks!
Re: 64 bit Linux

[tome] joylove: You can't just release an expansion like one would release a Kraken XD
--
[tome] phantomfrettchen: your ability not to tease anyone is simply stunning
--
[tome] phantomfrettchen: your ability not to tease anyone is simply stunning

Re: 64 bit Linux
Here's my hacky method of compiling the T-Engine as a 32-bit program on a 64-bit system:
Now if you want the debug version you can type:
Or if you want the optimized release version, type:
And now just type "./t-engine" to start the game. This works for me at least. Note that you will need the 32-bit system emulation libraries to run the game.
Code: Select all
tar xjf t-engine4-src-1.0.0beta4.tar.bz2
cd t-engine4-src-1.0.0beta4
wget http://sourceforge.net/projects/premake/files/Premake/4.2.1/premake-4.2.1-linux.tar.gz/download
tar xzf premake-4.2.1-linux.tar.gz
sed -i 's/buildoptions { "/buildoptions { "-m32 /' premake4.lua
./premake4 gmake
sed -i 's/LDFLAGS += /LDFLAGS += -m32 /' TEngine.make
Code: Select all
make config=debug
cp bin/Debug/t-engine .
Code: Select all
make config=release
cp bin/Release/t-engine .
Re: 64 bit Linux
Nice one!
Id been consistently failing when not compiling luajit at the final linking during compiling. And compiling as 32 bit, I was most likely forgetting the necessary flags during premake. Using the -m32 options gave me errors where it was looking for the wrong compiler.
The final alternative is to run it in WinE, which seems to be working fine.
Thanks!
Id been consistently failing when not compiling luajit at the final linking during compiling. And compiling as 32 bit, I was most likely forgetting the necessary flags during premake. Using the -m32 options gave me errors where it was looking for the wrong compiler.
The final alternative is to run it in WinE, which seems to be working fine.
Thanks!