1 |
Hello, |
2 |
|
3 |
I think You could try: |
4 |
1) change cflags in make.conf |
5 |
2) bootstrap.sh |
6 |
3) emerge -e system |
7 |
4) emerge -e world |
8 |
|
9 |
In other words this is how to build a system from stage 1. |
10 |
|
11 |
On Tue, Nov 16, 2010 at 12:06 PM, Helmut Jarausch < |
12 |
jarausch@××××××××××××××××.de> wrote: |
13 |
|
14 |
> On 11/16/10 10:56:29, Alan McKinnon wrote: |
15 |
> > |
16 |
> > Backup your portage related data and re-install. |
17 |
> > |
18 |
> > Seriously - you know you are looking at doing emerge -e world and |
19 |
> > will |
20 |
> > need to |
21 |
> > fiddle stuff to make it complete successfully. |
22 |
> > |
23 |
> > If you just reinstall, put your old world file and /etc/portage/ back |
24 |
> > then let |
25 |
> > portage have at it, that is exactly what will happen. You'll have |
26 |
> > 30-45 |
27 |
> > minutes of setup work and a high level of confidence it will complete |
28 |
> > successfully. |
29 |
> > |
30 |
> > Trying to fix the existing installation is potentially many hours of |
31 |
> > poking |
32 |
> > around to see what changed, potentially several goes at running |
33 |
> > emerge |
34 |
> > -e |
35 |
> > world, hair pulling, and you will probably give up and just reinstall |
36 |
> > anyway. |
37 |
> > |
38 |
> > I'm assuming you are looking for the easiest, fastest route to |
39 |
> > success |
40 |
> > with |
41 |
> > the least pain, and that your days of poking into portage to see how |
42 |
> > things |
43 |
> > work for fun are long over. |
44 |
> > |
45 |
> |
46 |
> Thanks Alan, |
47 |
> |
48 |
> just one more question: where are information like the |
49 |
> current eselect(ions) stored? |
50 |
> |
51 |
> Helmut. |
52 |
> |
53 |
> |
54 |
|
55 |
|
56 |
-- |
57 |
mv |