| 1 |
Hello, |
| 2 |
|
| 3 |
First a small note about my upgrade from 3.4.6 to 4.1.1 |
| 4 |
emerge -e system failed during the merging of sandbox |
| 5 |
reading logs it seems that it was trying to use the cross-i686i-... |
| 6 |
compiler that was on my system (at least, unmerging it solved my problem) |
| 7 |
|
| 8 |
so if you have it (cross-i686-...) installed, and because you will have |
| 9 |
to re-merge it later, maybe it is safer to remove it before the system |
| 10 |
update. |
| 11 |
|
| 12 |
|
| 13 |
Second a small (and possibly stupid) question. |
| 14 |
can you use --resume in a -e emerge (after having unmerged something else) ? |
| 15 |
|
| 16 |
|
| 17 |
Third, |
| 18 |
in fact because the emerge -e system, emerge -e world implies building |
| 19 |
system twice, I usually (gcc-3.3->3.4, and now) do something like this : |
| 20 |
|
| 21 |
(this is simplified as it requires proper sed'ing) |
| 22 |
|
| 23 |
emerge -pe system >system.merge |
| 24 |
emerge -pe world >world.merge |
| 25 |
grep -v -f system.merge world.merge > nosystem.merge |
| 26 |
|
| 27 |
emerge -e system |
| 28 |
|
| 29 |
cat nosystem.merge |xargs emerge -1 |
| 30 |
|
| 31 |
does anyone see something potentially wrong with this ? |
| 32 |
|
| 33 |
|
| 34 |
Pascal |
| 35 |
-- |
| 36 |
gentoo-amd64@g.o mailing list |
Archives