1 |
n952162 wrote: |
2 |
> On 2020-10-11 22:23, Dale wrote: |
3 |
>> n952162 wrote: |
4 |
>>> |
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 |
>> |
47 |
>> This seems to be the key, |
48 |
>> |
49 |
>> /Your CPU doesn't support the required SSE2 instruction. |
50 |
>> |
51 |
>> Either your CPU doesn't support that or you have not enabled it or |
52 |
>> disabled it for some reason. This is where cpuid2cpuflags comes in |
53 |
>> handy. If you can't tell what is going on still, post *emerge --info |
54 |
>> *for that package and also the command you used that resulted in that |
55 |
>> error. That will likely show the USE flags and give the rest of us |
56 |
>> more clues to work with. |
57 |
>> |
58 |
>> Dale |
59 |
>> |
60 |
>> :-) :-) |
61 |
>> / |
62 |
> |
63 |
> |
64 |
> Would that be different than the info output I sent in the original |
65 |
> posting? |
66 |
> |
67 |
> |
68 |
|
69 |
|
70 |
What might help, the listing of USE flags for that package. emerge -uvp |
71 |
/net-libs/nodejs should list the USE flags and how they are set. From |
72 |
the error, either something is set wrong for your CPU or SSE2 is |
73 |
disabled or something somewhere. It's where I'd start figuring out the |
74 |
problem. Either way, it needs to recognize your CPU and it's |
75 |
instruction sets properly. |
76 |
|
77 |
Someone else may have a better idea or ran into this and know the most |
78 |
likely cause. |
79 |
|
80 |
Dale |
81 |
|
82 |
:-) :-) |
83 |
/ |