Charles A Edwards <[EMAIL PROTECTED]> writes: > On 09 May 2002 22:35:17 +0200 > Guillaume Cottenceau <[EMAIL PROTECTED]> wrote: > > > Charles A Edwards <[EMAIL PROTECTED]> writes: > > > > > Currently nothing built against c++ will work because of a conflict between c++ >/bin in gcc3.0 and gcc3.1. > > > This caused the problem when Mesa was rebuilt with gcc3.1 and the -3 version >released. > > > Mesa has been patched to eliminate the problem in the current release 4.0.2-4mdk. > > > > Untrue.
[...] > doxyygen has not been recompiled with new gcc (gcc-3.1-0) it > was to the pkgs that have been to which I referred. What you said is: "nothing built against c++ will work", which is vague, but I do think that the most probable interpretation was that all older packages linked against libstdc++ were not working. What you say now is plain un-understandable to me, so I can't comment you new claims :-). If you say that every C++ stuff built with the new gcc will not work, recently packaged `bzflag' and `xwc' are an evidence that it's not true, they do work. To sum up current state: - old C++ stuff is still working in Cooker - new C++ stuff is working in Cooker - even, stuff linked against Mesa, be it recompiled or not since g++ change, is (now, with latest gb patch) working in Cooker So I don't see where is your problem :-). -- Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/
