| 1 |
On 2020-10-11 22:23, Dale wrote: |
| 2 |
> n952162 wrote: |
| 3 |
>> |
| 4 |
>> Apparently after a long series of checks, my emerge simply ended. |
| 5 |
>> The only hint of a problem was this message: |
| 6 |
>> |
| 7 |
>> />>> Running pre-merge checks for net-libs/nodejs-14.4.0// |
| 8 |
>> // * ERROR: net-libs/nodejs-14.4.0::gentoo failed (pretend phase):// |
| 9 |
>> // * Your CPU doesn't support the required SSE2 instruction.// |
| 10 |
>> // * // |
| 11 |
>> // * Call stack:// |
| 12 |
>> // * ebuild.sh, line 124: Called pkg_pretend// |
| 13 |
>> // * nodejs-14.4.0.ebuild, line 50: Called die// |
| 14 |
>> // * The specific snippet of code:// |
| 15 |
>> // * (use x86 && ! use cpu_flags_x86_sse2) && \// |
| 16 |
>> // * die "Your CPU doesn't support the required SSE2 |
| 17 |
>> instruction."// |
| 18 |
>> // * // |
| 19 |
>> // * If you need support, post the output of `emerge --info |
| 20 |
>> '=net-libs/nodejs-14.4.0::gentoo'`,// |
| 21 |
>> // * the complete build log and the output of `emerge -pqv |
| 22 |
>> '=net-libs/nodejs-14.4.0::gentoo'`.// |
| 23 |
>> // * The complete build log is located at |
| 24 |
>> '/var/tmp/portage/net-libs/nodejs-14.4.0/temp/build.log'.// |
| 25 |
>> // * The ebuild environment file is located at |
| 26 |
>> '/var/tmp/portage/net-libs/nodejs-14.4.0/temp/die.env'.// |
| 27 |
>> // * Working directory: |
| 28 |
>> '/var/tmp/portage/net-libs/nodejs-14.4.0/homedir'// |
| 29 |
>> // * S: '/var/tmp/portage/net-libs/nodejs-14.4.0/work/node-v14.4.0'/ |
| 30 |
>> |
| 31 |
>> |
| 32 |
>> Is this the problem? I'm not clear on why it's referring to x86. Am |
| 33 |
>> I configured wrong? Is there a work-around? |
| 34 |
>> |
| 35 |
>> My CPU is: |
| 36 |
>> |
| 37 |
>> /$ uname -p// |
| 38 |
>> //Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz/ |
| 39 |
>> |
| 40 |
>> $ uname -m |
| 41 |
>> x86_64 |
| 42 |
>> |
| 43 |
>> |
| 44 |
> |
| 45 |
> |
| 46 |
> This seems to be the key, |
| 47 |
> |
| 48 |
> /Your CPU doesn't support the required SSE2 instruction. |
| 49 |
> |
| 50 |
> Either your CPU doesn't support that or you have not enabled it or |
| 51 |
> disabled it for some reason. This is where cpuid2cpuflags comes in |
| 52 |
> handy. If you can't tell what is going on still, post *emerge --info |
| 53 |
> *for that package and also the command you used that resulted in that |
| 54 |
> error. That will likely show the USE flags and give the rest of us |
| 55 |
> more clues to work with. |
| 56 |
> |
| 57 |
> Dale |
| 58 |
> |
| 59 |
> :-) :-) |
| 60 |
> / |
| 61 |
|
| 62 |
|
| 63 |
Would that be different than the info output I sent in the original posting? |
Archives