| 1 |
maillog: 27/08/2005-02:46:03(+0200): Bjarke Istrup Pedersen types |
| 2 |
> I must say I have been wondering about this for a while too. |
| 3 |
> A solution might be add some sort of flag to packages that are binary, |
| 4 |
> and then let portage install libstdc++ the first time you install this |
| 5 |
> kind of package. |
| 6 |
|
| 7 |
You mean, like have binary packages depend on |
| 8 |
virtual/libstdc++-SOMEVERSION and have virtual/libstdc++ provided by gcc |
| 9 |
or the split-out libstdc++ ebuild? |
| 10 |
|
| 11 |
> Mike Frysinger skrev: |
| 12 |
> > On Fri, Aug 26, 2005 at 10:14:04AM +0100, Chris Bainbridge wrote: |
| 13 |
> > |
| 14 |
> >>Subject says it all - is there any reason why 3.4.4 installs either |
| 15 |
> >>gcc-3.3* or libstdc++-v3 built with gcc-3.3? |
| 16 |
> > |
| 17 |
> > |
| 18 |
> > because i got tired of people complaining about broken systems when they |
| 19 |
> > emerged gcc-3.4.4 and cleaned out all gcc-3.3.x versions from their system |
| 20 |
> > |
| 21 |
> > |
| 22 |
> >>Is it possible to compile |
| 23 |
> >>a native 3.4 system without the old gcc if I don't need binary |
| 24 |
> >>compatibility? |
| 25 |
> > |
| 26 |
> > |
| 27 |
> > i just add libstdc++-v3 to my package.provided in /etc/portage/profile/ and |
| 28 |
> > call it a day |
| 29 |
> > |
| 30 |
> > i dont really see there being a clean solution until we have portage support |
| 31 |
> > to track ABI dependencies |
| 32 |
> > -mike |
| 33 |
> |
| 34 |
> -- |
| 35 |
> gentoo-dev@g.o mailing list |
| 36 |
> |
| 37 |
|
| 38 |
-- |
| 39 |
\ Georgi Georgiev \ Professor: This is gonna be one hell of a \ |
| 40 |
/ chutz@×××.net / bowel movement. Afterwards, he'll be lucky / |
| 41 |
\ +81(90)2877-8845 \ if he has any bones left. \ |
Archives