Jump to content

Building Error

Skhorn

By Skhorn,
in Bug reports

 Share

Recommended Posts

Skhorn Duplicarius

Skhorn

Posted
Posted (edited)

Hi, 

I'm using Debian stretch 64bits. I updated the project using svn up, but when i went to build it, it started throwing errors. 

  • Did an apt-get update/upgrade. Checked if the packages needed to build were up to date, and performed the clean-workspaces, but still it thrown an error.
  • Deleted the folder, did svn up again, tried to compile, but nothing. 
In file included from /home/skhorn/Documents/0ad/0ad/libraries/source/spidermonkey/mozjs-38.0.0/js/src/build-debug/js/src/Unified_cpp_js_src1.cpp:110:0:
/home/skhorn/Documents/0ad/0ad/libraries/source/spidermonkey/mozjs-38.0.0/js/src/gc/Marking.cpp: In function ‘void AssertNonGrayGCThing(JSTracer*, void**, JSGCTraceKind)’:
/home/skhorn/Documents/0ad/0ad/libraries/source/spidermonkey/mozjs-38.0.0/js/src/gc/Marking.cpp:1980:1: internal compiler error: in change_scope, at final.c:1609
 }
 ^
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-6/README.Bugs> for instructions.
{standard input}: Assembler messages:
{standard input}: Error: open CFI at the end of file; missing .cfi_endproc directive
/home/skhorn/Documents/0ad/0ad/libraries/source/spidermonkey/mozjs-38.0.0/config/rules.mk:930: recipe for target 'Unified_cpp_js_src1.o' failed
make[3]: *** [Unified_cpp_js_src1.o] Error 1
make[3]: *** Waiting for unfinished jobs....
In file included from /home/skhorn/Documents/0ad/0ad/libraries/source/spidermonkey/mozjs-38.0.0/js/src/build-debug/js/src/Unified_cpp_js_src10.cpp:11:0:
/home/skhorn/Documents/0ad/0ad/libraries/source/spidermonkey/mozjs-38.0.0/js/src/vm/Debugger.cpp: In function ‘bool DebuggerObject_unsafeDereference(JSContext*, unsigned int, JS::Value*)’:
/home/skhorn/Documents/0ad/0ad/libraries/source/spidermonkey/mozjs-38.0.0/js/src/vm/Debugger.cpp:7100:1: internal compiler error: Segmentation fault
 DebuggerObject_unsafeDereference(JSContext* cx, unsigned argc, Value* vp)
 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-6/README.Bugs> for instructions.
/home/skhorn/Documents/0ad/0ad/libraries/source/spidermonkey/mozjs-38.0.0/config/rules.mk:930: recipe for target 'Unified_cpp_js_src10.o' failed
make[3]: *** [Unified_cpp_js_src10.o] Error 1
make[3]: Leaving directory '/home/skhorn/Documents/0ad/0ad/libraries/source/spidermonkey/mozjs-38.0.0/js/src/build-debug/js/src'
/home/skhorn/Documents/0ad/0ad/libraries/source/spidermonkey/mozjs-38.0.0/config/recurse.mk:74: recipe for target 'js/src/target' failed
make[2]: *** [js/src/target] Error 2
make[2]: Leaving directory '/home/skhorn/Documents/0ad/0ad/libraries/source/spidermonkey/mozjs-38.0.0/js/src/build-debug'
/home/skhorn/Documents/0ad/0ad/libraries/source/spidermonkey/mozjs-38.0.0/config/recurse.mk:36: recipe for target 'compile' failed
make[1]: *** [compile] Error 2
make[1]: Leaving directory '/home/skhorn/Documents/0ad/0ad/libraries/source/spidermonkey/mozjs-38.0.0/js/src/build-debug'
/home/skhorn/Documents/0ad/0ad/libraries/source/spidermonkey/mozjs-38.0.0/config/rules.mk:541: recipe for target 'default' failed
make: *** [default] Error 2
ERROR: SpiderMonkey build failed

Perhaps i'm missing something? 

Did what was in the BuildInstructions. 

svn up
cd build/workspaces
./update-workspaces.sh -j3
cd gcc
make -j3


Sorry i don't know how to reports such bugs, if something else is needed i will upload it

System info just in case

  Reveal hidden contents

 

Edited by Skhorn
Link to comment
Share on other sites
Itms Primus Pilus

Itms

Posted
Posted

It looks like SpiderMonkey compilation doesn't work with your compiler (doesn't look like it's related to dependencies). I compile it with GCC 6 as well on my Linux box (and so do a lot of people) so there must be some strange thing happening with your setup. Can you give us the output of 

g++ -dumpversion

(maybe it's some strange minor version)

Or maybe try 

update-workspaces.sh -j1

Really I'm not sure where that could come from, so I'm just throwing ideas.

  • Thanks 1
Link to comment
Share on other sites
Skhorn Duplicarius

Skhorn

Posted
  • Author
Posted
  On 12/02/2018 at 9:45 AM, Imarok said:

Have you installed all dependencies listed on the trac wiki page?

Expand  

Yes

  On 12/02/2018 at 12:13 PM, Itms said:

g++ -dumpversion

Expand   
skhorn@Morgul ~/D/0/0/b/workspaces> g++ -dumpversion
6.3.0

 

  On 12/02/2018 at 12:13 PM, Itms said: 
update-workspaces.sh -j1

Really I'm not sure where that could come from, so I'm just throwing ideas.

Expand  

That worked! But i don't understand why, as far as i know, -j# wasn't the amount of cpu cores used to compile it?

Used too the make -j1

My only bet is, that a few weeks ago i was messing with the sources.list, added a a few from the Kali repo and when i did an update/upgrade i forgot to delete them, so it installed a lot of packages, but not really sure if one of those affected the gcc. That's my only bet, don't know what else could be.

Thank you!

  • Like 1
Link to comment
Share on other sites
Itms Primus Pilus

Itms

Posted
Posted

I believe you actually encountered a bug in gcc 6.3.0 where the parallel build fails for some reason (looking at the assembler messages above it must be some race condition on the access to some temporary file). If you have some time maybe you should report it upstream or ask your package maintainers.

You should try make -j3, there are good chances that our code doesn't trigger this bug, and it will allow you to build more quickly (you shouldn't have to build SpiderMonkey too often).

You're welcome :)

  • Thanks 1
Link to comment
Share on other sites
  • 10 months later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
 Share
Go to topic listing
×
×
  • Create New...