GCC 3.2 issues on Solaris

["Aaron Williams" <aaron_williams at net dot com>]

I have  a question regarding GCC 3.2 on Solaris 2.7 running on Sparc.  I 
do not know if this is a bug or if it is a problem with binutils, but I 
am seeing problems with KDE applications compiled with GCC where 
destructors located in a shared library (qt) are being called from 
on_exit after the shared library has been unloaded from memory. From my 
research, I see that __cxa_atexit should be used instead, but this does 
not appear to be implemented in the Sun libc library.  Is there a 
solution to this problem with Solaris, or is this a binutils issue?  Is 
there any workaround for this?  This looks like issue 7764, except there 
appears to be no workaround.

In addition, I have had problems compiling KDE 3.0.3 and especially 
koffice 1.2.  I have seen several of the bugs listed in the database and 
have managed to work around all of them except for a destructor linkage 
problem in koffice and this on_exit issue.

I might add that I am using binutils 2.12.1 since 2.13 seems to have 
problems.

When compiling gcc 3.2 I had a lot of problems with the configure 
scripts on Solaris.

I used the following configure options:

export set CONFIG_SHELL=/bin/ksh
/bin/sh ./configure --prefix=/tools/gcc-3.2 --disable-multilib

This was compiled on an Ultrasparc running Solaris 2.7 in 32-bit mode.

The configure scripts in sun-sparc-solaris2.7/lib*  have problems 
finding the include files and some of the configuration scripts like 
install-sh.  Manually patching the configure scripts to add an 
additional "../" in key places allowed me to compile gcc.  The latest 
snapshot as of 10/7/2002 also appears to have similar configuration 
problems but not as bad as 3.2.  One reference I found was bug 7757, 
which is labeled low priority.

I realize that I am not providing enough information in many cases. I 
will supply detailed information if I have problems compiling or running 
KDE 3.0.4 (just released).

-Aaron