Internal error compiling xalan on red-hat 7.3

["AESYS S.p.A. [Enzo Arlati]" <en...@aesys.it>]

I build the xalan-c rev 1.10 with xerces-c 2.70 on a Red Hat Linux 7.3
2.96-110 (gcc version 2.96 20000731).
I got the error "Internal error: Segmentation fault." when I compile the
files:

/usr/local/xml-xalan/c/src/xalanc/Include/XalanObjectCache.hpp:293
and
/usr/local/xml-xalan/c/src/xalanc/Include/XalanObjectStackCache.hpp:74

both file give the error on equal code , a reported belowe:

#if !defined(XALAN_NO_STD_NAMESPACE)
                using std::for_each;
#endif
                for_each(
                                m_stack.begin(),
                                m_stack.end(),
                                m_deleteFunctor);
        }
---------------------------------------------------------
At the moment I solved the problem simply commenting the
critical code ( the for_each call ).

---------------------------------------------------------
#if !defined(XALAN_NO_STD_NAMESPACE)
                using std::for_each;
#endif
                /***********
                for_each(
                                m_stack.begin(),
                                m_stack.end(),
                                m_deleteFunctor);
                                ************/
        }
---------------------------------------------------------


My questions are:
1) why I get these error and how can I solve it.
2) Also with the comment, the Xalan module works, so I'm wondering what is
the role
   of the commented code what is doing.

Regards, Enzo Arlati

Re: Internal error compiling xalan on red-hat 7.3

[David Bertoni <db...@apache.org>]

AESYS S.p.A. [Enzo Arlati] wrote:
> I build the xalan-c rev 1.10 with xerces-c 2.70 on a Red Hat Linux 7.3
> 2.96-110 (gcc version 2.96 20000731).
> I got the error "Internal error: Segmentation fault." when I compile the
> files:
> 

You should not use GCC 2.96 for production:

     http://gcc.gnu.org/gcc-2.96.html

This bogus version of GCC is known to fail when compiling Xalan-C, and 
to generate broken code when it does compile.  We do not support it.

Dave