1 |
Unfortunately it seems I cannon emerge nodejs due |
2 |
to this error: |
3 |
|
4 |
/usr/lib/gcc/x86_64-pc-linux-gnu/10.2.0/../../../../ |
5 |
x86_64-pc-linux-gnu/bin/ld: |
6 |
failed to set dynamic section sizes: memory exhausted |
7 |
|
8 |
I tried to stop every process except gettys and the login, |
9 |
still the same, no MAKEOPTS (i.e. no paralell builds) and |
10 |
EMERGE_DEFAULT_OPTS="--jobs 1 ... |
11 |
|
12 |
The emerge line is: |
13 |
|
14 |
[ebuild U ] net-libs/nodejs-18.3.0 [14.19.0] |
15 |
USE="debug icu npm snapshot ssl system-icu system-ssl |
16 |
-doc* -inspector -lto -pax-kernel -systemtap -test" |
17 |
CPU_FLAGS_X86="sse2" |
18 |
|
19 |
Would dropping some use flags help ? |
20 |
I'm generally not interested in nodejs as such, |
21 |
it's just that firefox depends on it. |
22 |
|
23 |
/// |
24 |
|
25 |
When emergings with --skipfirst (i.e. skip nodejs), |
26 |
I get: |
27 |
emerge: It seems we have nothing to resume... |
28 |
|
29 |
Checking dependancies: |
30 |
# emerge -vc net-libs/nodejs |
31 |
|
32 |
Calculating dependencies .... done! |
33 |
net-libs/nodejs-14.19.0 pulled in by: |
34 |
www-client/firefox-91.9.0 requires >=net-libs/nodejs-10.23.1 |
35 |
|
36 |
So, why don't emerge build the other 100'ish packages ? |
37 |
Last time I did emerge nodejs, must I run emerge @world |
38 |
and let that fail first ? |
39 |
|
40 |
Regards, |
41 |
/Karl Hammar |