Re: Fw: AIX 32 bit built
Hi,
I assume you actually took traced source. I think this is a mistake on
our part -- it doesn't really make sense to provide trace instrumented
source when the build scripts are capable of instrumenting anyway.
I shall tweak the packaging scripts to ensure future releases don't contain
instrumented source in the source bundle.
Regards,
Adrian
___
Adrian Dick ([EMAIL PROTECTED])
"Antoine Galataud" <[EMAIL PROTECTED]> wrote on 12/04/2006
19:27:29:
> Hi,
>
> thanks a lot for your answer. Effectively, I built Axis with trace
> although it's a traced release (I took AIX-trace-bin, and called ant
> with buildWithTrace) ! I think it's my problem. I will try to test
> that asap, and give you some more feedback.
> The answers to the 2 other questions are respectively no and yes ;-)
>
> Many thanks again !
> 2006/4/12, Fred Preston <[EMAIL PROTECTED]>:
>
> Hi Antoine,
> I've been trying to replicate the problem that you are
> seeing on AIX and I am not having much success. We build and run
> all of the tests on AIX twice a day and do not experience the
> problem you are seeing. I have a couple of questions for you...
>
> Q. Are you running more two identical client application instances
> as this might account for why you are seeing double trace entries.
> Q. Have you somehow built a 'trace' build of Axis on a build that
> already had trace?
> Q. If you hard code the location of the library, it works? (e.g. ...
> // Obtain AXIS deployment path from environment, If not set, we will use
> // default deployment path. Note that default deployment path is the
NULL
> // string unless it is modified.
> sConfPath = getenv ("AXISCPP_DEPLOY"); < Q.
> Do you get the correct value from this getenv?
> if (sConfPath)
> setValue(0,AXCONF_AXISHOME,sConfPath);
>
> // get the value of the path
> // sConfPath = getAxisConfProperty(AXCONF_AXISHOME); < Q.
> What value is actually returned?
> )
>
> Its interesting that the first line of the double trace entry is
> usually correct, but the second is may be wrong. But, although the
> first appears correct, when you try to load the library, both fail.
>
> Regards,
>
> Fred Preston.
>
> "Antoine Galataud" <[EMAIL PROTECTED]>
> 04/04/2006 17:05
>
> Please respond to
> "Apache AXIS C User List"
>
> To
>
> "Apache AXIS C User List"
>
> cc
>
> Subject
>
> Re: AIX 32 bit built
edObject @205e6508
> [04/04/2006 17:52:20:230 DFT] 1 SharedObject < SharedObject @205e6508
> [04/04/2006 17:52:20:230 DFT] 1 RequestScopeHandlerPool >
> RequestScopeHandlerPool @205e6508
> [04/04/2006 17:52:20:230 DFT] 1 RequestScopeHandlerPool >
> RequestScopeHandlerPool @205e6508
> [04/04/2006 17:52:20:230 DFT] 1 RequestScopeHandlerPool <
> RequestScopeHandlerPool @205e6508
> [04/04/2006 17:52:20:230 DFT] 1 RequestScopeHandlerPool <
> RequestScopeHandlerPool @205e6508
> [04/04/2006 17:52:20:230 DFT] 1 SharedObject > SharedObject @205e6598
> [04/04/2006 17:52:20:230 DFT] 1 SharedObject > SharedObject @205e6598
> [04/04/2006 17:52:20:230 DFT] 1 SharedObject < SharedObject @205e6598
> [04/04/2006 17:52:20:230 DFT] 1 SharedObject < SharedObject @205e6598
> [04/04/2006 17:52:20:230 DFT] 1 SessionScopeHandlerPool >
> SessionScopeHandlerPool @205e6598
> [04/04/2006 17:52:20:230 DFT] 1 SessionScopeHandlerPool >
> SessionScopeHandlerPool @205e6598
> [04/04/2006 17:52:20:230 DFT] 1 SessionScopeHandlerPool <
> SessionScopeHandlerPool @205e6598
> [04/04/2006 17:52:20:231 DFT] 1 SessionScopeHandlerPool <
> SessionScopeHandlerPool @205e6598
> [04/04/2006 17:52:20:231 DFT] 1 SharedObject > SharedObject @205e6618
> [04/04/2006 17:52:20:231 DFT] 1 SharedObject > SharedObject @205e6618
> [04/04/2006 17:52:20:231 DFT] 1 SharedObject < SharedObject @205e6618
> [04/04/2006 17:52:20:231 DFT] 1 SharedObject < SharedObject @205e6618
> [04/04/2006 17:52:20:231 DFT] 1 DeserializerPool > DeserializerPool
@205e6618
> [04/04/2006 17:52:20:231 DFT] 1 DeserializerPool > DeserializerPool
@205e6618
> [04/04/2006 17:52:20:231 DFT] 1 DeserializerPool < DeserializerPool
@205e6618
> [04/04/2006 17:52:20:231 DFT] 1 DeserializerPool < DeserializerPool
@205e6618
> [04/04/2006 17:52:20:231 DFT] 1 SharedObject > SharedObject @205e6698
> [04/04/2006 17:52:20:231 DFT] 1 SharedObject > SharedObject @205e6698
> [04/04/2006 17:52:20:231 DFT] 1 SharedObject < SharedObject @205e6698
> [04/04/2006 17:52:20:231 DFT] 1 SharedObject < SharedObject @205e6698
> [04/04/2006 17:52:20:231 DFT] 1 SerializerPool > SerializerPo
Re: AIX 32 bit built
Could you please put start-up trace on and then put the log here pls. AXISCPP_STARTUP_TRACE= "Antoine Galataud" <[EMAIL PROTECTED]> 27/03/2006 09:02 Please respond to "Apache AXIS C User List" To "Apache AXIS C User List" cc Subject Re: AIX 32 bit built Hi It's weird, all environment variables are correctly set in the startup logs. They are really similar to the ones set when I lauch on a solaris machine (and it works on a solaris machine). Any other idea ? Thanks 2006/3/24, Antoine Galataud <[EMAIL PROTECTED]>: That's right, axiscpp.conf file is not processed: if I unset AXISCPP_DEPLOY environment var, then the values outputed in log file (like lib locations and names) are the same. axiscpp.conf file is normally retrieved in $AXISCPP_DEPLOY/etc directory, am I right ? 2006/3/24, John Hawkins <[EMAIL PROTECTED]>: Hmm, looks like your axiscpp_eploy is not being picked up. Check what the trace header file says for any clues. If its not then you can just put the libs in your libpath and they'll get picked up withouth the need for the conf file. "Antoine Galataud" <[EMAIL PROTECTED]> 24/03/2006 10:31 Please respond to "Apache AXIS C User List" <axis-c-user@ws.apache.org> To "Apache AXIS C User List" <axis-c-user@ws.apache.org> cc Subject Re: AIX 32 bit built Hi ! I suceeded in compiling Axis with xerces 2.7.0 version. It worked just fine. Now I'm getting issues at startup, with simple_axis_server or with apache module. The strange thing is that it seems configuration file parser get correctly the values, but then the values are corrupted with something and it produces strange ascii chars (see log output below). Then, it can't load any lib. I'm also wondering if it finds correctly the $AXISCPP_DEPLOY/etc/axiscpp.conf file (it could explain that it can't find any library), because if you look at the logs, it outputed a wrong configuration value for log files location (though I set another value in the axiscpp.conf file) What could be the reasons ? Thanks logs : [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > AxisConfig @205c7ee8,205c5848 [205C5848F008BCC4F008BCD4] < \XH> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > AxisConfig @205c7ee8,205c5848 [205C5848F008BCC4F008BCD4] < \XH> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[] <> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[] <> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@1 [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@1 "¾ïÞ" [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[0001] <> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[0001] <> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@2 "/usr/local/axiscpp_deploy/log/AxisLog" [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@3 "Kÿÿä‚'" [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[0002] <> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[0002] <> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@2 "/usr/local/axiscpp_deploy/log/AxisClientLog" [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@3 "Kÿÿä‚'" [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[0003] <> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[0003] <> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@1 [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@1 "¾ïÞ" [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[0004] <> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[0004] <> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@1 [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@1 "¾ïÞ" [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[0005] <> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[0005] <> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@2 "libhttp_transport.a" [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisC
Re: AIX 32 bit built
HiIt's weird, all environment variables are correctly set in the startup logs. They are really similar to the ones set when I lauch on a solaris machine (and it works on a solaris machine).Any other idea ? Thanks2006/3/24, Antoine Galataud <[EMAIL PROTECTED]>: That's right, axiscpp.conf file is not processed: if I unset AXISCPP_DEPLOY environment var, then the values outputed in log file (like lib locations and names) are the same.axiscpp.conf file is normally retrieved in $AXISCPP_DEPLOY/etc directory, am I right ? 2006/3/24, John Hawkins <[EMAIL PROTECTED]>: Hmm, looks like your axiscpp_eploy is not being picked up. Check what the trace header file says for any clues. If its not then you can just put the libs in your libpath and they'll get picked up withouth the need for the conf file. "Antoine Galataud" <[EMAIL PROTECTED]> 24/03/2006 10:31 Please respond to "Apache AXIS C User List" <axis-c-user@ws.apache.org> To "Apache AXIS C User List" <axis-c-user@ws.apache.org> cc Subject Re: AIX 32 bit built Hi ! I suceeded in compiling Axis with xerces 2.7.0 version. It worked just fine. Now I'm getting issues at startup, with simple_axis_server or with apache module. The strange thing is that it seems configuration file parser get correctly the values, but then the values are corrupted with something and it produces strange ascii chars (see log output below). Then, it can't load any lib. I'm also wondering if it finds correctly the $AXISCPP_DEPLOY/etc/axiscpp.conf file (it could explain that it can't find any library), because if you look at the logs, it outputed a wrong configuration value for log files location (though I set another value in the axiscpp.conf file) What could be the reasons ? Thanks logs : [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > AxisConfig @205c7ee8,205c5848 [205C5848F008BCC4F008BCD4] < \XH> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > AxisConfig @205c7ee8,205c5848 [205C5848F008BCC4F008BCD4] < \XH> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[] <> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[] <> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@1 [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@1 "¾ïÞ" [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[0001] <> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[0001] <> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@2 "/usr/local/axiscpp_deploy/log/AxisLog" [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@3 "Kÿÿä‚'" [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[0002] <> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[0002] <> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@2 "/usr/local/axiscpp_deploy/log/AxisClientLog" [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@3 "Kÿÿä‚'" [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[0003] <> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[0003] <> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@1 [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@1 "¾ïÞ" [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[0004] <> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[0004] <> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@1 [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@1 "¾ïÞ" [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[0005] <> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[0005] <> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@2 "libhttp_transport.a" [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@3 "Kÿÿä‚'" [24/03/2006 11:26:51:271 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[0006] <> [24/03/2006 11:26:51:271 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[0006] <> [24/03/2006 11:26:51:271 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@1 [
Re: AIX 32 bit built
That's right, axiscpp.conf file is not processed: if I unset AXISCPP_DEPLOY environment var, then the values outputed in log file (like lib locations and names) are the same.axiscpp.conf file is normally retrieved in $AXISCPP_DEPLOY/etc directory, am I right ? 2006/3/24, John Hawkins <[EMAIL PROTECTED]>: Hmm, looks like your axiscpp_eploy is not being picked up. Check what the trace header file says for any clues. If its not then you can just put the libs in your libpath and they'll get picked up withouth the need for the conf file. "Antoine Galataud" <[EMAIL PROTECTED]> 24/03/2006 10:31 Please respond to "Apache AXIS C User List" <axis-c-user@ws.apache.org> To "Apache AXIS C User List" <axis-c-user@ws.apache.org> cc Subject Re: AIX 32 bit built Hi ! I suceeded in compiling Axis with xerces 2.7.0 version. It worked just fine. Now I'm getting issues at startup, with simple_axis_server or with apache module. The strange thing is that it seems configuration file parser get correctly the values, but then the values are corrupted with something and it produces strange ascii chars (see log output below). Then, it can't load any lib. I'm also wondering if it finds correctly the $AXISCPP_DEPLOY/etc/axiscpp.conf file (it could explain that it can't find any library), because if you look at the logs, it outputed a wrong configuration value for log files location (though I set another value in the axiscpp.conf file) What could be the reasons ? Thanks logs : [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > AxisConfig @205c7ee8,205c5848 [205C5848F008BCC4F008BCD4] < \XH> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > AxisConfig @205c7ee8,205c5848 [205C5848F008BCC4F008BCD4] < \XH> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[] <> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[] <> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@1 [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@1 "¾ïÞ" [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[0001] <> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[0001] <> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@2 "/usr/local/axiscpp_deploy/log/AxisLog" [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@3 "Kÿÿä‚'" [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[0002] <> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[0002] <> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@2 "/usr/local/axiscpp_deploy/log/AxisClientLog" [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@3 "Kÿÿä‚'" [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[0003] <> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[0003] <> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@1 [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@1 "¾ïÞ" [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[0004] <> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[0004] <> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@1 [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@1 "¾ïÞ" [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[0005] <> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[0005] <> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@2 "libhttp_transport.a" [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@3 "Kÿÿä‚'" [24/03/2006 11:26:51:271 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[0006] <> [24/03/2006 11:26:51:271 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[0006] <> [24/03/2006 11:26:51:271 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@1 [24/03/2006 11:26:51:271 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@1 "¾ïÞ" [24/03/2006 11:26:51:271 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[0007] <> [24/03/2006 11:26:51:271 NFT] 1 AxisConfig > getAxisConfPrope
Re: AIX 32 bit built
Hmm, looks like your axiscpp_eploy is not being picked up. Check what the trace header file says for any clues. If its not then you can just put the libs in your libpath and they'll get picked up withouth the need for the conf file. "Antoine Galataud" <[EMAIL PROTECTED]> 24/03/2006 10:31 Please respond to "Apache AXIS C User List" To "Apache AXIS C User List" cc Subject Re: AIX 32 bit built Hi ! I suceeded in compiling Axis with xerces 2.7.0 version. It worked just fine. Now I'm getting issues at startup, with simple_axis_server or with apache module. The strange thing is that it seems configuration file parser get correctly the values, but then the values are corrupted with something and it produces strange ascii chars (see log output below). Then, it can't load any lib. I'm also wondering if it finds correctly the $AXISCPP_DEPLOY/etc/axiscpp.conf file (it could explain that it can't find any library), because if you look at the logs, it outputed a wrong configuration value for log files location (though I set another value in the axiscpp.conf file) What could be the reasons ? Thanks logs : [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > AxisConfig @205c7ee8,205c5848 [205C5848F008BCC4F008BCD4] < \XH> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > AxisConfig @205c7ee8,205c5848 [205C5848F008BCC4F008BCD4] < \XH> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[] <> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[] <> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@1 [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@1 "¾ïÞ" [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[0001] <> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[0001] <> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@2 "/usr/local/axiscpp_deploy/log/AxisLog" [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@3 "Kÿÿä‚'" [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[0002] <> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[0002] <> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@2 "/usr/local/axiscpp_deploy/log/AxisClientLog" [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@3 "Kÿÿä‚'" [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[0003] <> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[0003] <> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@1 [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@1 "¾ïÞ" [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[0004] <> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[0004] <> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@1 [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@1 "¾ïÞ" [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[0005] <> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[0005] <> [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@2 "libhttp_transport.a" [24/03/2006 11:26:51:270 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@3 "Kÿÿä‚'" [24/03/2006 11:26:51:271 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[0006] <> [24/03/2006 11:26:51:271 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[0006] <> [24/03/2006 11:26:51:271 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@1 [24/03/2006 11:26:51:271 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@1 "¾ïÞ" [24/03/2006 11:26:51:271 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[0007] <> [24/03/2006 11:26:51:271 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[0007] <> [24/03/2006 11:26:51:271 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@2 "libaxis_xmlparser.a" [24/03/2006 11:26:51:271 NFT] 1 AxisConfig < getAxisConfProperty @205c5848,@3 "Kÿÿä‚'" [24/03/2006 11:26:51:271 NFT] 1 AxisConfig > getAxisConfProperty @205c5848,[0008] <> [24/03/2006 11:26:51:271 NFT] 1 Axis
Re: AIX 32 bit built
] 1 AxisConfig > getAxisConfProperty > > @205c7ee8,[0007] <> > > [24/03/2006 11:26:51:272 NFT] 1 AxisConfig > getAxisConfProperty > > @205c7ee8,[0007] <> > > [24/03/2006 11:26:51:272 NFT] 1 AxisConfig < getAxisConfProperty > > @205c7ee8,@2 "Kÿÿä‚'" > > [24/03/2006 11:26:51:272 NFT] 1 AxisConfig < getAxisConfProperty > > @205c7ee8,@3 > > [24/03/2006 11:26:51:272 NFT] 1 XMLParserFactory > loadLib > > [24/03/2006 11:26:51:272 NFT] 1 XMLParserFactory > loadLib > > [24/03/2006 11:26:51:289 NFT] 1 XMLParserFactory < loadLib 0 > > [24/03/2006 11:26:51:289 NFT] 1 XMLParserFactory < loadLib @1 0 > > [24/03/2006 11:26:51:289 NFT] 1 XMLParserFactory > unloadLib > > [24/03/2006 11:26:51:289 NFT] 1 XMLParserFactory > unloadLib > > [24/03/2006 11:26:51:289 NFT] 1 XMLParserFactory < unloadLib 0 > > [24/03/2006 11:26:51:289 NFT] 1 XMLParserFactory < unloadLib @1 540180256 > > > [24/03/2006 11:26:51:289 NFT] 1 AxisEngineException > > > AxisEngineException @2ff20a00,29, "" > > [24/03/2006 11:26:51:289 NFT] 1 AxisEngineException > > > AxisEngineException @2ff20a00,29, "" > > [24/03/2006 11:26:51:289 NFT] 1 AxisEngineException > > > getMessageForExceptionCode @2ff20a00,29 > > [24/03/2006 11:26:51:289 NFT] 1 AxisEngineException > > > getMessageForExceptionCode @2ff20a00,29 > > [24/03/2006 11:26:51:289 NFT] 1 AxisEngineException < > > getMessageForExceptionCode @2ff20a00,"DLOPEN FAILED in loading > > parser library" > > [24/03/2006 11:26:51:289 NFT] 1 AxisEngineException < > > getMessageForExceptionCode @2ff20a00,@1 "" > > [24/03/2006 11:26:51:290 NFT] 1 AxisEngineException > > > getMessageForExceptionCode @2ff20a00,29 > > [24/03/2006 11:26:51:290 NFT] 1 AxisEngineException > > > getMessageForExceptionCode @2ff20a00,29 > > [24/03/2006 11:26:51:290 NFT] 1 AxisEngineException < > > getMessageForExceptionCode @2ff20a00,"DLOPEN FAILED in loading parser > library" > > [24/03/2006 11:26:51:290 NFT] 1 AxisEngineException < > > getMessageForExceptionCode @2ff20a00,@1 "" > > [24/03/2006 11:26:51:290 NFT] 1 AxisEngineException < > > AxisEngineException @2ff20a00 > > [24/03/2006 11:26:51:290 NFT] 1 AxisEngineException < > > AxisEngineException @2ff20a00 > > [24/03/2006 11:26:51:290 NFT] 1 - X initialize_module @1 caught > > AxisException( , " ") > > [24/03/2006 11:26:51:290 NFT] 1 - X initialize_module @1 caught > > AxisException( , " ") > > [24/03/2006 11:26:51:290 NFT] 1 AxisEngineException > > > AxisEngineException @2ff20b18,29, " " > > [24/03/2006 11:26:51:290 NFT] 1 AxisEngineException > > > AxisEngineException @2ff20b18,29, " " > > [24/03/2006 11:26:51:290 NFT] 1 AxisEngineException > > > getMessageForExceptionCode @2ff20b18,29 > > [24/03/2006 11:26:51:290 NFT] 1 AxisEngineException > > > getMessageForExceptionCode @2ff20b18,29 > > [24/03/2006 11:26:51:290 NFT] 1 AxisEngineException < > > getMessageForExceptionCode @2ff20b18,"DLOPEN FAILED in loading > > parser library" > > [24/03/2006 11:26:51:290 NFT] 1 AxisEngineException < > > getMessageForExceptionCode @2ff20b18,@1 "" > > [24/03/2006 11:26:51:290 NFT] 1 AxisEngineException > > > getMessageForExceptionCode @2ff20b18,29 > > [24/03/2006 11:26:51:290 NFT] 1 AxisEngineException > > > getMessageForExceptionCode @2ff20b18,29 > > [24/03/2006 11:26:51:290 NFT] 1 AxisEngineException < > > getMessageForExceptionCode @2ff20b18,"DLOPEN FAILED in loading parser > library" > > [24/03/2006 11:26:51:290 NFT] 1 AxisEngineException < > > getMessageForExceptionCode @2ff20b18,@1 "" > > [24/03/2006 11:26:51:290 NFT] 1 AxisEngineException < > > AxisEngineException @2ff20b18 > > > 2006/3/22, John Hawkins <[EMAIL PROTECTED]>: > > > > Nope. Because we're upgrading to a new version of xerces we need to > > do this across all platforms and we're having problems against > > simple-axis server on windows. > > > > Can you build it yourself on aix? It might be quicker for you. > > > > > > > > > > > > > > > "Antoine Galataud" <[EMAIL PROTECTED]> > > 22/03/2006 17:23 > > > > Please respond to > > "Apache AXIS C User List" > > > > To > > > > "Apache AXIS C User List" > > > > cc > > > > Subject > > > > Re: AIX 32 bit built > >
Re: AIX 32 bit built
ption > > AxisEngineException @2ff20a00,29, "" > [24/03/2006 11:26:51:289 NFT] 1 AxisEngineException > > AxisEngineException @2ff20a00,29, "" > [24/03/2006 11:26:51:289 NFT] 1 AxisEngineException > > getMessageForExceptionCode @2ff20a00,29 > [24/03/2006 11:26:51:289 NFT] 1 AxisEngineException > > getMessageForExceptionCode @2ff20a00,29 > [24/03/2006 11:26:51:289 NFT] 1 AxisEngineException < > getMessageForExceptionCode @2ff20a00,"DLOPEN FAILED in loading > parser library" > [24/03/2006 11:26:51:289 NFT] 1 AxisEngineException < > getMessageForExceptionCode @2ff20a00,@1 "" > [24/03/2006 11:26:51:290 NFT] 1 AxisEngineException > > getMessageForExceptionCode @2ff20a00,29 > [24/03/2006 11:26:51:290 NFT] 1 AxisEngineException > > getMessageForExceptionCode @2ff20a00,29 > [24/03/2006 11:26:51:290 NFT] 1 AxisEngineException < > getMessageForExceptionCode @2ff20a00,"DLOPEN FAILED in loading parser library" > [24/03/2006 11:26:51:290 NFT] 1 AxisEngineException < > getMessageForExceptionCode @2ff20a00,@1 "" > [24/03/2006 11:26:51:290 NFT] 1 AxisEngineException < > AxisEngineException @2ff20a00 > [24/03/2006 11:26:51:290 NFT] 1 AxisEngineException < > AxisEngineException @2ff20a00 > [24/03/2006 11:26:51:290 NFT] 1 - X initialize_module @1 caught > AxisException( , " ") > [24/03/2006 11:26:51:290 NFT] 1 - X initialize_module @1 caught > AxisException( , " ") > [24/03/2006 11:26:51:290 NFT] 1 AxisEngineException > > AxisEngineException @2ff20b18,29, " " > [24/03/2006 11:26:51:290 NFT] 1 AxisEngineException > > AxisEngineException @2ff20b18,29, " " > [24/03/2006 11:26:51:290 NFT] 1 AxisEngineException > > getMessageForExceptionCode @2ff20b18,29 > [24/03/2006 11:26:51:290 NFT] 1 AxisEngineException > > getMessageForExceptionCode @2ff20b18,29 > [24/03/2006 11:26:51:290 NFT] 1 AxisEngineException < > getMessageForExceptionCode @2ff20b18,"DLOPEN FAILED in loading > parser library" > [24/03/2006 11:26:51:290 NFT] 1 AxisEngineException < > getMessageForExceptionCode @2ff20b18,@1 "" > [24/03/2006 11:26:51:290 NFT] 1 AxisEngineException > > getMessageForExceptionCode @2ff20b18,29 > [24/03/2006 11:26:51:290 NFT] 1 AxisEngineException > > getMessageForExceptionCode @2ff20b18,29 > [24/03/2006 11:26:51:290 NFT] 1 AxisEngineException < > getMessageForExceptionCode @2ff20b18,"DLOPEN FAILED in loading parser library" > [24/03/2006 11:26:51:290 NFT] 1 AxisEngineException < > getMessageForExceptionCode @2ff20b18,@1 "" > [24/03/2006 11:26:51:290 NFT] 1 AxisEngineException < > AxisEngineException @2ff20b18 > 2006/3/22, John Hawkins <[EMAIL PROTECTED]>: > > Nope. Because we're upgrading to a new version of xerces we need to > do this across all platforms and we're having problems against > simple-axis server on windows. > > Can you build it yourself on aix? It might be quicker for you. > > > > > > > "Antoine Galataud" <[EMAIL PROTECTED]> > 22/03/2006 17:23 > > Please respond to > "Apache AXIS C User List" > > To > > "Apache AXIS C User List" > > cc > > Subject > > Re: AIX 32 bit built > > > > > Hi ! > > So, is this release ready for download ? > > Thanks > > 2006/3/21, Antoine Galataud <[EMAIL PROTECTED] >: > Thanks a lot ! > > 2006/3/21, John Hawkins < [EMAIL PROTECTED]>: > > Xerces 2.7 worked fine. > > We'll upgrade the build to use this asap. > > > > > > "Antoine Galataud" <[EMAIL PROTECTED] > > 21/03/2006 08:54 > > Please respond to > "Apache AXIS C User List" > > To > > "Apache AXIS C User List" > > cc > > Subject > > Re: AIX 32 bit built > > > > > > > > Hi, > > It could be great to upgrade binaries on website, so a end-user can > take it, develop, and run. In my opinion, you should provide both > source and binary release, and giving advice about how to compile > correctly the source one. > For the binary release, it could be easier to have a built version in > accordance with the xerces binary release (it seams logical). > > Thanks for your answer. > 2006/3/20, John Hawkins <[EMAIL PROTECTED] >: > > > > Hi Folks, > > > > Quite a few people have been having trouble with the aix binaries we've got > > on the site at the moment (and we thought we were doing everyone a favour > > ;-) > > > > > > > > Looks like the issue with the aix 32 bit build is this: > > > > The xerces build on the apache website was built using xmlC 5.*. The machine > > that we build the aix release code on uses 6.* and so we compiled xerces to > > use that compiler level also. Therefore, what we are seeing is the > > incompatibility of name mangling (or compiler options) between compiler > > levels. > > > > Given that I don't know how to get around this issue i.e. tell the xlc at > > 6.* level to mangle the same somehow (or use the same options?) We have two > > ways forward either > > a) Compile your own version of xerces 2_2_0 for AIX using xlc 6.* > > b) We'll also look into upgrading the version of xerces to be the latest and > > the binaries for this already use xlc 6.* > > > > > > I'll get back to you on how well the tests go for option b) but you can > > always continue with option a) yourselves :-) > > > > cheers for now, > > John. > > > -- > Antoine Galataud > [EMAIL PROTECTED] > Département Architecture des Systèmes d'Information > INSA - Rouen > > > > > -- > > Antoine Galataud > [EMAIL PROTECTED] > Département Architecture des Systèmes d'Information > INSA - Rouen > > > > -- > Antoine Galataud > [EMAIL PROTECTED] > Département Architecture des Systèmes d'Information > INSA - Rouen > > > > -- > Antoine Galataud > [EMAIL PROTECTED] > Département Architecture des Systèmes d'Information > INSA - Rouen
Re: AIX 32 bit built
4/03/2006 11:26:51:290 NFT] 1 - X initialize_module @1 caught AxisException( , " ") [24/03/2006 11:26:51:290 NFT] 1 - X initialize_module @1 caught AxisException( , " ")[24/03/2006 11:26:51:290 NFT] 1 AxisEngineException > AxisEngineException @2ff20b18,29, " "[24/03/2006 11:26:51:290 NFT] 1 AxisEngineException > AxisEngineException @2ff20b18,29, " " [24/03/2006 11:26:51:290 NFT] 1 AxisEngineException > getMessageForExceptionCode @2ff20b18,29[24/03/2006 11:26:51:290 NFT] 1 AxisEngineException > getMessageForExceptionCode @2ff20b18,29[24/03/2006 11:26:51:290 NFT] 1 AxisEngineException < getMessageForExceptionCode @2ff20b18,"DLOPEN FAILED in loading parser library" [24/03/2006 11:26:51:290 NFT] 1 AxisEngineException < getMessageForExceptionCode @2ff20b18,@1 ""[24/03/2006 11:26:51:290 NFT] 1 AxisEngineException > getMessageForExceptionCode @2ff20b18,29[24/03/2006 11:26:51:290 NFT] 1 AxisEngineException > getMessageForExceptionCode @2ff20b18,29 [24/03/2006 11:26:51:290 NFT] 1 AxisEngineException < getMessageForExceptionCode @2ff20b18,"DLOPEN FAILED in loading parser library"[24/03/2006 11:26:51:290 NFT] 1 AxisEngineException < getMessageForExceptionCode @2ff20b18,@1 "" [24/03/2006 11:26:51:290 NFT] 1 AxisEngineException < AxisEngineException @2ff20b182006/3/22, John Hawkins <[EMAIL PROTECTED]>: Nope. Because we're upgrading to a new version of xerces we need to do this across all platforms and we're having problems against simple-axis server on windows. Can you build it yourself on aix? It might be quicker for you. "Antoine Galataud" <[EMAIL PROTECTED]> 22/03/2006 17:23 Please respond to "Apache AXIS C User List" <axis-c-user@ws.apache.org> To "Apache AXIS C User List" <axis-c-user@ws.apache.org> cc Subject Re: AIX 32 bit built Hi ! So, is this release ready for download ? Thanks 2006/3/21, Antoine Galataud <[EMAIL PROTECTED] >: Thanks a lot ! 2006/3/21, John Hawkins < [EMAIL PROTECTED]>: Xerces 2.7 worked fine. We'll upgrade the build to use this asap. "Antoine Galataud" <[EMAIL PROTECTED] > 21/03/2006 08:54 Please respond to "Apache AXIS C User List" <axis-c-user@ws.apache.org > To "Apache AXIS C User List" <axis-c-user@ws.apache.org > cc Subject Re: AIX 32 bit built Hi, It could be great to upgrade binaries on website, so a end-user can take it, develop, and run. In my opinion, you should provide both source and binary release, and giving advice about how to compile correctly the source one. For the binary release, it could be easier to have a built version in accordance with the xerces binary release (it seams logical). Thanks for your answer. 2006/3/20, John Hawkins <[EMAIL PROTECTED] >: > > Hi Folks, > > Quite a few people have been having trouble with the aix binaries we've got > on the site at the moment (and we thought we were doing everyone a favour > ;-) > > > > Looks like the issue with the aix 32 bit build is this: > > The xerces build on the apache website was built using xmlC 5.*. The machine > that we build the aix release code on uses 6.* and so we compiled xerces to > use that compiler level also. Therefore, what we are seeing is the > incompatibility of name mangling (or compiler options) between compiler > levels. > > Given that I don't know how to get around this issue i.e. tell the xlc at > 6.* level to mangle the same somehow (or use the same options?) We have two > ways forward either > a) Compile your own version of xerces 2_2_0 for AIX using xlc 6.* > b) We'll also look into upgrading the version of xerces to be the latest and > the binaries for this already use xlc 6.* > > > I'll get back to you on how well the tests go for option b) but you can > always continue with option a) yourselves :-) > > cheers for now, > John. -- Antoine Galataud [EMAIL PROTECTED] Département Architecture des Systèmes d'Information INSA - Rouen -- Antoine Galataud [EMAIL PROTECTED] Département Architecture des Systèmes d'Information INSA - Rouen -- Antoine Galataud [EMAIL PROTECTED] Département Architecture des Systèmes d'Information INSA - Rouen -- Antoine Galataud[EMAIL PROTECTED]Département Architecture des Systèmes d'InformationINSA - Rouen
Re: AIX 32 bit built
Nope. Because we're upgrading to a new version of xerces we need to do this across all platforms and we're having problems against simple-axis server on windows. Can you build it yourself on aix? It might be quicker for you. "Antoine Galataud" <[EMAIL PROTECTED]> 22/03/2006 17:23 Please respond to "Apache AXIS C User List" To "Apache AXIS C User List" cc Subject Re: AIX 32 bit built Hi ! So, is this release ready for download ? Thanks 2006/3/21, Antoine Galataud <[EMAIL PROTECTED]>: Thanks a lot ! 2006/3/21, John Hawkins < [EMAIL PROTECTED]>: Xerces 2.7 worked fine. We'll upgrade the build to use this asap. "Antoine Galataud" <[EMAIL PROTECTED]> 21/03/2006 08:54 Please respond to "Apache AXIS C User List" <axis-c-user@ws.apache.org> To "Apache AXIS C User List" <axis-c-user@ws.apache.org> cc Subject Re: AIX 32 bit built Hi, It could be great to upgrade binaries on website, so a end-user can take it, develop, and run. In my opinion, you should provide both source and binary release, and giving advice about how to compile correctly the source one. For the binary release, it could be easier to have a built version in accordance with the xerces binary release (it seams logical). Thanks for your answer. 2006/3/20, John Hawkins <[EMAIL PROTECTED]>: > > Hi Folks, > > Quite a few people have been having trouble with the aix binaries we've got > on the site at the moment (and we thought we were doing everyone a favour > ;-) > > > > Looks like the issue with the aix 32 bit build is this: > > The xerces build on the apache website was built using xmlC 5.*. The machine > that we build the aix release code on uses 6.* and so we compiled xerces to > use that compiler level also. Therefore, what we are seeing is the > incompatibility of name mangling (or compiler options) between compiler > levels. > > Given that I don't know how to get around this issue i.e. tell the xlc at > 6.* level to mangle the same somehow (or use the same options?) We have two > ways forward either > a) Compile your own version of xerces 2_2_0 for AIX using xlc 6.* > b) We'll also look into upgrading the version of xerces to be the latest and > the binaries for this already use xlc 6.* > > > I'll get back to you on how well the tests go for option b) but you can > always continue with option a) yourselves :-) > > cheers for now, > John. -- Antoine Galataud [EMAIL PROTECTED] Département Architecture des Systèmes d'Information INSA - Rouen -- Antoine Galataud [EMAIL PROTECTED] Département Architecture des Systèmes d'Information INSA - Rouen -- Antoine Galataud [EMAIL PROTECTED] Département Architecture des Systèmes d'Information INSA - Rouen
Re: AIX 32 bit built
Hi !So, is this release ready for download ?Thanks2006/3/21, Antoine Galataud <[EMAIL PROTECTED]>: Thanks a lot !2006/3/21, John Hawkins < [EMAIL PROTECTED]>: Xerces 2.7 worked fine. We'll upgrade the build to use this asap. "Antoine Galataud" <[EMAIL PROTECTED]> 21/03/2006 08:54 Please respond to "Apache AXIS C User List" <axis-c-user@ws.apache.org> To "Apache AXIS C User List" <axis-c-user@ws.apache.org> cc Subject Re: AIX 32 bit built Hi, It could be great to upgrade binaries on website, so a end-user can take it, develop, and run. In my opinion, you should provide both source and binary release, and giving advice about how to compile correctly the source one. For the binary release, it could be easier to have a built version in accordance with the xerces binary release (it seams logical). Thanks for your answer. 2006/3/20, John Hawkins <[EMAIL PROTECTED]>: > > Hi Folks, > > Quite a few people have been having trouble with the aix binaries we've got > on the site at the moment (and we thought we were doing everyone a favour > ;-) > > > > Looks like the issue with the aix 32 bit build is this: > > The xerces build on the apache website was built using xmlC 5.*. The machine > that we build the aix release code on uses 6.* and so we compiled xerces to > use that compiler level also. Therefore, what we are seeing is the > incompatibility of name mangling (or compiler options) between compiler > levels. > > Given that I don't know how to get around this issue i.e. tell the xlc at > 6.* level to mangle the same somehow (or use the same options?) We have two > ways forward either > a) Compile your own version of xerces 2_2_0 for AIX using xlc 6.* > b) We'll also look into upgrading the version of xerces to be the latest and > the binaries for this already use xlc 6.* > > > I'll get back to you on how well the tests go for option b) but you can > always continue with option a) yourselves :-) > > cheers for now, > John. -- Antoine Galataud [EMAIL PROTECTED] Département Architecture des Systèmes d'Information INSA - Rouen -- Antoine Galataud [EMAIL PROTECTED]Département Architecture des Systèmes d'InformationINSA - Rouen -- Antoine Galataud[EMAIL PROTECTED]Département Architecture des Systèmes d'InformationINSA - Rouen
Re: AIX 32 bit built
Thanks a lot !2006/3/21, John Hawkins <[EMAIL PROTECTED]>: Xerces 2.7 worked fine. We'll upgrade the build to use this asap. "Antoine Galataud" <[EMAIL PROTECTED]> 21/03/2006 08:54 Please respond to "Apache AXIS C User List" <axis-c-user@ws.apache.org> To "Apache AXIS C User List" <axis-c-user@ws.apache.org> cc Subject Re: AIX 32 bit built Hi, It could be great to upgrade binaries on website, so a end-user can take it, develop, and run. In my opinion, you should provide both source and binary release, and giving advice about how to compile correctly the source one. For the binary release, it could be easier to have a built version in accordance with the xerces binary release (it seams logical). Thanks for your answer. 2006/3/20, John Hawkins <[EMAIL PROTECTED]>: > > Hi Folks, > > Quite a few people have been having trouble with the aix binaries we've got > on the site at the moment (and we thought we were doing everyone a favour > ;-) > > > > Looks like the issue with the aix 32 bit build is this: > > The xerces build on the apache website was built using xmlC 5.*. The machine > that we build the aix release code on uses 6.* and so we compiled xerces to > use that compiler level also. Therefore, what we are seeing is the > incompatibility of name mangling (or compiler options) between compiler > levels. > > Given that I don't know how to get around this issue i.e. tell the xlc at > 6.* level to mangle the same somehow (or use the same options?) We have two > ways forward either > a) Compile your own version of xerces 2_2_0 for AIX using xlc 6.* > b) We'll also look into upgrading the version of xerces to be the latest and > the binaries for this already use xlc 6.* > > > I'll get back to you on how well the tests go for option b) but you can > always continue with option a) yourselves :-) > > cheers for now, > John. -- Antoine Galataud [EMAIL PROTECTED] Département Architecture des Systèmes d'Information INSA - Rouen -- Antoine Galataud[EMAIL PROTECTED]Département Architecture des Systèmes d'InformationINSA - Rouen
Re: AIX 32 bit built
Xerces 2.7 worked fine. We'll upgrade the build to use this asap. "Antoine Galataud" <[EMAIL PROTECTED]> 21/03/2006 08:54 Please respond to "Apache AXIS C User List" To "Apache AXIS C User List" cc Subject Re: AIX 32 bit built Hi, It could be great to upgrade binaries on website, so a end-user can take it, develop, and run. In my opinion, you should provide both source and binary release, and giving advice about how to compile correctly the source one. For the binary release, it could be easier to have a built version in accordance with the xerces binary release (it seams logical). Thanks for your answer. 2006/3/20, John Hawkins <[EMAIL PROTECTED]>: > > Hi Folks, > > Quite a few people have been having trouble with the aix binaries we've got > on the site at the moment (and we thought we were doing everyone a favour > ;-) > > > > Looks like the issue with the aix 32 bit build is this: > > The xerces build on the apache website was built using xmlC 5.*. The machine > that we build the aix release code on uses 6.* and so we compiled xerces to > use that compiler level also. Therefore, what we are seeing is the > incompatibility of name mangling (or compiler options) between compiler > levels. > > Given that I don't know how to get around this issue i.e. tell the xlc at > 6.* level to mangle the same somehow (or use the same options?) We have two > ways forward either > a) Compile your own version of xerces 2_2_0 for AIX using xlc 6.* > b) We'll also look into upgrading the version of xerces to be the latest and > the binaries for this already use xlc 6.* > > > I'll get back to you on how well the tests go for option b) but you can > always continue with option a) yourselves :-) > > cheers for now, > John. -- Antoine Galataud [EMAIL PROTECTED] Département Architecture des Systèmes d'Information INSA - Rouen
Re: AIX 32 bit built
Hi, It could be great to upgrade binaries on website, so a end-user can take it, develop, and run. In my opinion, you should provide both source and binary release, and giving advice about how to compile correctly the source one. For the binary release, it could be easier to have a built version in accordance with the xerces binary release (it seams logical). Thanks for your answer. 2006/3/20, John Hawkins <[EMAIL PROTECTED]>: > > Hi Folks, > > Quite a few people have been having trouble with the aix binaries we've got > on the site at the moment (and we thought we were doing everyone a favour > ;-) > > > > Looks like the issue with the aix 32 bit build is this: > > The xerces build on the apache website was built using xmlC 5.*. The machine > that we build the aix release code on uses 6.* and so we compiled xerces to > use that compiler level also. Therefore, what we are seeing is the > incompatibility of name mangling (or compiler options) between compiler > levels. > > Given that I don't know how to get around this issue i.e. tell the xlc at > 6.* level to mangle the same somehow (or use the same options?) We have two > ways forward either > a) Compile your own version of xerces 2_2_0 for AIX using xlc 6.* > b) We'll also look into upgrading the version of xerces to be the latest and > the binaries for this already use xlc 6.* > > > I'll get back to you on how well the tests go for option b) but you can > always continue with option a) yourselves :-) > > cheers for now, > John. -- Antoine Galataud [EMAIL PROTECTED] Département Architecture des Systèmes d'Information INSA - Rouen
AIX 32 bit built
Hi Folks, Quite a few people have been having trouble with the aix binaries we've got on the site at the moment (and we thought we were doing everyone a favour ;-) Looks like the issue with the aix 32 bit build is this: The xerces build on the apache website was built using xmlC 5.*. The machine that we build the aix release code on uses 6.* and so we compiled xerces to use that compiler level also. Therefore, what we are seeing is the incompatibility of name mangling (or compiler options) between compiler levels. Given that I don't know how to get around this issue i.e. tell the xlc at 6.* level to mangle the same somehow (or use the same options?) We have two ways forward either a) Compile your own version of xerces 2_2_0 for AIX using xlc 6.* b) We'll also look into upgrading the version of xerces to be the latest and the binaries for this already use xlc 6.* I'll get back to you on how well the tests go for option b) but you can always continue with option a) yourselves :-) cheers for now, John.
