Hi David, Here is how we are tried to build 2.5.0:
runConfigure -p os400 -x icc -c icc -m inmem -t Iconv400 The first bit of output looks like this: Generating makefiles with the following options ... Platform: os400 C Compiler: icc C++ Compiler: icc Message Loader: inmem Net Accessor: socket Transcoder: Iconv400 Thread option: pthread bitsToBuild option: 32 Extra compile options: Extra link options: Extra configure options: Debug is OFF NATIVE OS400 BUILD Then some checking of compiler options happens. One error pops out of this process: Invalid configuration `AS400-OS400': machine `AS400' not recognized A lot of make files get created. Then this: In future, you may also directly type the following commands to create the Makefiles. export TRANSCODER="Iconv400" export MESSAGELOADER="INMEM" export NETACCESSOR="Socket" export THREADS="pthread" export BITSTOBUILD="32" export CC="icc" export CXX="icc" export CXXFLAGS=" -DPROJ_XMLPARSER -DPROJ_XMLUTIL -DPROJ_PARSERS -DPROJ_SAX4C -DPRO J_SAX2 ICONV400_TRANSCODER -DXML_USE_INMEM_MESSAGELOADER -DXML_USE_PTHREADS -DXML_U SE_NETACCESSOR export CFLAGS=" -DPROJ_XMLPARSER -DPROJ_XMLUTIL -DPROJ_PARSERS -DPROJ_SAX4C -DPROJ_ SAX2 -D ONV400_TRANSCODER -DXML_USE_INMEM_MESSAGELOADER -DXML_USE_PTHREADS -DXML_USE _NETACCESSOR_S export LDFLAGS=" " export LIBS=" -lpthread " configure When I run gmake it fails with this: gmake Preparing the directory structure for a build ... mkdir -p /xerces/xerces-c-src_2_5_0/obj/UNKNOWN mkdir -p /xerces/xerces-c-src_2_5_0/lib /usr/bin/gmake -C util includes GMAKE[1]: Entering directory `/xerces/xerces250/src/xercesc/util' mkdir -p /xerces/xerces-c-src_2_5_0/include/xercesc/util cp -fp ArrayIndexOutOfBoundsException.hpp AutoSense.hpp BaseRefVectorOf. BinMemInputStream.hpp BitOps.hpp BitSet.hpp CountedPointer.hpp DefaultPa hpp FlagJanitor.hpp HashBase.hpp HashCMStateSet.hpp HashPtr.hpp HashXMLC Exception.hpp IOException.hpp Janitor.hpp KeyRefPair.hpp KeyValuePair.hp ntException.hpp NullPointerException.hpp NumberFormatException.hpp OutOf latformUtils.hpp QName.hpp RefArrayOf.hpp RefArrayVectorOf.hpp RefHashTa RefStackOf.hpp RefVectorOf.hpp RuntimeException.hpp SchemaDateTimeExcept ringPool.hpp TranscodingException.hpp TransENameMap.hpp TransService.hpp hpp UTFDataFormatException.hpp ValueArrayOf.hpp ValueHashTableOf.hpp Val ion.hpp XMemory.hpp XMLAbstractDoubleFloat.hpp XMLASCIITranscoder.hpp XM oder.hpp XMLDateTime.hpp XMLDeleterFor.hpp XMLDOMMsg.hpp XMLDouble.hpp X r.hpp XMLException.hpp XMLExceptMsgs.hpp XMLFloat.hpp XMLIBM1047Transcod er.hpp XMLNetAccessor.hpp XMLNumber.hpp XMLRegisterCleanup.hpp XMLResour UCS4Transcoder.hpp XMLUni.hpp XMLUniDefs.hpp XMLUri.hpp XMLURL.hpp XMLUT der.hpp XML256TableTranscoder.hpp XML88591Transcoder.hpp BaseRefVectorOf KeyValuePair.c NameIdPool.c RefArrayOf.c RefArrayVectorOf.c RefHashTableOf.c f.c RefVectorOf.c TransENameMap.c ValueArrayOf.c ValueHashTableOf.c ValueSta /xerces/xerces-c-src_2_5_0/include/xercesc/util cp: 001-0070 Exception MCH0601 not expected. GMAKE[1]: [pubheaders] Error 1 (ignored) /usr/bin/gmake -C Platforms includes GMAKE[2]: Entering directory `/xerces/xerces250/src/xercesc/util/Platforms' /usr/bin/gmake -C includes GMAKE: Entering an unknown directory GMAKE: *** includes: No such path or directory.. Stop. GMAKE: Leaving an unknown directory GMAKE[2]: *** [includes] Error 2 GMAKE[2]: Leaving directory `/xerces/xerces250/src/xercesc/util/Platforms' GMAKE[1]: *** [includes] Error 2 GMAKE[1]: Leaving directory `/xerces/xerces250/src/xercesc/util' GMAKE: *** [Prepare] Error 2 I'm guessing that the preceding error about the platform is confusing gmake? Any thoughts you have would be appreciated. Patrick -----Original Message----- From: David Cargill [mailto:[EMAIL PROTECTED] Sent: Thursday, April 29, 2004 3:04 AM To: [EMAIL PROTECTED] Subject: RE: AS400, was: z/OS and OS/390 runConfigure ??? 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
