Archives
Archives
| From: | karl@××××××××.se | ||
|---|---|---|---|
| To: | gentoo-user@l.g.o | ||
| Subject: | Re: [gentoo-user] emerge failure for dev-lang/R-4.0.4 | ||
| Date: | Sun, 04 Apr 2021 22:45:26 | ||
| Message-Id: | 20210404224454.AA0B48246B5B@turkos.aspodata.se | ||
| In Reply to: | Re: [gentoo-user] emerge failure for dev-lang/R-4.0.4 by Michael Orlitzky |
||
| 1 | Michael: |
| 2 | > On Sat, 2021-04-03 at 13:15 +0200, karl@××××××××.se wrote: |
| 3 | > > Is there a way to run emerge step by step to find out why it fails ? |
| 4 | > > |
| 5 | > |
| 6 | > No easy way. You can `cp -a` the source/build directories out of |
| 7 | > /var/tmp/portage and then re-run `make -j<whatever>`. That should re- |
| 8 | > start the build more or less where it failed. |
| 9 | |
| 10 | $ cp -a ... |
| 11 | $ cd ... |
| 12 | $ make -j1 |
| 13 | ... |
| 14 | $ echo $? |
| 15 | 0 |
| 16 | |
| 17 | It builds without failure in that case. |
| 18 | |
| 19 | Regards, |
| 20 | /Karl Hammar |
| Subject | Author |
|---|---|
| Re: [gentoo-user] emerge failure for dev-lang/R-4.0.4 | Michael Orlitzky <mjo@g.o> |