Page 4 of 13
Posted: Mon Dec 01, 2008 10:57 am
by another_commander
There should be. Lines 13 and 15 of the GNUmakefile.postamble should read
BINARY=$(OBJC_PROGRAM_NAME).exe
and
BINARY=$(OBJC_PROGRAM_NAME)
respectively.
Posted: Mon Dec 01, 2008 11:39 am
by tinker
Ahha an overambitious replacement of the first couple of lines of the postamble, that solved the problem thank you.
Posted: Tue Dec 02, 2008 4:56 am
by Simon B
... heh heh heh - we fall over each other getting you help ;)
A possible deb???
Posted: Sun Jan 25, 2009 5:14 pm
by kcallis
I made the mistake of dumping 1.65 (from the repository) and building the 1.71-2 package. That failed miserably! I was looking at the posting and was getting ready to install from source, but wondered if anyone had created a deb for 1.72 in order to make installation a snap?
Posted: Sun Jan 25, 2009 9:08 pm
by DaddyHoggy
Have you tried this? Now getafix has sorted it out - it seems to work fine...
Ahruman wrote:A modified package (oolite-1.72.2.x86.v2.package) is now
available. The previous package (oolite-1.72.2.x86.package) accidentally contained hardware-specific files. Anyone who installed the previous package should update to the new one, even if there are no obvious problems with the old one.
This applies only to the Linux binary release.
64-bit build
Posted: Wed Feb 25, 2009 3:28 am
by kcallis
Thanks to the directions, I got the 64-bit version of Oolite 1.72.1 working nearly flawlessly. The only issue I seem to be having is that I can't seem to get my AddOn loaded.
Is there a way to install system wide? I would rather this be place in /usr/games or some place system wide as opposed to running out of my home directory!
Re: 64-bit build
Posted: Thu Feb 26, 2009 7:04 pm
by _ds_
kcallis wrote:Thanks to the directions, I got the 64-bit version of Oolite 1.72.1 working nearly flawlessly. The only issue I seem to be having is that I can't seem to get my AddOn loaded.
Is there a way to install system wide? I would rather this be place in /usr/games or some place system wide as opposed to running out of my home directory!
I build .debs from checked-out source (plus a patch or two). Works fine.
Outstanding job
Posted: Thu Feb 26, 2009 9:00 pm
by kcallis
Would you add a text file so that one can know what they are downloading.
Thanks!
Ok...
Posted: Sat Feb 28, 2009 5:31 am
by kcallis
I was syncing my laptop to my server and thought I would go ahead and get rid of my ~/src/Oolite directory. I am getting old, so I of course forget that I had my executable in the src directory.
Once I build out my source, is there any make directive that will place the executable and libraries in a system wide directory. If not, what files besides the required oolite do I need to place in a directory (for instance /usr/games/oolite) to make the game run?
Posted: Sun Jun 07, 2009 7:55 am
by PhantorGorth
Trying to compile trunk (build 2196) on Ubuntu (9.04) on a AMD AthlonXP (32 bit) and I am running into problems. I am compiling SpiderMonkey and the first step of compiling the code in fdlibm works fine. The second step of compiling in the parent directory gives the following errors:
Code: Select all
cat: ../../dist/Linux_All_DBG.OBJ/nspr/Version: No such file or directory
cd editline; make -f Makefile.ref all
make[1]: Entering directory `/home/paul/Dev/Oolite/trunk/deps/Cross-platform-deps/SpiderMonkey/js/src/editline'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/home/paul/Dev/Oolite/trunk/deps/Cross-platform-deps/SpiderMonkey/js/src/editline'
make -f Makefile.ref Linux_All_DBG.OBJ/libjs.a Linux_All_DBG.OBJ/libjs.so Linux_All_DBG.OBJ/js Linux_All_DBG.OBJ/jsautocfg.h Linux_All_DBG.OBJ/jscpucfg Linux_All_DBG.OBJ/jscpucfg.o
cat: ../../dist/Linux_All_DBG.OBJ/nspr/Version: No such file or directory
make[1]: Entering directory `/home/paul/Dev/Oolite/trunk/deps/Cross-platform-deps/SpiderMonkey/js/src'
make[1]: Circular jscpucfg.h <- Linux_All_DBG.OBJ/jsautocfg.h dependency dropped.
make[1]: Circular Linux_All_DBG.OBJ/jsautocfg.h <- Linux_All_DBG.OBJ/jsautocfg.h dependency dropped.
gcc -o Linux_All_DBG.OBJ/jsapi.o -c -Wall -Wno-format -g -DXP_UNIX -DSVR4 -DSYSV -D_BSD_SOURCE -DPOSIX_SOURCE -DHAVE_LOCALTIME_R -DX86_LINUX -DDEBUG -DDEBUG_paul -DJS_C_STRINGS_ARE_UTF8 -UMOZILLA_1_8_BRANCH -DEDITLINE -ILinux_All_DBG.OBJ jsapi.c
In file included from jsapi.c:49:
jstypes.h:264:2: error: #error No suitable type for JSInt8/JSUint8
jstypes.h:277:2: error: #error No suitable type for JSInt16/JSUint16
jstypes.h:297:2: error: #error No suitable type for JSInt32/JSUint32
jstypes.h:348:2: error: #error 'sizeof(int)' not sufficient for platform use
In file included from jsapi.c:49:
jstypes.h:393: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘JSBool’
jstypes.h:403: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘JSPackedBool’
.
.
.
Any ideas?
Phantor Gorth
(Paul)
Posted: Sun Jun 07, 2009 9:24 am
by pleb87
I recently compiled Oolite from both 1.72.2 source and the trunk using Ubuntu 8.04 (64-bit) and GNUStep 2.0.2 and had no problems, except I had to rename one of my folders. Try searching this forum for that post (would provide link but im on ps3 and i don't have a usb keyboard and takes hours just to write this!).
Posted: Sun Jun 07, 2009 12:49 pm
by another_commander
I think you are trying to build libjs with JS_THREADSAFE defined. Try to see if this macro is defined somewhere in the makefile and make sure you build without it.
Posted: Sun Jun 07, 2009 6:49 pm
by PhantorGorth
Thanks for the quick response.
Unfortunately, I checked JS_THREADSAFE is not defined anywhere.
By looking deeper in to this it looks like the "Circular" reference bit is stopping jsautocfg.h from being included and that header file contains the macro definitions that hold the size of the differing types for the CPU. Without this the code in jstypes.h baulks. Unfortunately the Circular error line does not provide much info on what is causing it. I looked at the files it gets to before to this see where it goes wrong and they are way to difficult to figure out.
Phantor Gorth
(Paul)
Posted: Tue Jun 09, 2009 11:36 pm
by PhantorGorth
I seem to have got to the bottom of it and fixed the issue.
The subdirectory Linux_All_DBG.OBJ of .../js/src had copy of the file jsautocfg.h (I assume this was created by the first attempt compiling as the directory doesn't exit in the svn repository) This file had the values required but the copy of the file in the .../js/src directory (also must be generated as again it isn't in the repository) was empty. To fix I copied the content of the subdirectory file into the parent file. Compiling after this worked.
Re-reading the instructions in the first post of this thread I had missed a step that populated the file. This goes to show that you should read the instructions several times and once more again just to be sure!
Phantor Gorth
(Paul)
Posted: Sun Jul 05, 2009 11:55 am
by wild turkey
Just to let everyone know I have just compiled Oolite from svn (V1.73?) on Ubuntu 9.04 64bit successfully using the instruction in this topic. Had to rename the directory
deps/Cross-platform-deps/SpiderMonkey/js/src/Linux_All_DBG.OBJ/
to
deps/Cross-platform-deps/SpiderMonkey/js/src/Linux_All_OPT.OBJ/
Everything else went smoothly. Just thought I'd mentioned it as 9.04 is not mentioned in the instructions.
If needed I can also test 1.72.2. Let me know.