| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
I must say I have been wondering about this for a while too. |
| 5 |
A solution might be add some sort of flag to packages that are binary, |
| 6 |
and then let portage install libstdc++ the first time you install this |
| 7 |
kind of package. |
| 8 |
|
| 9 |
Mike Frysinger skrev: |
| 10 |
> On Fri, Aug 26, 2005 at 10:14:04AM +0100, Chris Bainbridge wrote: |
| 11 |
> |
| 12 |
>>Subject says it all - is there any reason why 3.4.4 installs either |
| 13 |
>>gcc-3.3* or libstdc++-v3 built with gcc-3.3? |
| 14 |
> |
| 15 |
> |
| 16 |
> because i got tired of people complaining about broken systems when they |
| 17 |
> emerged gcc-3.4.4 and cleaned out all gcc-3.3.x versions from their system |
| 18 |
> |
| 19 |
> |
| 20 |
>>Is it possible to compile |
| 21 |
>>a native 3.4 system without the old gcc if I don't need binary |
| 22 |
>>compatibility? |
| 23 |
> |
| 24 |
> |
| 25 |
> i just add libstdc++-v3 to my package.provided in /etc/portage/profile/ and |
| 26 |
> call it a day |
| 27 |
> |
| 28 |
> i dont really see there being a clean solution until we have portage support |
| 29 |
> to track ABI dependencies |
| 30 |
> -mike |
| 31 |
|
| 32 |
-----BEGIN PGP SIGNATURE----- |
| 33 |
Version: GnuPG v1.4.2 (MingW32) |
| 34 |
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org |
| 35 |
|
| 36 |
iD8DBQFDD7fLO+Ewtpi9rLERAi3NAJsEKnxeVaCrJUl6dSvaU1zP3J4OpwCgxa5v |
| 37 |
HfmJvCp8XDXDYAyFpYDoNu0= |
| 38 |
=bV8B |
| 39 |
-----END PGP SIGNATURE----- |
| 40 |
-- |
| 41 |
gentoo-dev@g.o mailing list |
Archives