| 1 |
On 2020-10-11 22:57, Dale wrote: |
| 2 |
> n952162 wrote: |
| 3 |
>> On 2020-10-11 22:23, Dale wrote: |
| 4 |
>>> n952162 wrote: |
| 5 |
>>>> Apparently after a long series of checks, my emerge simply ended. |
| 6 |
>>>> The only hint of a problem was this message: |
| 7 |
>>>> |
| 8 |
>>>> />>> Running pre-merge checks for net-libs/nodejs-14.4.0// |
| 9 |
>>>> // * ERROR: net-libs/nodejs-14.4.0::gentoo failed (pretend phase):// |
| 10 |
>>>> // * Your CPU doesn't support the required SSE2 instruction.// |
| 11 |
>>>> // * // |
| 12 |
>>>> // * Call stack:// |
| 13 |
>>>> // * ebuild.sh, line 124: Called pkg_pretend// |
| 14 |
>>>> // * nodejs-14.4.0.ebuild, line 50: Called die// |
| 15 |
>>>> // * The specific snippet of code:// |
| 16 |
>>>> // * (use x86 && ! use cpu_flags_x86_sse2) && \// |
| 17 |
>>>> // * die "Your CPU doesn't support the required SSE2 |
| 18 |
>>>> instruction."// |
| 19 |
>>>> // * // |
| 20 |
>>>> // * If you need support, post the output of `emerge --info |
| 21 |
>>>> '=net-libs/nodejs-14.4.0::gentoo'`,// |
| 22 |
>>>> // * the complete build log and the output of `emerge -pqv |
| 23 |
>>>> '=net-libs/nodejs-14.4.0::gentoo'`.// |
| 24 |
>>>> // * The complete build log is located at |
| 25 |
>>>> '/var/tmp/portage/net-libs/nodejs-14.4.0/temp/build.log'.// |
| 26 |
>>>> // * The ebuild environment file is located at |
| 27 |
>>>> '/var/tmp/portage/net-libs/nodejs-14.4.0/temp/die.env'.// |
| 28 |
>>>> // * Working directory: |
| 29 |
>>>> '/var/tmp/portage/net-libs/nodejs-14.4.0/homedir'// |
| 30 |
>>>> // * S: '/var/tmp/portage/net-libs/nodejs-14.4.0/work/node-v14.4.0'/ |
| 31 |
>>>> |
| 32 |
>>>> |
| 33 |
>>>> Is this the problem? I'm not clear on why it's referring to x86. |
| 34 |
>>>> Am I configured wrong? Is there a work-around? |
| 35 |
>>>> |
| 36 |
>>>> My CPU is: |
| 37 |
>>>> |
| 38 |
>>>> /$ uname -p// |
| 39 |
>>>> //Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz/ |
| 40 |
>>>> |
| 41 |
>>>> $ uname -m |
| 42 |
>>>> x86_64 |
| 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 |
>> Would that be different than the info output I sent in the original |
| 63 |
>> posting? |
| 64 |
>> |
| 65 |
>> |
| 66 |
> |
| 67 |
> What might help, the listing of USE flags for that package. emerge -uvp |
| 68 |
> /net-libs/nodejs should list the USE flags and how they are set. From |
| 69 |
> the error, either something is set wrong for your CPU or SSE2 is |
| 70 |
> disabled or something somewhere. It's where I'd start figuring out the |
| 71 |
> problem. Either way, it needs to recognize your CPU and it's |
| 72 |
> instruction sets properly. |
| 73 |
> |
| 74 |
> Someone else may have a better idea or ran into this and know the most |
| 75 |
> likely cause. |
| 76 |
> |
| 77 |
> Dale |
| 78 |
> |
| 79 |
> :-) :-) |
| 80 |
> / |
| 81 |
> |
| 82 |
$ pwd |
| 83 |
/etc/portage/package.use |
| 84 |
$ grep node * |
| 85 |
$ lf /var/db/pkg/net-libs |
| 86 |
gnutls-3.5.19/ http-parser-2.8.1/ libmnl-1.0.4/ libnsl-1.2.0/ |
| 87 |
libpcap-1.8.1/ libssh2-1.8.0-r1/ libtirpc-1.0.2-r1/ |
| 88 |
|
| 89 |
i.e. it's not currently installed. |
| 90 |
|
| 91 |
And in make.conf, there's only this: |
| 92 |
|
| 93 |
USE="-elogind" |
Archives