On Mon, Apr 15, 2002 at 11:43:19PM +0200, Tomas Pospisek's Mailing Lists wrote: > My knowledge of gcc-2.95 vs gcc-3.0 intricacies and C++ specialities is > far too small to figure out what's going on here: > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=140032 > > and I estimate that I won't have the time to improve my knowledge > sufficiently either untill woody deadline so I plan to drop support for > all platforms that _require_ gcc-3.0. How would I achieve that: > > * by explicitly adding "Conflicts: gcc-3.0" to the control file? > * by explicitly naming all supported plattforms? > * by excluding some architectures (this doesn't seem to be possible) > > The upstream who's much more knowledgeable won't be available during the > next two weeks either. So if there's any g++-3.0 guru listening, then I'd > be glad for some hints. > > Here's how far I've come: If I: > > * define CXX = LINKER = g++-3.0 and CC = gcc-3.0 > * add -DCOMPILER_GNU to the CXX options in the Makefile > then the "looser throw specifier for `virtual" goes away. > > but then I get plentyful of undefined references. Ex:
If you're testing this on your x86 (or similar) platform, the undefined references are to be expected. You can't link 2.95 and 3.0 C++ code, and QT is 2.95 C++ code. Try working on one of the architectures in question; they should be available to you as a Debian developer. -- Daniel Jacobowitz Carnegie Mellon University MontaVista Software Debian GNU/Linux Developer -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]