Re: emerge --keep-going didn't continue (Re: [gentoo-user] net-libs/nodejs)

[Jack]

On 2022.07.06 19:34, k...@aspodata.se wrote:

tastytea:
> On 2022-07-07 00:19+0200 k...@aspodata.se wrote:
...
> > 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.

Just tried that, emerge world and then killing g++ once the build for
nodejs started and "nodejs" failed, but emerge didn't continue with
the next one (using --keep-going), so why is nodejs blocking  
everything

else ???

So I removed firefox from world, now the rest is building. I'll solve
the firefox/nodejs thing later.

Regards,
/Karl Hammar


I think you might also want to use --skip-first, which should then also  
skip firefox due to the missing dependency.  You could also use  
--exclude firefox, to save editing your world file.

emerge --keep-going didn't continue (Re: [gentoo-user] net-libs/nodejs)

[karl]

tastytea:
> On 2022-07-07 00:19+0200 k...@aspodata.se wrote:
...
> > 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.

Just tried that, emerge world and then killing g++ once the build for
nodejs started and "nodejs" failed, but emerge didn't continue with
the next one (using --keep-going), so why is nodejs blocking everything 
else ???

So I removed firefox from world, now the rest is building. I'll solve
the firefox/nodejs thing later.

Regards,
/Karl Hammar

Re: [gentoo-user] net-libs/nodejs

[tastytea]

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

¹ 
² 

[gentoo-user] net-libs/nodejs

[karl]

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.

///

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 ?

Regards,
/Karl Hammar

Re: [gentoo-user] continuing an emerge

[karl]

Neil Bothwick:
> On Wed,  6 Jul 2022 15:48:04 +0200 (CEST), k...@aspodata.se wrote:
...
> > so, instead of redoing the whole compile, can I, after reducing
> > current memory usage, set up emerge to retry the linking and
> > continue from there ?
> 
> ebuild /path/to/ebuild merge

Thanks, that did what I asked about.

Regards,
/Karl Hammar

Re: [gentoo-user] bundler-2.1.4 failing to emerge

[Matt Connell]

On Wed, 2022-07-06 at 11:50 -0600, the...@sys-concept.com wrote:
> I'm updating my system, but it is stopping on dev-ruby/bundler-2.1.4
> 
> According rebuild, below it shouldn't be related to new "python"
> 
> [ebuild   R   ] dev-ruby/bundler-2.1.4  USE="doc -test" RUBY_TARGETS="ruby27 
> -ruby26*"

I had this as well.  I had to manually use "eselect ruby" to choose
ruby27 in order to proceed.

Re: [gentoo-user] bundler-2.1.4 failing to emerge

[thelma]

Thelma
On 7/6/22 11:50, the...@sys-concept.com wrote:

I'm updating my system, but it is stopping on dev-ruby/bundler-2.1.4

According rebuild, below it shouldn't be related to new "python"

[ebuild   R   ] dev-ruby/bundler-2.1.4  USE="doc -test" RUBY_TARGETS="ruby27 
-ruby26*"

--message
ERROR: compile
ERROR: dev-ruby/bundler-2.1.4::gentoo failed (compile phase):
   failed to (re)build documentation

Call stack:
     ebuild.sh, line  127:  Called src_compile
   environment, line 2182:  Called ruby-ng_src_compile
   environment, line 1782:  Called _ruby_invoke_environment 'all' 
'all_ruby_compile'
   environment, line  618:  Called all_ruby_compile
   environment, line  727:  Called all_fakegem_compile
   environment, line  688:  Called die
The specific snippet of code:
   rdoc ${RUBY_FAKEGEM_DOC_SOURCES} || die "failed to (re)build 
documentation";

