1. Forum
  2. Usenet
  3. LINUX.GENTOO.USER

  • Re: [gentoo-user] continuing an emerge

    From Neil Bothwick@21:1/5 to karl@aspodata.se on Wed Jul 6 16:10:01 2022
    On Wed, 6 Jul 2022 15:48:04 +0200 (CEST), karl@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.

    -----BEGIN PGP SIGNATURE-----

    iQIzBAEBCAAdFiEE8k9T/rX16EJxEKG692eFu0QSMJgFAmLFlpkACgkQ92eFu0QS MJibzg//aVQs5fS961ki0tYezNW/2QBqqRQPridSkZoeKfJnG20LItuQQHQDm1FU e9XhyqksOzcjgXaAkJ6oZs7G9tqt8dmuYGRfl4gIamXdrIWpF58m4yzfUbBHj5mS 2IXhvHRNrUleRyPdQJe+7EdUZgrp1ooU0G0JskX1zzAePUw3VsaLNZXTCEpq5IAY y9JBYkPFG51H1bbWN1wTzTOt9dbKnMYZcd4H2VIwHYLhS96SK4cG0CA6yvl2w9BE yYevqmxrlgPb+4hHEPxmRljlmXRfP+XdI+sD+/+093vPZoTSPdlx0mabUp4IQ0JU tlT6g8CcTX+DyAK8wk+p3nadrEIsKra7p6e7pGE07vmz1AVJeOcY0JsLMO70xU4q mz8Fd10daZukVmLYPfnTijUMbJNUxdSnXgUx69ixMO1vc7HimEIZ9IF/vThvCFi7 oGQMd5WUDlUnWqpMLbhieqR+h0EvqF7WqtBXzgdVvN+RaBeCDslBhsgqkhIJrp8S SiOD4z4kYN6QdU1ezd6fL7VmLXjF9xlw1Jg+DVNRzBur+LCtI2VX5XuOtJZsZmtr Wm9bnhZsoDF1rchouS45IUOc7oPCxiXxqO3+asJj153sSegz02mPQWVx9o7sE5Zk JBu7ayseckzVoavHSqHTXb3fNKYdnEB8U/pAV1knVrpIMgWC2CM=
    =sUFb
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    *
  • From wkuz@op.pl@21:1/5 to All on Wed Jul 6 16:00:01 2022
    Dnia 2022-07-06, o godz. 15:48:04
    karl@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

    -----BEGIN PGP SIGNATURE-----

    iHUEAREIAB0WIQQDlhT0eXq9QZcYNDCwxtjiG5GR4gUCYsWUmAAKCRCwxtjiG5GR 4kbnAQCmcJCXgMpueHZYJg58Y9ZLTbjOS7bTB9PVvQu/90FPZwEAyNTX7ntvzahk NTncg01FnywC/2yR7ejZFSscDat3y/s=
    =zyYr
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From karl@aspodata.se@21:1/5 to All on Wed Jul 6 15:50:01 2022
    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

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From karl@aspodata.se@21:1/5 to All on Thu Jul 7 00:30:01 2022
    Neil Bothwick:
    On Wed, 6 Jul 2022 15:48:04 +0200 (CEST), karl@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

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)