| 1 |
On 2018.12.04 14:13, Neil Bothwick wrote: |
| 2 |
> On Tue, 04 Dec 2018 13:42:16 -0500, Jack wrote: |
| 3 |
> |
| 4 |
>>> Given I've spent more than two days compiling to get nowhere with |
| 5 |
>>> this, I'm thinking: |
| 6 |
>> One thing I've done in the past if something failed after a long |
| 7 |
>> time compiling is to cd to the top build dir (under the Portage tmp |
| 8 |
>> dir) and just continue the compile (either make or ninja, or |
| 9 |
>> whatever that package uses) when/if that finishes, you can use |
| 10 |
>> ebuild to finish the install and qmerge steps. That avoids needing |
| 11 |
>> to start the compile from the beginning. |
| 12 |
> You can use ebuild for that too, with the compile option. I've have |
| 13 |
> the chromium build fail for apparently random reasons on my laptop |
| 14 |
> from time to time and ebuild ... compile finishes the process. |
| 15 |
|
| 16 |
Unless I'm mistaken, "ebuild /path/to/ebuild compile" does avoid |
| 17 |
redoing the unpack, prepare, and configure steps, but it starts the |
| 18 |
compile from scratch. Manually doing "make" (or whatever) in the |
| 19 |
appropriate directory avoids repeating those parts of the compile that |
| 20 |
were successful. If the compile takes two days, that's a significant |
| 21 |
savings in time. |
| 22 |
|
| 23 |
Jack |
Archives