Seleucids Posted September 6 Share Posted September 6 The build failure occured when running /libraries/build-source-libs.sh It is at the checking stage. I am using the latest code from gitea main branch as of 6th September 13:40 UTC ``` 0:03.59 checking for rustc... /usr/bin/rustc 0:03.59 checking for cargo... /usr/bin/cargo 0:03.63 checking rustc version... 1.98.1 0:03.65 checking cargo version... 1.98.1 0:03.67 checking for rust host triplet... 0:03.67 ERROR: Don't know how to translate x86_64-pc-linux-gnu for rustc *** Fix above errors and then restart with "./mach build" ERROR: SpiderMonkey build failed ``` Host OS: Arch Linux I found some similar discussions about spidermonkey packages on the Gentoo forum https://bugs.gentoo.org/915651 hopefully it can be of help Link to comment Share on other sites More sharing options...
fabio Posted September 6 Share Posted September 6 I had a similar problem, it looks like building spidermonkey requires huge amount of RAM, and if you don't have enough of it some build process crash. If you are building with -jX (with X which works fine for 0ad and the other libraries), you may want to decrease X when running build-source-libs.sh , so there are less simultaneously build processes and maximum RAM usage decrease. 1 Link to comment Share on other sites More sharing options...
Seleucids Posted September 6 Author Share Posted September 6 (edited) I have 32 GB of RAM I used -j28 (usual value for 0ad in the past and building other AUR packages) now i decreased to -j1. the same error occurs. I suspect this is more of a dependency version issue than a RAM issue Edited September 6 by Seleucids Link to comment Share on other sites More sharing options...
hyperion Posted September 6 Share Posted September 6 2GB per job is usually a good value, not enough for some packages, Webkit being notorious for needing about 4GB per job. Anyway dmesg will tell you if oom happened. Link to comment Share on other sites More sharing options...
Perzival12 Posted 13 hours ago Share Posted 13 hours ago I ran into this problem as well, same exact error message. Should I just restart my computer and try again? Link to comment Share on other sites More sharing options...
Seleucids Posted 1 hour ago Author Share Posted 1 hour ago Didn't fix for me, I suspect package upgrade was the cause Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now