n952162 wrote: > > On 2020-10-11 22:57, Dale wrote: >> n952162 wrote: >>> On 2020-10-11 22:23, Dale wrote: >>>> 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 >>>> >>>> :-) :-) >>>> / >>> >>> Would that be different than the info output I sent in the original >>> posting? >>> >>> >> >> What might help, the listing of USE flags for that package. emerge -uvp >> /net-libs/nodejs should list the USE flags and how they are set. From >> the error, either something is set wrong for your CPU or SSE2 is >> disabled or something somewhere. It's where I'd start figuring out the >> problem. Either way, it needs to recognize your CPU and it's >> instruction sets properly. >> >> Someone else may have a better idea or ran into this and know the most >> likely cause. >> >> Dale >> >> :-) :-) >> / >> > $ pwd > /etc/portage/package.use > $ grep node * > $ lf /var/db/pkg/net-libs > gnutls-3.5.19/ http-parser-2.8.1/ libmnl-1.0.4/ libnsl-1.2.0/ > libpcap-1.8.1/ libssh2-1.8.0-r1/ libtirpc-1.0.2-r1/ > > i.e. it's not currently installed. > > And in make.conf, there's only this: > > USE="-elogind" > > > >
The output of emerge -uvp net-libs/nodejs would be more helpful. Also emerge --info may help. There's a setting somewhere that needs to be changed. Dale :-) :-)
