<covici <at> ccs.covici.com> writes: > Hi. I am having problems emerging nodejs 6.2.1 which happened on my > last update of world. I get the following error output:
OK, so, I'm "no java whiz" so keep that in mind.... I was just able to install it:: Installed versions: 6.2.1(09:59:02 AM 06/27/2016)(npm snapshot ssl -debug -doc -icu -test CPU_FLAGS_X86="sse2" PYTHON_TARGETS="python2_7") So it's probably an issue on your system. Security reading suggest that 6.3.0 is out, so I'd file a bug at bgo to 'version bump' it anyway. First, look at the ebuild as the install procedure is quite long for an ebuild. So that means there are plenty of place where compiling can go wrong. Looking at the ebuild flow of control and correlating the issues in the elog file helps you to comprehend the steps and particularly hone in on where the compile fail occurred. Go to the build dir and look at the intermediate files for issues, permission etc etc. > [ -x ./node ] && ./node tools/doc/generate.js --node-version=v6.2.1 > --format=html --template=doc/template.html doc/api/modules.md > > out/doc/api/modules.html || node tools/doc/generate.js > --node-version=v6.2.1 --format=html --template=doc/t\emplate.html > doc/api/modules.md > out/doc/api/modules.html > Input file = doc/api/modules.md > module.js:442 > throw err; > ^ > Right below here the errors narrow in:: > Error: Cannot find module Here they tell you want one of the problems is, below. > Error: Cannot find module > Any assistance would be appreciated. > You can publish your java settings and I'll compare against mine (I'm not really sure how to print the java-settings only... Good Hunting! hth, James
