1.12.2005, 1:30:41, Marien Zwart wrote:
> Not sure if everyone is aware of this, but most installed pythons link to
> libstdc++.so. This is not a problem if you run the above revdep-rebuild (it
> should catch it just fine). It is a problem if you get rid of gcc 3.3 before
> installing libstdc++-v
1.12.2005, 0:29:48, Chris Gianelloni wrote:
> On Wed, 2005-11-30 at 17:34 -0500, Philip Webb wrote:
>> Ordinarily, I upgrade packages individually when it seems appropriate
>> & never do 'emerge world' with or without '-e' or other flags;
>> I do 'esync' every weekend & look at what is marked as
30.11.2005, 22:19:27, Peter Ruskin wrote:
> On Wednesday 30 November 2005 20:12, Mark Loeser wrote:
>> gcc-3.4.* will not be selected as your system compiler after
>> merging it. The old gcc profile is still valid, therefore it is
>> kept. Users have to consciously go and change their profile t
