Mailing-List: contact axis-c-user-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache AXIS C User List" <axis-c-user@ws.apache.org>
Received-SPF: pass (hermes.apache.org: domain of Chris.Campbell@assetsmart.com
 designates 64.52.11.126 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: HP-UX 11.11 compatibility
Date: Tue, 4 Jan 2005 09:39:39 -0800
Message-ID: <1D04F32D608E8349BCC7E35CA9B3321C0785D4@mailsrv1.assetsmart.local>
Thread-Topic: HP-UX 11.11 compatibility
Thread-Index: AcTyZhYzw4uPztDZReGyrp3zs6uKVAAHEYAQ
From: "Christopher J. Campbell" <Chris.Campbell@AssetSmart.com>
To: "Apache AXIS C User List" <axis-c-user@ws.apache.org>

Thanks Roshan and Andrew - I'll try omitting tspp from the build. (I am
using Xerces-C.) If tspp is not required when an external parser is
used, i.e. when --with-xercesc is specified, perhaps the build procedure
should skip it by default in that case?

I think the tspp code definitely has issues related to the include file
hierarchy.  I noticed that much of the class implementation code resides
in the header (.hpp) files as opposed to the source (.cpp) files which
seems unusual in my experience. I doubt this is related to gcc's gripes,
but nevertheless 3.4.3 does not like the code as currently structured.

Due to these compile issues I actually switched back to 1.3 last night
and it seems to build cleanly on HP-UX 11i with very minor
platform-related tweaks. These could be easily handled with conditional
directives similar to the existing platform-specific code. If I get 1.3
to function properly then I'll jump back to 1.4 minus tspp and will
share whatever patches I need to make for hpux.

Cheers,

	ChrisC

=20

-----Original Message-----
From: Roshan Weerasuriya [mailto:roshan@opensource.lk]=20
Sent: Tuesday, January 04, 2005 5:59 AM
To: Apache AXIS C User List
Subject: RE: HP-UX 11.11 compatibility

...

The following "--enable-tspp=3Dno" works on my linux mechine (Red Hat
linux 9). You could specify this as a configure option to avoid building
"tspp" parser.

./configure --prefix=3D$AXISCPP_DEPLOY =
--with-apache2=3D/usr/local/apache2/
--with-xercesc=3D/usr/local/xerces-c/ --enable-tspp=3Dno

Roshan

On Tue, 2005-01-04 at 17:12, Andrew Perry2 wrote:
>=20
>=20
> I think that the xml/tspp part of the project is only in a=20
> developmental state [can someone confirm this?]. It is not required as

> part of the project and the Xerces parser could/should be used. If you

> modify the make call to specify to use the xerces parser only then it
should all build OK.
>=20
...