| 1 |
I have found a script called emwrap.sh The forum thread attached to that |
| 2 |
script makes it clear it is important to compile the few core TC files twice |
| 3 |
before emerge -e system. Then do that twice. Then emerce -e world. Wow. |
| 4 |
The script is supposed to shorten the overall time, by not recompiling TC |
| 5 |
and system when compiling the rest of the world. It seems logical. |
| 6 |
|
| 7 |
I also found some inconsistencies in my USE flags, so it's back to square |
| 8 |
one. I hope this works. (I am trying the script). |
| 9 |
|
| 10 |
Thank you very much. |
| 11 |
|
| 12 |
Alan |
| 13 |
|
| 14 |
On Tue, Jul 29, 2008 at 2:39 AM, Volker Armin Hemmann < |
| 15 |
volker.armin.hemmann@××××××××××××.de> wrote: |
| 16 |
|
| 17 |
> On Montag, 28. Juli 2008, Alan E. Davis wrote: |
| 18 |
> > On Mon, Jul 28, 2008 at 4:55 PM, Volker Armin Hemmann < |
| 19 |
> > |
| 20 |
> > volker.armin.hemmann@××××××××××××.de> wrote: |
| 21 |
> > > On Montag, 28. Juli 2008, Andrey Falko wrote: |
| 22 |
> > > > To eliminate the first factor do: emerge -e world. |
| 23 |
> > > |
| 24 |
> > > no. Just no. |
| 25 |
> > |
| 26 |
> > For what it's worth, I started emerge -e system quite some time ago. It |
| 27 |
> > stops about 1/2 way through on glib. Apparently this is common. I |
| 28 |
> > started it up again as "emerge -e system --skipfirst". How bad of an |
| 29 |
> idea |
| 30 |
> > was that? I think about 200 out of about 350 pkgs have been rebuilt. |
| 31 |
> > |
| 32 |
> > I'll halt this and rebuild dbus again. Etc/ |
| 33 |
> > |
| 34 |
> > > > The second |
| 35 |
> > > > factor can be eliminated by downgrading to firefox2. If it is a |
| 36 |
> > > > firefox3 problem then the bug report would go to firefox developers. |
| 37 |
> > |
| 38 |
> > It does affect firefox 2 also. All users except root. All gecko |
| 39 |
> browsers, |
| 40 |
> > I guess (all firefox, and epiphany---didnt' try galeon). |
| 41 |
> > |
| 42 |
> > > just re-emerge dbus and/or revdep-rebuilt should be enough. Or that |
| 43 |
> > > 'preserved-libs' stuff. |
| 44 |
> > |
| 45 |
> > I don't qet it about preserved-libs. THerefore I haven't done anything |
| 46 |
> > about any of the messages. I don't understand the messages, exactly what |
| 47 |
> > would happen? Would I be building the same app with the same old lib or |
| 48 |
> > with the new lib? I need to find something in the docs, but haven't seen |
| 49 |
> > anything yet. |
| 50 |
> |
| 51 |
> http://r0bertz.blogspot.com/2008/06/portage-22-preserve-libs-features.html |
| 52 |
> |
| 53 |
> the problem with it (a friend run into it - maybe the have fixed it in the |
| 54 |
> meantime)if you do an emerge -e system/world while the old stuff is still |
| 55 |
> there, some apps and libs will link against the old stuff. Thus the whole |
| 56 |
> exercise will be a waste of time and energy. |
| 57 |
> |
| 58 |
> |
| 59 |
|
| 60 |
|
| 61 |
-- |
| 62 |
Alan Davis |
| 63 |
|
| 64 |
"It's never a matter of liking or disliking ..." |
| 65 |
---Santa Ynez Chumash Medicine Man |
Archives