Hi David,
I applied these changes to our V5R2 system and it ran much further! The
problem with the platform identifier seems resolved. When I ran gmake it did
a lot of cp copies, and then tried to run ICC for a compile. It got this
error:
icc -qnotempinc -D_MULTI_THREADED -DOS400 -c -I/xerces/xerces-c-src_2_5_0/i
nclude -I/include -DPROJ_XMLPARSER -DPROJ_XMLUTIL -DPROJ_PARSERS -DPROJ_
SAX4C -DPROJ_SAX2 -DPROJ_DOM -DPROJ_DEPRECATED_DOM -DPROJ_VALIDATORS -DXML
_USE_ICONV400_TRANSCODER -DXML_USE_INMEM_MESSAGELOADER -DXML_USE_PTHREADS -D
XML_USE_NETACCESSOR_SOCKET -I. -g -o
/xerces/xerces-c-src_2_5_0/obj/OS400/Base64.o Base64.cpp
Keyword NOTEMPINC not valid for this command.
Error found on CRTCPPMOD command.
GMAKE[1]: *** [Base64.o] Error 1
GMAKE[1]: Leaving directory `/xerces/xerces-c-src_2_5_0/src/xercesc/util'
GMAKE: *** [Util] Error 2
$
I thought this might be a problem with the "-qnotempinc" parameter passed to
icc and did a source code search. I found instances of notempinc in the
Makefile.incl files. I tried removing this parameter in the src/xerces file
like this:
ifeq (${SYSOVR},OS400)
# PLATFORM_COMPILE_OPTIONS = -qnotempinc
PLATFORM_COMPILE_OPTIONS =
However, this did not remove the error.
The icc program is a CLE object in the GNU library. I tried retrieving the
source, but with no luck. I'm guessing that icc passes the parameter to the
CRTCPPMOD command. I'll try finding the source for icc at the GNU site. Any
thoughts you have would be appreciated!
Thanks,
Patrick
-----Original Message-----
From: David Cargill [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 02, 2004 1:25 PM
To: [EMAIL PROTECTED]
Subject: RE: Xerces-C 2.6 Release
Hi Patrick,
Today I committed a fix to cvs which I hope solves this problem. The files
that were updated were config.sub (in src/xercesc/, tests/ and samples);
runConfigure (in src/xercesc/) and build-other.xml (in doc).
The build-other.xml file contains instructions on building on AS400.
Can you try doing a build on AS400 and let me know how it goes? Thanks.
Regards,
David A. Cargill
XML Parser Development
IBM Toronto Lab
(905) 413-2371, tie 969
[EMAIL PROTECTED]
"Patrick
Townsend"
<Patrick.Townsend To
[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
cc
08/20/2004 11:41
AM Subject
RE: Xerces-C 2.6 Release
Please respond to
xerces-c-dev
Hi David,
I reported a problem with building Xerces on the iSeries (AS/400) platform
a
few weeks ago. The configuration scripts were reporting a problem with the
machine type. Do you know if this build problem was resolved in Xerces 2.6?
I've not seen any update on it.
Thanks,
Patrick
-----Original Message-----
From: David Cargill [mailto:[EMAIL PROTECTED]
Sent: Friday, August 20, 2004 8:33 AM
To: [EMAIL PROTECTED]
Subject: Xerces-C 2.6 Release
In a note to this list in April regarding the Xerces-C 2.6 Features List, I
suggested releasing Xerces-C 2.6 in 4Q 2004. As most of the features are
complete I propose September 29th for the actual release date.
I would also like to propose changing some of the available download
binaries as follows:
32 Bit Xerces-C
-Drop RedHat Linux 7.2 compiled with Intel C++ Compiler v7.1
-Drop SuSE Linux 8.1 compiled with gcc 3.2 (i386)
-Add RedHat Linux 8.0 compiled with gcc 3.2 (i386)
-Keep Windows, AIX, HP & Solaris same as last release
64 Bit Xerces-C
-Drop Windows XP, IA64 compiled with Intel C++ Compiler v7.1
-Drop RedHat Linux 7.2 IA64 compiled with Intel C++ Compiler v7
-Add SuSE Linux 8.0 (64 bit AMD) with gcc 3.2.2
-Keep AIX, HP & Solaris same as last release
Regards,
David A. Cargill
XML Parser Development
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
