aCC -O -DNDEBUG -AA +Z -DHPUX -D_THREAD_SAFE -c -I.
-I/home/jp/xml/xerces-c-src1_7_0/src/
-I/home/jp/xml/xerces-c-src1_7_0/include/xercesc
-I/home/jp/xml/xerces-c-src1_7_0/include/ -o
/home/jp/xml/xml-xalan/c/obj/XalanAttr.o XalanDOM/XalanAttr.cpp
Error 419: "./XalanDOM/XalanDOMString.hpp", line 88 # 'vector' is used as a
type, but has not been defined as a type.
typedef vector<XalanDOMChar> XalanDOMCharVectorType;
^^^^^^
Error 318: "./XalanDOM/XalanDOMString.hpp", line 88 # A template name was
expected instead of '<type inserted by compiler>'.
Did you forget to define the template?
typedef vector<XalanDOMChar> XalanDOMCharVectorType;
^^^^^^^^^^^^^^
Error (future) 600: "./XalanDOM/XalanDOMString.hpp", line 88 # Type
specifier is omitted; "int" is no longer assumed.
typedef vector<XalanDOMChar> XalanDOMCharVectorType;
^^^^^^^^^^^^^^
Error 419: "./XalanDOM/XalanDOMString.hpp", line 89 # 'vector' is used as a
type, but has not been defined as a type.
typedef vector<char> CharVectorType;
^^^^^^
Error 318: "./XalanDOM/XalanDOMString.hpp", line 89 # A template name was
expected instead of '<type inserted by compiler>'.
Did you forget to define the template?
typedef vector<char> CharVectorType;
^^^^^^
Error (future) 600: "./XalanDOM/XalanDOMString.hpp", line 89 # Type
specifier is omitted; "int" is no longer assumed.
typedef vector<char> CharVectorType;
^^^^^^
Error 419: "./XalanDOM/XalanDOMString.hpp", line 90 # 'vector' is used as a
type, but has not been defined as a type.
typedef vector<wchar_t>
WideCharVectorType;
^^^^^^
Error 318: "./XalanDOM/XalanDOMString.hpp", line 90 # A template name was
expected instead of '<type inserted by compiler>'.
Did you forget to define the template?
typedef vector<wchar_t>
WideCharVectorType;
^^^^^^^^^
Error (future) 600: "./XalanDOM/XalanDOMString.hpp", line 90 # Type
specifier is omitted; "int" is no longer assumed.
typedef vector<wchar_t>
WideCharVectorType;
^^^^^^^^^
Error 419: "./XalanDOM/XalanDOMString.hpp", line 101 # 'size_type' is used
as a type, but has not been defined as a type.
typedef XalanDOMCharVectorType::size_type
size_type;
^^^^^^^^^
Error 448: "./XalanDOM/XalanDOMString.hpp", line 101 # Operator '::' must be
preceded by a name of a namespace or class;
'XalanDOMCharVectorType' is neither.
typedef XalanDOMCharVectorType::size_type
size_type;
^^^^^^^^^^^^^^^^^^^^^^^^
-----Original Message-----
From: David N Bertoni/Cambridge/IBM [mailto:[EMAIL PROTECTED]]
Sent: Thursday, July 11, 2002 12:14 AM
To: [EMAIL PROTECTED]
Subject: RE: HPUX 11 xerces xalan
I do runConfigure like this:
./runConfigure -p hp-11 -c cc -x aCC
I get my Xalan sources directly from CVS. I've built with the Xerces
binary distribution, the Xerces source distribution, and from CVS.
Here's the output from one file, with -v:
aCC -O -DNDEBUG +Z -DHPUX -D_THREAD_SAFE +DAportable +p -mt -Aa -AA -v
-c -I. -I/home/xalan/apache/xml-xerces/c/src/
-I/home/xalan/apache/xml-xerces/c/include/xercesc
-I/home/xalan/apache/xml-xerces/c/include/ -o
/home/xalan/apache/xml-xalan/c/obj/XalanAttr.o XalanDOM/XalanAttr.cpp
/opt/aCC/lbin/ctcom.pa20 -DNDEBUG -DHPUX -D_THREAD_SAFE -architecture
portable -errors all -diag anachronisms,warnings,futureerrors -I.
-I/home/xalan/apache/xml-xerces/c/src/
-I/home/xalan/apache/xml-xerces/c/include/xercesc
-I/home/xalan/apache/xml-xerces/c/include/ -piccode long -inst
compiletime -diags 523 -D__HP_CXD_SPP=1 -D__hpux -D__unix -D__hppa
-D__hp9000s800 -D__parisc -D__STDCPP__ -D_HP_NAMESPACE_STD -D_ILP32
-D__HP_aCC=33300 -D_REENTRANT -D_RWSTD_MULTI_THREAD -D_RW_MULTI_THREAD
-D_HPUX_SOURCE -D_POSIX_C_SOURCE=199506L -D__hp9000s700 -D_PA_RISC1_1
-I/opt/aCC/include_std -I/opt/aCC/include_std/iostream_compat
-I/usr/include -I/usr -test namespaces -koenig_lookup on -ansi_for_scope
on -inline_power 2 -longbranch 0 -unique_strings on -o
/home/xalan/apache/xml-xalan/c/obj/XalanAttr.o -cachesize 256
-plusooption
-Oq02,al,ag,cn,Lm,sz,Ic,vo,lc,Mf,Po,es,rs,sp,in,vc,Pi,fa,pe,Rr,Fl,pv,pa,nf,c
p,lx,st,ap,Pg,ug,Lu,lb,uj,dp,Fs,bp,wp,Ex,mp,rp,ap,dn,Sg,pt,kt,Em,pc,np!
XalanDOM/XalanAttr.cpp
I'd be happy to provide you with whatever specs you need. However, I will
be going on vacation for a week starting tomorrow night, so best get me
want you want by earlier tomorrow morning California time.
Also, please post the errors you're seeing building Xalan, and I'll take a
look. Maybe something will ring a bell.
Dave
"Prothro, John"
<John_Prothro@bm To:
"'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
c.com> cc: (bcc: David N
Bertoni/Cambridge/IBM)
Subject: RE: HPUX 11 xerces
xalan
07/10/2002 08:31
PM
Please respond
to xalan-dev
Hmmm... interesting. My compiler is the same. There are many other
factors though... lib patches, etc... I'll look into it.
BTW, what are your args to runConfigure? Do you add any thing else
to Makefile.in files or do you just untar and run runConfigure and make?
Could you also turn on the -v compiler switch and send me a single
files' compilation output? Also, would you be willing to
send version specs of certain libs?
Thanks a ton,
John
-----Original Message-----
From: David N Bertoni/Cambridge/IBM [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 10, 2002 4:41 PM
To: [EMAIL PROTECTED]
Subject: RE: HPUX 11 xerces xalan
Hey John,
This is very strange. I've built and tested with the latest Xalan code
with both the post 1.7 version of Xerces that I have, and the official
Xerces 1.7 release, and haven't had any problems.
Here's the version of the compiler and OS we're using:
~/apache/xml-xalan/test/tests > aCC -V
aCC: HP ANSI C++ B3910B A.03.33
~/apache/xml-xalan/test/tests > uname -a
HP-UX tcdev1 B.11.00 E 9000/785 2004214080 8-user license
Are your's different? We've had to ask HP for several upgrades after
running into compiler bugs. Perhaps that's why you're having problems?
Dave
"Prothro, John"
<John_Prothro@bm To:
"'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
c.com> cc: (bcc: David N
Bertoni/Cambridge/IBM)
Subject: RE: HPUX 11 xerces
xalan
07/10/2002 02:01
PM
Please respond
to xalan-dev
Sure, I'll do anything you ask. I'll check out whatever code,
wherever... I'll stay up late tonight and build... you name it. :)
-----Original Message-----
From: David N Bertoni/Cambridge/IBM [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 10, 2002 3:28 PM
To: [EMAIL PROTECTED]
Subject: RE: HPUX 11 xerces xalan
Hmm, I just built everything fine with Xerces code that is post 1.7. I can
even get things to work properly if I don't rebuild Xerces with -AA (which
is officially a no-no). I'll download the 1.7 distribution and try that
myself.
Can you post just the errors and the offending lines of code? If it's a
lot, don't bother.
I'll reply again once I've built 1.7 of Xerces with the latest Xalan code.
Dave
"Prothro, John"
<John_Prothro@bm To:
"'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
c.com> cc: (bcc: David N
Bertoni/Cambridge/IBM)
Subject: RE: HPUX 11 xerces
xalan
07/10/2002 12:16
PM
Please respond
to xalan-dev
OK, well, got the latest from cvs but it has build errors.
So, it was suggested that I go back to get 1.7 stable src.
It does not build for erros also.
So... do you guys support native compiles on HPUX with the
-AA switch? The website and download area suggests that you
do support native HPUX builds, but the source does not support
that notion.
Thanks,
John
-----Original Message-----
From: Prothro, John [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 27, 2002 3:15 PM
To: '[EMAIL PROTECTED]'
Subject: RE: HPUX 11 xerces xalan
Excellent. I tried this months ago and got no where on
this list. Thanks. Your fantastic!!!! Who's your boss?
Can I buy you lunch?.. just kidding. :)
I'll -try- to get the latest source and re do experiment.
John
-----Original Message-----
From: David N Bertoni/Cambridge/IBM [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 27, 2002 3:04 PM
To: [EMAIL PROTECTED]
Subject: RE: HPUX 11 xerces xalan
Hi John,
If you're building with the -AA switch, then I suggest you get the latest
sources from CVS and build with them. A while back, I did the work to make
the source code compatible with HP's new standard library. We didn't do
the distribution with the -AA switch because the Xerces team does not use
it.
That will also solve the problem you're having with supports() vs.
isSupported(), which is a result of the Xerces team changing their
interfaces. You're trying to build Xalan sources which use the old
interfaces against a version of Xerces after the changes.
I'll kick off a build with -AA right now, just to make sure the sources are
still compatible. For more info about getting sources from CVS, see here:
http://xml.apache.org/cvs.html
Dave
"Prothro, John"
<John_Prothro@bm To:
"'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
c.com> cc:
"'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>,
"'[EMAIL PROTECTED]'"
<[EMAIL PROTECTED]>
06/27/2002 12:24 Subject: RE: HPUX 11 xerces
xalan
PM
Please respond
to xalan-dev
Ok, Thanks...
My Compiler Version is...
HP aC++ B3910B A.03.33
Also, I am in a similar situation as you probably...
I work for a large software company and I build mega bytes of source on
this machine every day or so... so I know it is up to the task.
Another question... was the distribution built with the -AA switch?
The reason I am building, instead of using the distributed libs is
because of the documented requirement that -all- translation units must be
rebuilt with this switch. (ref. hp's aCC 3.33 manual)
I have had to change the HPUXDefinitions.hpp to exclude the
XALAN_NO_NAMESPACES,
XALAN_OLD_STREAMS, XALAN_OLD_STREAMS_HEADERS, and ultimately had to
define XALAN_UNALIGNEDLAN_NO_COVARIANT_RETURN_TYPE to get around the
compiler error in XercesAttrBridge.cpp whereas line 269 indicates
"supports"
is not a member of class DOM_Attr. But when I did that and rebuilt, I
started to get other
errors relating to XALAN_UNALIGNED definition. ;( So I gave up and went
to
lunch.
Also, Thanks you very much for the reply. Any further assistance
will be greatly appreciated.
My compile flags are...
aCC -O -DNDEBUG -mt -AA -D_HPUX_SOURCE -D_HP_NAMESPACE_STD +Z -DHPUX
-D_THREAD_SAFE
Thanks a whole bunch,
John
-----Original Message-----
From: David N Bertoni/Cambridge/IBM [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 27, 2002 1:17 PM
To: [EMAIL PROTECTED]
Subject: Re: HPUX 11 xerces xalan
Earlier today, I built Xalan with the latest CVS sources on HP-UX 11
without any problems. Here's our compiler version:
~/apache/xml-xalan/test/tests > aCC -V
aCC: HP ANSI C++ B3910B A.03.33
~/apache/xml-xalan/test/tests > uname -a
HP-UX tcdev1 B.11.00 E 9000/785 2004214080 8-user license
The distribution was built with this version of the compiler.
If your compiler is not at the level, you should probably upgrade. If your
compiler is at a higher level, I'll have to ask our HP contact to upgrade
the compiler so I can figure out what's wrong.
I do remember a compiler issue a while back, but we got an upgrade. I
don't remember the details any longer.
If you continue to have problems, you might want to post a _brief_ message
that explains what problems you're seeing.
"Prothro, John"
<John_Prothro@bm To:
"'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
c.com> cc: (bcc: David N
Bertoni/Cambridge/IBM)
Subject: HPUX 11 xerces
xalan
06/27/2002 10:58
AM
Please respond
to xalan-dev
Hi,
I have noticed that your site offers xerces/xalan binaries for HPUX 11.
I have downloaded the latest stable source and can get xerces to compile
with relative minimal effort.
Xalan however is proving to be a challenge. Could someone be so
kind as to supply the source that compiles on HPUX 11 with aCC 3.3x
or better. Or can someone supply the compiler flags, defines,
changes to Include/HPUXDefinitions.hpp etc... that is required to
build the product?
Thanks,
John
