From http://gcc.gnu.org/gcc-3.2/c++-abi.html: "We strongly advise all developers and distributors to follow the guidelines given here for GNU/Linux systems. Configuring GCC Configure GCC with this options: --enable-__cxa_atexit GCC is configured by default on GNU/Linux systems also with these two flags, do not change them to any other value: --enable-threads=posix -enable-shared If you do not use these options, your files generated by GCC will not be fully ABI compatible." The Gentoo gcc-3.2_pre ebuild doesn't seem to use the --enable-__cxa_atexit configure flag. Should it? FWIW, the latest gcc-3.2 based RedHat beta and the latest Rawhide uses it.
Guess we should .. will add it this side and test.
I'd say it's probably a good time for a newer gcc snapshot while you're at it.
It appears enable-__cxa_atexit seems to break programs/libraries linked against the shared libstc++, etc. libraries from the previous snapshot. While this is annoying to me, I'll survive. However, I'm sure this will generate some noise for people when they make the switch, so I thought I'd give a heads up.
The gcc guys should be shot :P
I know, I made the unfortunate mistake of exiting X. I just discovered, much to my eternal joy, that MesaGL apparently is programmed in C++ [I did not know this], and therefore I'm stuck in console. I'm beginning to suspect , due to the fact that many of the undefined symbols refer to GLIBCPP_3.1 or CXXABI_1 not being in libstc++.so.5, that they *just* now switched the C++ ABI from 3.1 to 3.2!!! I cannot confirm that statement as of yet, though I'm poking around the Changelog to see what's what. Well, you might as well stick with the --enable-__cxa_atexit since now all the people are probably going to have to recompile any c++ programs now. I have close to 230 packages installed, so I don't even know where to begin. A perl script which traverses the filesystem, objdumping and grepping for the telltale symbols, then uses epm to determine which package the library/binary belongs to would come in handy right about now. Ah the joy that the GCC steering brings to millons of GCC users worldwide...
Slashdot's saying that the production 3.2 was just released.
Already on it. Got about 6MB with this 56k dialup :P
This default verboseness makes me want to shoot gcc developers: cpp0: warning: changing search order for system directory... Obnoxious warning even appears with the c preprocessor, causing many autoconf macros to return a failed condition. Arrg
Has been a problem for a while. Think Lostlogic knows the fix.
ICAClient has troubles with this too :'-(
