I remember previous comments about needing to mount e.g. /dev, here
are a couple of related requirements: xulrunner needs /dev
(specifically /dev/urandom) very early in its build. And then at
the end it needs /proc [ it also needs this when firefox starts up,
but I guess we all have /proc mounted when a new system has booted ],
otherwise it gives errors like:
^G###!!! ABORT: Recursive layout module initialization: file
/scratch/working/mozilla-release/layout/build/nsLayoutModule.cpp,
line 373
###!!! ABORT: Recursive layout module initialization: file
/scratch/working/mozilla-release/layout/build/nsLayoutModule.cpp,
line 373
/bin/sh: line 1: 797 Segmentation fault
/scratch/working/mozilla-release/xulrunner-build-dir/dist/bin/run-mozilla.sh
/scratch/working/mozilla-release/xulrunner-build-dir/dist/bin/xpcshell
-g "$PWD" -a "$PWD" -f
/scratch/working/mozilla-release/toolkit/mozapps/installer/precompile_cache.js
-e "populate_startupcache('startupCache.zip');"
make[1]: *** [prepare-package] Error 139
make[1]: Leaving directory
`/scratch/working/mozilla-release/xulrunner-build-dir/xulrunner/installer'
make: *** [install] Error 2
- yes, that really was a ^G in the log, and obviously change
/scratch/working to wherever you build it. Those were with 19.0.2
but if I was a gambling man I'd put money on 20.0 being the same.
ĸen, getting through my 'updated' build, but expecting to trash it
and "start over" at the end because of what I've learned.
--
das eine Mal als Tragödie, das andere Mal als Farce
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
