--- Comment #5 from tom dot culliton at oracle dot com 2007-03-22 20:15
---
That does indeed appear to have been the problem. Even though the system
claims that APAR was already applied, the header file was still missing the
typedef keyword. I suspect something silly like the compiler
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Severity|blocker |normal
Component|libstdc++ |other
--- Comment #1 from dje at gcc dot gnu dot org 2007-03-20 21:43 ---
Compiling with -pthread adds -D_THREAD_SAFE to the defined macros, which causes
different header files to be included. Prior to GCC 4.3, this appears to cause
a non-unique name to be chosen for the global constructor
--- Comment #2 from dje at gcc dot gnu dot org 2007-03-20 21:47 ---
Andrew Pinski pointed out that this is known with a workaround:
http://www-128.ibm.com/developerworks/forums/dw_thread.jsp?forum=747thread=119546cat=72
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31282
--- Comment #3 from pinskia at gcc dot gnu dot org 2007-03-20 21:48 ---
http://gcc.gnu.org/ml/gcc-help/2007-03/msg00095.html
According to IBM, the fix for this APAR IY90737 is incorporated into
Service Pack 5300-05-04.
Do you have that installed?
--
--- Comment #4 from dje at gcc dot gnu dot org 2007-03-20 21:48 ---
and more info http://gcc.gnu.org/ml/gcc-help/2007-03/msg00095.html
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31282
