Re: [gentoo-user] What happened to my emerge -u?
On 2020-10-12 00:42, Neil Bothwick wrote: On Sun, 11 Oct 2020 22:44:45 +0200, n952162 wrote: I don't know why it's written in such an opaque manner (a simple `if` would suffice), but it seems like this error is printed only if x86 is used and SSE2 is disabled, which doesn't make sense to me? Is SSE2 required for building/ running NodeJS on x86 machines? But how can my CPU be mistaken for a 32-bit machine? /Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz/ It's not your CPU type but the type of CPU you are building for. The key information from emerge --info is CHOST="i686-pc-linux-gnu" when it should be CHOST="x86_64-pc-linux-gnu" !!! wow. I'm dumbfounded. This is one of the machines I've been trying to get updated for awhile. It seemed this time that I'd found the proper incantation, because it got farther than before. But I discover now that I have NO saved emerge output from a system*.out or world*.out file that has "Emerging" lines in it (portage is very frugal with its unequivocal progress markers). Perhaps I have indeed used the wrong stage 3. Thank you for the tip.
Re: [gentoo-user] What happened to my emerge -u?
On Sun, 11 Oct 2020 22:44:45 +0200, n952162 wrote: > > I don't know why it's written in such an opaque manner (a simple > > `if` would suffice), but it seems like this error is printed only if > > x86 is used and SSE2 is disabled, which doesn't make sense to me? > > Is SSE2 required for building/ running NodeJS on x86 machines? > > > > But how can my CPU be mistaken for a 32-bit machine? > > /Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz/ It's not your CPU type but the type of CPU you are building for. The key information from emerge --info is CHOST="i686-pc-linux-gnu" when it should be CHOST="x86_64-pc-linux-gnu" However, it is not as simple as editing make.conf, changing the CHOST of an installation is not supported, the setting is usually derived from the stage3 you started with. Backup settings and home then reinstall may be the easiest way out of this. -- Neil Bothwick When cryptography is outlawed, bayl bhgynjf jvyy unir cevinpl. pgpDVLDohkpns.pgp Description: OpenPGP digital signature
Re: [gentoo-user] What happened to my emerge -u?
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 :-) :-)
Re: [gentoo-user] What happened to my emerge -u?
On 11/10/2020 21:55, n952162 wrote: I ran into this: https://forums.gentoo.org/viewtopic-t-1108636-start-0.html but I really don't understand anything about these alternative instruction sets and would think my CPU is pretty vanilla. I mean, I hope to avoid trail-and-error approaches to solving this ... My first reaction was "have you specified x86 in make.conf?". As others have said, you need to make sure it's either x86_64, or AMD64, whatever is appropriate. I think SSE2 first appeared about the end of the Pentium era (if not earlier), so any half-way-modern cpu will have it. Dunno whether these musings will be any help, but we'll see ... Cheers, Wol
Re: [gentoo-user] What happened to my emerge -u?
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"
Re: [gentoo-user] What happened to my emerge -u?
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 :-) :-) /
Re: [gentoo-user] What happened to my emerge -u?
On 2020-10-11 21:34, 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 I ran into this: https://forums.gentoo.org/viewtopic-t-1108636-start-0.html but I really don't understand anything about these alternative instruction sets and would think my CPU is pretty vanilla. I mean, I hope to avoid trail-and-error approaches to solving this ...
Re: [gentoo-user] What happened to my emerge -u?
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?
Re: [gentoo-user] What happened to my emerge -u?
On 2020-10-11 22:44, n952162 wrote: On 2020-10-11 22:39, Ashley Dixon wrote: On Sun, Oct 11, 2020 at 09:35:07PM +0100, Ashley Dixon wrote: `pkg_pretend` issues that error only if the architecture is x86 and SSE2 is enabled in the USE-flags: (use x86 && ! use cpu_flags_x86_sse2) && \ die "Your CPU doesn't support the required SSE2 instruction." Sorry, I read that line wrong. Tired. I don't know why it's written in such an opaque manner (a simple `if` would suffice), but it seems like this error is printed only if x86 is used and SSE2 is disabled, which doesn't make sense to me? Is SSE2 required for building/ running NodeJS on x86 machines? But how can my CPU be mistaken for a 32-bit machine? /Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz/ 02~/adm/gentoo/emerged>less /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz stepping : 10 microcode : 0xa07 cpu MHz : 1656.069 cache size : 3072 KB physical id : 0 siblings : 2 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arc> bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf bogomips : 5866.98 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz stepping : 10 microcode : 0xa07 cpu MHz : 1994.147 cache size : 3072 KB physical id : 0 siblings : 2 core id : 1 cpu cores : 2 apicid : 1 initial apicid : 1 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arc> bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf bogomips : 5866.98 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management:
Re: [gentoo-user] What happened to my emerge -u?
On 2020-10-11 22:39, Ashley Dixon wrote: On Sun, Oct 11, 2020 at 09:35:07PM +0100, Ashley Dixon wrote: `pkg_pretend` issues that error only if the architecture is x86 and SSE2 is enabled in the USE-flags: (use x86 && ! use cpu_flags_x86_sse2) && \ die "Your CPU doesn't support the required SSE2 instruction." Sorry, I read that line wrong. Tired. I don't know why it's written in such an opaque manner (a simple `if` would suffice), but it seems like this error is printed only if x86 is used and SSE2 is disabled, which doesn't make sense to me? Is SSE2 required for building/ running NodeJS on x86 machines? But how can my CPU be mistaken for a 32-bit machine? /Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz/
Re: [gentoo-user] What happened to my emerge -u?
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 :-) :-) / / / /$ //cpuid2cpuflags/ /CPU_FLAGS_X86: mmx mmxext sse sse2 sse3 sse4_1 ssse3 / I forgot to include this, from /var/log/emerge.log: /1602438887: Started emerge on: Oct 11, 2020 19:54:47// //1602438887: *** emerge --verbose-conflicts --update --backtrack=100 --changed-deps=y --deep --keep-going --with-bdeps=y --reinstall=changed-use --verbose @world// //1602438960: *** exiting unsuccessfully with status '1'.// //1602438960: *** terminating.// //1602442111: Started emerge on: Oct 11, 2020 20:48:31// //1602442111: *** emerge --verbose-conflicts --update --backtrack=100 --changed-deps=y --deep --keep-going --with-bdeps=y --reinstall=changed-use --verbose @world// //1602442182: *** exiting unsuccessfully with status '1'.// //1602442182: *** terminating./ Is this business with the SSE2 instructions the thing that's causing the emerge failure?
Re: [gentoo-user] What happened to my emerge -u?
On Sun, Oct 11, 2020 at 09:35:07PM +0100, Ashley Dixon wrote: > `pkg_pretend` issues that error only if the architecture is x86 and SSE2 is > enabled in the USE-flags: > > (use x86 && ! use cpu_flags_x86_sse2) && \ > die "Your CPU doesn't support the required SSE2 instruction." Sorry, I read that line wrong. Tired. I don't know why it's written in such an opaque manner (a simple `if` would suffice), but it seems like this error is printed only if x86 is used and SSE2 is disabled, which doesn't make sense to me? Is SSE2 required for building/ running NodeJS on x86 machines? -- Ashley Dixon suugaku.co.uk 2A9A 4117 DA96 D18A 8A7B B0D2 A30E BF25 F290 A8AA signature.asc Description: PGP signature
Re: [gentoo-user] What happened to my emerge -u?
On Sun, Oct 11, 2020 at 03:23:50PM -0500, Dale wrote: > 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. `pkg_pretend` issues that error only if the architecture is x86 and SSE2 is enabled in the USE-flags: (use x86 && ! use cpu_flags_x86_sse2) && \ die "Your CPU doesn't support the required SSE2 instruction." Considering the output of `uname -m`, I cannot imagine why `use x86` is returning true; surely `amd64` would be the appropriate flag? Strange... https://gitweb.gentoo.org/repo/gentoo.git/tree/net-libs/nodejs/nodejs-14.4.0.ebuild#n50 -- Ashley Dixon suugaku.co.uk 2A9A 4117 DA96 D18A 8A7B B0D2 A30E BF25 F290 A8AA signature.asc Description: PGP signature
Re: [gentoo-user] What happened to my emerge -u?
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 :-) :-) /
