On 2022-07-07 00:19+0200 k...@aspodata.se wrote: > Unfortunately it seems I cannon emerge nodejs due > to this error: > > /usr/lib/gcc/x86_64-pc-linux-gnu/10.2.0/../../../../ > x86_64-pc-linux-gnu/bin/ld: > failed to set dynamic section sizes: memory exhausted > > I tried to stop every process except gettys and the login, > still the same, no MAKEOPTS (i.e. no paralell builds) and > EMERGE_DEFAULT_OPTS="--jobs 1 ... > > The emerge line is: > > [ebuild U ] net-libs/nodejs-18.3.0 [14.19.0] > USE="debug icu npm snapshot ssl system-icu system-ssl > -doc* -inspector -lto -pax-kernel -systemtap -test" > CPU_FLAGS_X86="sse2" > > Would dropping some use flags help ? > I'm generally not interested in nodejs as such, > it's just that firefox depends on it.
I'm not familiar with nodejs in particular, but dropping the debug USE-flag will probably reduce the amount of memory it needs somewhat. You could also add more swap, or look into zswap¹ or zram². > When emergings with --skipfirst (i.e. skip nodejs), > I get: > emerge: It seems we have nothing to resume... > > Checking dependancies: > # emerge -vc net-libs/nodejs > > Calculating dependencies .... done! > net-libs/nodejs-14.19.0 pulled in by: > www-client/firefox-91.9.0 requires >=net-libs/nodejs-10.23.1 > > So, why don't emerge build the other 100'ish packages ? > Last time I did emerge nodejs, must I run emerge @world > and let that fail first ? Yes, --resume will always try to resume the last command that failed, as far as i know. > Regards, > /Karl Hammar Regards, tastytea ¹ <https://wiki.gentoo.org/wiki/Zswap> ² <https://wiki.gentoo.org/wiki/Zram>
