DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24875>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24875

exceptions don't work for gcc version 3.2.2

           Summary: exceptions don't work for gcc version 3.2.2
           Product: Xerces-C++
           Version: Nightly build (please specify the date)
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Build
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]


I use Xerces C++ from CVS, updated the evening of 20 November 2003. My OS is
RedHat 9. My c++ compiler is: `g++ -v`
Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/specs
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
--infodir=/usr/share/info --enable-shared --enable-threads=posix
--disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux
Thread model: posix
gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)

This problem was detected because DOMTypeInfoTest produces the following output
when it is run in a directory that does not contain "data/TypeInfo.xml":
DOMTypeInfo test at line 881was not carried out
DOMTypeInfo test at line 915was not carried out
DOMTypeInfo test at line 938was not carried out
DOMTypeInfo test at line 962was not carried out
DOMTypeInfo test at line 985was not carried out
Test Run Successfully

The problem did not go away when I added  -z-fexceptions -z-frtti to the
runConfigure arguments and rebuilt xerces and tests. (The gcc info seems to say
this is not necessary, but you never know ...) 

I am not an expert in autoconf, but I came across AC_CXX_EXCEPTIONS
http://www.gnu.org/software/ac-archive/htmldoc/ac_cxx_exceptions.html while I
was researching this problem. Perhaps this can be used to detect (and perhaps
even correct) this problem.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to