Gentoo Archives: gentoo-user

From: Dale <rdalek1967@×××××.com>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] What happened to my emerge -u?
Date: Sun, 11 Oct 2020 22:16:57
Message-Id: 56b28d8d-1d70-e291-fe8b-6309c51662a8@gmail.com
In Reply to: Re: [gentoo-user] What happened to my emerge -u? by n952162
1 n952162 wrote:
2 >
3 > On 2020-10-11 22:57, Dale wrote:
4 >> n952162 wrote:
5 >>> On 2020-10-11 22:23, Dale wrote:
6 >>>> n952162 wrote:
7 >>>>> Apparently after a long series of checks, my emerge simply ended.
8 >>>>> The only hint of a problem was this message:
9 >>>>>
10 >>>>> />>> Running pre-merge checks for net-libs/nodejs-14.4.0//
11 >>>>> // * ERROR: net-libs/nodejs-14.4.0::gentoo failed (pretend phase)://
12 >>>>> // *   Your CPU doesn't support the required SSE2 instruction.//
13 >>>>> // * //
14 >>>>> // * Call stack://
15 >>>>> // *              ebuild.sh, line 124:  Called pkg_pretend//
16 >>>>> // *   nodejs-14.4.0.ebuild, line  50:  Called die//
17 >>>>> // * The specific snippet of code://
18 >>>>> // *      (use x86 && ! use cpu_flags_x86_sse2) && \//
19 >>>>> // *              die "Your CPU doesn't support the required SSE2
20 >>>>> instruction."//
21 >>>>> // * //
22 >>>>> // * If you need support, post the output of `emerge --info
23 >>>>> '=net-libs/nodejs-14.4.0::gentoo'`,//
24 >>>>> // * the complete build log and the output of `emerge -pqv
25 >>>>> '=net-libs/nodejs-14.4.0::gentoo'`.//
26 >>>>> // * The complete build log is located at
27 >>>>> '/var/tmp/portage/net-libs/nodejs-14.4.0/temp/build.log'.//
28 >>>>> // * The ebuild environment file is located at
29 >>>>> '/var/tmp/portage/net-libs/nodejs-14.4.0/temp/die.env'.//
30 >>>>> // * Working directory:
31 >>>>> '/var/tmp/portage/net-libs/nodejs-14.4.0/homedir'//
32 >>>>> // * S: '/var/tmp/portage/net-libs/nodejs-14.4.0/work/node-v14.4.0'/
33 >>>>>
34 >>>>>
35 >>>>> Is this the problem?  I'm not clear on why it's referring to x86.
36 >>>>> Am I configured wrong?  Is there a work-around?
37 >>>>>
38 >>>>> My CPU is:
39 >>>>>
40 >>>>> /$ uname -p//
41 >>>>> //Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz/
42 >>>>>
43 >>>>> $ uname -m
44 >>>>> x86_64
45 >>>>>
46 >>>>>
47 >>>>
48 >>>> This seems to be the key,
49 >>>>
50 >>>> /Your CPU doesn't support the required SSE2 instruction.
51 >>>>
52 >>>> Either your CPU doesn't support that or you have not enabled it or
53 >>>> disabled it for some reason.  This is where cpuid2cpuflags comes in
54 >>>> handy.  If you can't tell what is going on still, post *emerge --info
55 >>>> *for that package and also the command you used that resulted in that
56 >>>> error.  That will likely show the USE flags and give the rest of us
57 >>>> more clues to work with.
58 >>>>
59 >>>> Dale
60 >>>>
61 >>>> :-)  :-)
62 >>>> /
63 >>>
64 >>> Would that be different than the info output I sent in the original
65 >>> posting?
66 >>>
67 >>>
68 >>
69 >> What might help, the listing of USE flags for that package.  emerge -uvp
70 >> /net-libs/nodejs should list the USE flags and how they are set.  From
71 >> the error, either something is set wrong for your CPU or SSE2 is
72 >> disabled or something somewhere.  It's where I'd start figuring out the
73 >> problem.  Either way, it needs to recognize your CPU and it's
74 >> instruction sets properly.
75 >>
76 >> Someone else may have a better idea or ran into this and know the most
77 >> likely cause.
78 >>
79 >> Dale
80 >>
81 >> :-)  :-)
82 >> /
83 >>
84 > $ pwd
85 > /etc/portage/package.use
86 > $ grep node *
87 > $ lf /var/db/pkg/net-libs
88 > gnutls-3.5.19/  http-parser-2.8.1/  libmnl-1.0.4/  libnsl-1.2.0/
89 > libpcap-1.8.1/  libssh2-1.8.0-r1/  libtirpc-1.0.2-r1/
90 >
91 > i.e. it's not currently installed.
92 >
93 > And in make.conf, there's only this:
94 >
95 > USE="-elogind"
96 >
97 >
98 >
99 >
100
101
102 The output of emerge -uvp net-libs/nodejs would be more helpful.  Also
103 emerge --info may help.  There's a setting somewhere that needs to be
104 changed. 
105
106 Dale
107
108 :-)  :-)