We are not supporting gcc 3.0.4 yet. I don't know what the problem with
the compiler is, but we don't really have the resources to support more
than one version of gcc, especially given its quirkiness.
There is no way you should define XALAN_NO_NAMESPACES for a compiler that
does support namespaces. Also, I think you're confusing that #ifdef, since
it's ! (not) defined(XALAN_NO_NAMESPACES).
If gcc finally has a conforming library, you could change the file
GCCDefinitions.hpp and comment out XALAN_OLD_STREAM_HEADERS. Otherwise,
you could try including iostream.h, instead of just strstream.h:
#if defined(XALAN_OLD_STREAM_HEADERS)
#include <iostream.h> // This is the new include
#include <strstream.h>
#else
#include <iostream>
#include <strstream>
#endif
Dave
"Bruce Bailey"
<[EMAIL PROTECTED] To: "Xalan Developers"
<[EMAIL PROTECTED]>
p.com> cc: (bcc: David N
Bertoni/Cambridge/IBM)
Subject: Compiling With gcc 3.0.4 -
'cerr' undefined
03/06/2002 07:57
AM
Please respond
to xalan-dev
Hi
I have been attempting to compile Xalan 1.3 on gcc 3.0.4 on RH 7.1. I have
discovered that one of the modules won't compile due to a missing
(conditionally removed) using statement.
The module is XalanStdOutputStream.cpp. The compiler is complaining about
cerr being undefined. I notice that elsewhere in the module is:
#if !defined(XALAN_NO_NAMESPACES)
using std::ostream;
using std::cerr;
#endif
when I added "-z -UXALAN_NO_NAMESPACES" to the runConfigure command, the
build failed pretty much right away. I am beginning to have a sneaking
suspicion that gcc 3.0.4 isn't supported yet.
Does anyone have any ideas? Are there different parameters to runConfigure
that I should be using? Currently, I use:
./runConfigure -p linux -c gcc -x g++
This worked fine with gcc 2.95 and 2.96 (after removing -instances=static
from the makefile).
Thanks,
Bruce
Bruce Bailey
2525 SW First Avenue
Portland, OR 97201
[EMAIL PROTECTED]
