1 |
Well no, but I did this change before doing the actual bootstrap. I |
2 |
followed the quick install guide and made changes to make.conf, then |
3 |
completed bootstrap.sh and started emerging the system. Thats when it |
4 |
happend. As there is a stage-installed perl version, when the library |
5 |
tried to compile, it used the present perl version as it was dependent |
6 |
on it. However, as the stage-installed version did'nt work with my |
7 |
changes, i had to manually upgrade perl before i could emerge the rest |
8 |
of the system. I'm sure other people will have the same problem and to |
9 |
solve this, one way would be to reinstall perl somewhere in the very |
10 |
beguinning of emerge system. |
11 |
|
12 |
I'm just a stupid user trying to make life easier for others :). |
13 |
|
14 |
Thanks, George. |
15 |
|
16 |
On 5/11/06, Jan Kundrát <jkt@g.o> wrote: |
17 |
> George Hedfors wrote: |
18 |
> > I've found out several times that I have to recompile perl manually |
19 |
> > during the "emerge -e system" process due to some error becouse perl |
20 |
> > was unable to locate the proper gcc. |
21 |
> |
22 |
> Have you read our GCC Update Guide [1]? |
23 |
> |
24 |
> > During the installation I change the CHOST in /etc/make.conf, which |
25 |
> > then changes the location of gcc according to gcc-config, but after |
26 |
> > this, perl has to be reinstalled for it to be able to compile modules |
27 |
> > properly. |
28 |
> |
29 |
> Changing CHOST is a bit tricky. Setting it in /etc/make.conf is not |
30 |
> enough. You have to use the /usr/portage/scripts/bootstrap.sh script. |
31 |
> |
32 |
> Anyway, how is this related to the documentation? :) |
33 |
> |
34 |
> [1] http://www.gentoo.org/doc/en/gcc-upgrading.xml |
35 |
> |
36 |
> Cheers, |
37 |
> -jkt |
38 |
> |
39 |
> -- |
40 |
> cd /local/pub && more beer > /dev/mouth |
41 |
> |
42 |
> |
43 |
> |
44 |
|
45 |
|
46 |
-- |
47 |
PGP Fingerprint: |
48 |
4BB9 7A99 3DB5 52AA 8CEF 4DFB 32F2 41AC 0EF2 D595 |
49 |
|
50 |
-- |
51 |
gentoo-doc@g.o mailing list |