If you need support, post the output of `emerge --info 
'=dev-ruby/bundler-2.1.4::gentoo'`,
the complete build log and the output of `emerge -pqv 
'=dev-ruby/bundler-2.1.4::gentoo'`.
The complete build log is located at 
'/var/tmp/portage/dev-ruby/bundler-2.1.4/temp/build.log'.
The ebuild environment file is located at 
'/var/tmp/portage/dev-ruby/bundler-2.1.4/temp/environment'.
Working directory: 
'/var/tmp/portage/dev-ruby/bundler-2.1.4/work/all/bundler-2.1.4'
S: '/var/tmp/portage/dev-ruby/bundler-2.1.4/work/all/bundler-2.1.4'


I think it is a bug in recent version of rubby, "documentation doesn't exist or has 
a wrong link"
Removing "doc" flag solve the problem:

=dev-ruby/bundler-2.1.4 -doc
 

[gentoo-user] bundler-2.1.4 failing to emerge

[thelma]

I'm updating my system, but it is stopping on dev-ruby/bundler-2.1.4

According rebuild, below it shouldn't be related to new "python"

[ebuild   R   ] dev-ruby/bundler-2.1.4  USE="doc -test" RUBY_TARGETS="ruby27 
-ruby26*"

--message
ERROR: compile
ERROR: dev-ruby/bundler-2.1.4::gentoo failed (compile phase):
  failed to (re)build documentation

Call stack:
ebuild.sh, line  127:  Called src_compile
  environment, line 2182:  Called ruby-ng_src_compile
  environment, line 1782:  Called _ruby_invoke_environment 'all' 
'all_ruby_compile'
  environment, line  618:  Called all_ruby_compile
  environment, line  727:  Called all_fakegem_compile
  environment, line  688:  Called die
The specific snippet of code:
  rdoc ${RUBY_FAKEGEM_DOC_SOURCES} || die "failed to (re)build 
documentation";

If you need support, post the output of `emerge --info 
'=dev-ruby/bundler-2.1.4::gentoo'`,
the complete build log and the output of `emerge -pqv 
'=dev-ruby/bundler-2.1.4::gentoo'`.
The complete build log is located at 
'/var/tmp/portage/dev-ruby/bundler-2.1.4/temp/build.log'.
The ebuild environment file is located at 
'/var/tmp/portage/dev-ruby/bundler-2.1.4/temp/environment'.
Working directory: 
'/var/tmp/portage/dev-ruby/bundler-2.1.4/work/all/bundler-2.1.4'
S: '/var/tmp/portage/dev-ruby/bundler-2.1.4/work/all/bundler-2.1.4'

--
Thelma

Re: [gentoo-user] continuing an emerge

[Neil Bothwick]

On Wed,  6 Jul 2022 15:48:04 +0200 (CEST), k...@aspodata.se wrote:

> With nodejs, I get:
> 
> /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
> 
> so, instead of redoing the whole compile, can I, after reducing
> current memory usage, set up emerge to retry the linking and
> continue from there ?

ebuild /path/to/ebuild merge

should do it.


-- 
Neil Bothwick

In the 60's people took acid to make the world weird.
Now the world is weird and people take Prozac to make it normal.


pgpzjgBf8bOSj.pgp
Description: OpenPGP digital signature

Re: [gentoo-user] continuing an emerge

[w...@op.pl]

Dnia 2022-07-06, o godz. 15:48:04
k...@aspodata.se napisał(a):

>  Is it possible to continue a failed emerge ?
> 
> ///
> 
> With nodejs, I get:
> 
> /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
> 
> so, instead of redoing the whole compile, can I, after reducing
> current memory usage, set up emerge to retry the linking and
> continue from there ?
> 
> Regards,
> /Karl Hammar
> 
> 
> 

There is emerge --resume command. However it starts from scratch with
the not-yet-merged packages as far as I can tell

-- 
xWK


pgpx6CUxBYQWy.pgp
Description: Podpis cyfrowy OpenPGP

[gentoo-user] continuing an emerge

[karl]

 Is it possible to continue a failed emerge ?

///

With nodejs, I get:

/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

so, instead of redoing the whole compile, can I, after reducing
current memory usage, set up emerge to retry the linking and
continue from there ?

Regards,
/Karl Hammar