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

Replies

Subject Author
Re: [gentoo-user] What happened to my emerge -u? Ashley Dixon <ash@××××××××××.uk>
Re: [gentoo-user] What happened to my emerge -u? n952162 <n952162@×××.de>
Re: [gentoo-user] What happened to my emerge -u? n952162 <n952162@×××.de>