n952162 wrote: > > Apparently after a long series of checks, my emerge simply ended. The > only hint of a problem was this message: > > />>> Running pre-merge checks for net-libs/nodejs-14.4.0// > // * ERROR: net-libs/nodejs-14.4.0::gentoo failed (pretend phase):// > // * Your CPU doesn't support the required SSE2 instruction.// > // * // > // * Call stack:// > // * ebuild.sh, line 124: Called pkg_pretend// > // * nodejs-14.4.0.ebuild, line 50: Called die// > // * The specific snippet of code:// > // * (use x86 && ! use cpu_flags_x86_sse2) && \// > // * die "Your CPU doesn't support the required SSE2 > instruction."// > // * // > // * If you need support, post the output of `emerge --info > '=net-libs/nodejs-14.4.0::gentoo'`,// > // * the complete build log and the output of `emerge -pqv > '=net-libs/nodejs-14.4.0::gentoo'`.// > // * The complete build log is located at > '/var/tmp/portage/net-libs/nodejs-14.4.0/temp/build.log'.// > // * The ebuild environment file is located at > '/var/tmp/portage/net-libs/nodejs-14.4.0/temp/die.env'.// > // * Working directory: > '/var/tmp/portage/net-libs/nodejs-14.4.0/homedir'// > // * S: '/var/tmp/portage/net-libs/nodejs-14.4.0/work/node-v14.4.0'/ > > > Is this the problem? I'm not clear on why it's referring to x86. Am > I configured wrong? Is there a work-around? > > My CPU is: > > /$ uname -p// > //Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz/ > > $ uname -m > x86_64 > >
This seems to be the key, /Your CPU doesn't support the required SSE2 instruction. Either your CPU doesn't support that or you have not enabled it or disabled it for some reason. This is where cpuid2cpuflags comes in handy. If you can't tell what is going on still, post emerge --info for that package and also the command you used that resulted in that error. That will likely show the USE flags and give the rest of us more clues to work with. Dale :-) :-) /
