1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
Bjarke Istrup Pedersen wrote: |
5 |
> I must say I have been wondering about this for a while too. |
6 |
> A solution might be add some sort of flag to packages that are binary, |
7 |
> and then let portage install libstdc++ the first time you install this |
8 |
> kind of package. |
9 |
> |
10 |
|
11 |
This does not solve the following problem: |
12 |
1. user upgrades to gcc-3.4.x |
13 |
2. gcc-config to 3.4.x |
14 |
3. emerge -P gcc |
15 |
|
16 |
Because libstdc++ has a different name (.6) in 3.4.x than the .5 in |
17 |
3.3.X all the packages linked against the old one are borked and this |
18 |
includes python meaning that emerge does not work until you for example |
19 |
make a symlink from the .6 to .5. I recently run into this when |
20 |
reinstalling my desktop after a broken hard drive. |
21 |
|
22 |
Regards, |
23 |
Petteri Räty (Betelgeuse) |
24 |
-----BEGIN PGP SIGNATURE----- |
25 |
Version: GnuPG v1.4.2 (GNU/Linux) |
26 |
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org |
27 |
|
28 |
iD8DBQFDEHpTcxLzpIGCsLQRAoOLAJwPpe3od7YvvqpQQkFE5zKbvEQgQQCdG7KG |
29 |
f07PYC8yAD+EJuBzyjT7cX8= |
30 |
=Trg6 |
31 |
-----END PGP SIGNATURE----- |
32 |
-- |
33 |
gentoo-dev@g.o mailing list |