Hi Patrick,
I have never used AS/400 so I will have to do some digging to find this
information for you.
I would imagine you would have to set:
export TRANSCODER=Uniconv390 (you might want NATIVE instead).
export MESSAGELOADER=INMEM
export USELIBWWW=0
export NETACCESSOR=Socket
export CC=???
export CXX=???
But I am not sure what to set CC and CXX to on AS/400.
BTW, the environment variables that the runConfigure sets are (some are
optional):
TRANSCODER
MESSAGELOADER
NETACCESSOR
THREADS
BITSTOBUILD
CC
CXX
CXXFLAGS
CFLAGS
LDFLAGS
LIBS
Regards,
David A. Cargill
"Patrick
Townsend"
<Patrick.Townsend To
[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
cc
04/28/2004 10:59
PM Subject
RE: AS400, was: z/OS and OS/390
runConfigure ???
Please respond to
xerces-c-dev
Hi David,
I would like to build this on the AS/400 (iSeries), too. Can you tell me
the
settings for AS/400? I've loaded gmake so I think I just need the exports.
Thanks,
Patrick
-----Original Message-----
From: David Cargill [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 28, 2004 11:14 AM
To: [EMAIL PROTECTED]
Subject: RE: z/OS and OS/390 runConfigure ???
Hi,
To build xerces-c on 390 we just use "configure" rather than using the
runConfigure wrapper script so that is why the runConfigure script hasn't
been modified. I will see what we can do about getting runConfigure
modified for 390 for the next release...
The environment variables I set (the last time I built it which was a while
ago) before calling configure are:
export TRANSCODER=Uniconv390 (you might want NATIVE instead).
export MESSAGELOADER=INMEM
export USELIBWWW=0
export NETACCESSOR=Socket
export CC=c89
export CXX=c++
unset _CXX_CXXSUFFIX
export _CXX_CCMODE=1
export _C89_CCMODE=1
after running configure,
export _CXX_CXXSUFFIX=cpp
gmake
Regards,
David A. Cargill
"Bovy, Stephen J"
<[EMAIL PROTECTED]
com> To
<[EMAIL PROTECTED]>
04/28/2004 01:28 cc
PM
Subject
RE: z/OS and OS/390 runConfigure
Please respond to ???
xerces-c-dev
Then why haven't those fixes been merged back into the Xerces tree ???
Is IBM not being a good citizen in this matter ???
Is IBM Purposefully and intentionally maintaining a "separate" "fork" of
Xerces ?????
The main reason I ask this , is because the official IBM toolkit is always
way way behind the current Xerces version.
And on the Alpha works site there are no binary builds provided for z/OS,
which is frustratingly stupid.
From: moshief, daniel [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 28, 2004 7:07 AM
To: '[EMAIL PROTECTED]'
Subject: z/OS and OS/390 runConfigure ???
The general question is: can xerces be compiled and successfully built and
function
correctly? IBM XML Toolkit support has indicated that the xerces code
would need updates
for it to function (ie that IBM XML Toolkit support does).
Content-Type: text/plain;
charset="us-ascii"
Subject: z/OS and OS/390 runConfigure ???
Date: Tue, 27 Apr 2004 13:42:59 -0400
From: Bovy, Stephen J <[EMAIL PROTECTED]>
How come the runConfigure script has no support for z/OS and/or OS/390
????
---------------------------------------------------------------------
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]
