libjs.a: No such file or directory

For discussion of ports to POSIX based systems, especially using GNUStep.

Moderators: winston, another_commander, Getafix

Post Reply
User avatar
Getafix
Quite Grand Sub-Admiral
Quite Grand Sub-Admiral
Posts: 979
Joined: Tue Apr 01, 2008 12:55 pm
Location: A small ice asteroid, orbiting Oresrati in Galaxy 8 (a.k.a. northwest Armorica).
Contact:

libjs.a: No such file or directory

Post by Getafix »

The trunk revision 1857 till now (1941) fails to build with the following error:

Code: Select all

 Linking objc_program oolite ...
gcc: deps/Cross-platform-deps/SpiderMonkey/js/src/Linux_All_OPT.OBJ/libjs.a: No such file or directory
make[1]: *** [obj/oolite] Error 1
make: *** [oolite.all.objc-program.variables] Error 2
The actual path for me is Linux_All_DBG.OBJ and consequently it fails to build.
I believe this is true for all users with gnustep-make version >= 2.0.0 where debug flag is by default true.

For the moment I have renamed my path
trunk/deps/Cross-platform-deps/SpiderMonkey/js/src/Linux_All_DBG.OBJ
to
trunk/deps/Cross-platform-deps/SpiderMonkey/js/src/Linux_All_OPT.OBJ
and it links successfully.

(EDIT 08/Jan/2009)
The file <Makefile> appeared in revision 1857 that has this path hard coded.
A first attempt to alter this, did not solve the issue.
If this is not to be changed, please inform me, in order to update the Ubuntu development environment setup instructions.
"Any sufficiently advanced information is indistinguishable from noise." [Newman, Lachmann, Moore]
User avatar
Thargoid
Thargoid
Thargoid
Posts: 5528
Joined: Thu Jun 12, 2008 6:55 pm

Post by Thargoid »

Just had exactly this problem. Brand new download of both the dev and Ubuntu itself.

The rename trick seems to have solved it though :) And this machine with Ubuntu even has shaders :D
User avatar
JensAyton
Grand Admiral Emeritus
Grand Admiral Emeritus
Posts: 6657
Joined: Sat Apr 02, 2005 2:43 pm
Location: Sweden
Contact:

Re: libjs.a: No such file or directory

Post by JensAyton »

Getafix wrote:
(EDIT 08/Jan/2009)
The file <Makefile> appeared in revision 1857 that has this path hard coded.
A first attempt to alter this, did not solve the issue.
If this is not to be changed, please inform me, in order to update the Ubuntu development environment setup instructions.
This change was made by mwerle. I’m not sure who that is in forumspace. Help?
another_commander
Quite Grand Sub-Admiral
Quite Grand Sub-Admiral
Posts: 6740
Joined: Wed Feb 28, 2007 7:54 am

Post by another_commander »

Micha.
User avatar
Micha
Commodore
Commodore
Posts: 815
Joined: Tue Sep 02, 2008 2:01 pm
Location: London, UK
Contact:

Post by Micha »

Hey guys,

Sorry I haven't been around much lately - hopefully my situation will be resolved soonish and I can get back into Oolite :)

Using the 'Makefile' you can build debug or release versions of the executable - and under Linux it will build the relevant version of libjs as well. So it's a lot more convenient to build the sources.


From a brand-new checkout, it 'should' simply be a case of:

make -f Makefile pkg-deb => build a release exe packaged up as a Debian/Ubuntu package.

Other targets:
make -f Makefile help => list of targets
make -f Makefile release => build a release exe (using a release-build of libjs)
make -f Makefile debug => build a debug exe (using a debug-build of libjs)


If somebody could please confirm that this still works? Much appreciated..

Otherwise, to build the optimised version of libjs manually, which will create the Linux_All_OPT.OBJ directory:

make -f Makefile.ref BUILD_OPT=1

Cheers,
- Micha.
The glass is twice as big as it needs to be.
Post Reply