On Fri, Jun 12, 1998 at 03:54:57PM +0200, Gregor Hoffleit wrote: > But when I compared the resulting packages, I found that the old package > had been built with a g++/libstdc++ based on 2.7.2, while nowadays g++ > 2.90 is the official C++ compiler, going with libstdc++2.8. > > Now I don't know: When I recompile the package using the official g++ > 2.90 / libstdc++ 2.80 combo, this may introduce new bugs, therefore I'm > sure Brian won't allow this to go into frozen. > > The alternative is faking an build environment that installs g++272 as > c++ and uses libstdc++272. Is this the accepted way to go ?
I think I'm going to have to do the same if I'm to fix 22325 against guavac. It won't build with libstdc++2.8, and the error seems to be in the STL header files, ie not in guavac's source. Very strange. Hamish -- Hamish Moffatt, [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Latest Debian packages at ftp://ftp.rising.com.au/pub/hamish. PGP#EFA6B9D5 CCs of replies from mailing lists are welcome. http://hamish.home.ml.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
