| 1 |
chek that email i sent ya |
| 2 |
|
| 3 |
On 9/1/06, Pascal BERTIN <pascal.bertin@×××××××.com> wrote: |
| 4 |
> |
| 5 |
> Hello, |
| 6 |
> |
| 7 |
> First a small note about my upgrade from 3.4.6 to 4.1.1 |
| 8 |
> emerge -e system failed during the merging of sandbox |
| 9 |
> reading logs it seems that it was trying to use the cross-i686i-... |
| 10 |
> compiler that was on my system (at least, unmerging it solved my problem) |
| 11 |
> |
| 12 |
> so if you have it (cross-i686-...) installed, and because you will have |
| 13 |
> to re-merge it later, maybe it is safer to remove it before the system |
| 14 |
> update. |
| 15 |
> |
| 16 |
> |
| 17 |
> Second a small (and possibly stupid) question. |
| 18 |
> can you use --resume in a -e emerge (after having unmerged something else) |
| 19 |
> ? |
| 20 |
> |
| 21 |
> |
| 22 |
> Third, |
| 23 |
> in fact because the emerge -e system, emerge -e world implies building |
| 24 |
> system twice, I usually (gcc-3.3->3.4, and now) do something like this : |
| 25 |
> |
| 26 |
> (this is simplified as it requires proper sed'ing) |
| 27 |
> |
| 28 |
> emerge -pe system >system.merge |
| 29 |
> emerge -pe world >world.merge |
| 30 |
> grep -v -f system.merge world.merge > nosystem.merge |
| 31 |
> |
| 32 |
> emerge -e system |
| 33 |
> |
| 34 |
> cat nosystem.merge |xargs emerge -1 |
| 35 |
> |
| 36 |
> does anyone see something potentially wrong with this ? |
| 37 |
> |
| 38 |
> |
| 39 |
> Pascal |
| 40 |
> -- |
| 41 |
> gentoo-amd64@g.o mailing list |
| 42 |
> |
| 43 |
> |
| 44 |
|
| 45 |
|
| 46 |
-- |
| 47 |
Karma, It's Real! |
| 48 |
"No penguins were harmed during the writing, just a bunch of broken windows |
| 49 |
to let them escape..."-xtacocorex |
Archives