On Tuesday, 4 December 2018 20:57:11 GMT Neil Bothwick wrote: > On Tue, 04 Dec 2018 14:23:27 -0500, Jack wrote: > > On 2018.12.04 14:13, Neil Bothwick wrote: > > >> One thing I've done in the past if something failed after a long > > >> time compiling is to cd to the top build dir (under the Portage tmp > > >> dir) and just continue the compile (either make or ninja, or > > >> whatever that package uses) when/if that finishes, you can use > > >> ebuild to finish the install and qmerge steps. That avoids needing > > >> to start the compile from the beginning. > > > > > > You can use ebuild for that too, with the compile option. I've have > > > the chromium build fail for apparently random reasons on my laptop > > > from time to time and ebuild ... compile finishes the process. > > > > Unless I'm mistaken, "ebuild /path/to/ebuild compile" does avoid > > redoing the unpack, prepare, and configure steps, but it starts the > > compile from scratch. Manually doing "make" (or whatever) in the > > appropriate directory avoids repeating those parts of the compile that > > were successful. If the compile takes two days, that's a significant > > savings in time. > > It starts the compile by running make or whatever is appropriate for the > build, so it doesn't need to build anything already built any more than a > bare make does. But using ebuild compile means you get the same > environment as when you started the compile.
Which will be counterproductive if the reason the compile failed is because RAM was exhausted and you need to reduce the job number. Could I define MAKEOPTS on the CLI when running ebuild by hand? -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
