You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by Chris Darroch <ch...@pearsoncmg.com> on 2007/05/01 07:11:19 UTC
Re: [Vote] [Axis2] Vote for Apache Axis2/C 1.0.0 Release
Samisa Abeysinghe wrote:
> Please test, review and vote on the release artifacts for Apache
> Axis2/C 1.0.0 release.
If you can bear with me for a few days, I'll try to do a bit more
testing, but here are a few initial notes:
First, the include files look so nice and clean! Thank you! On
first glance the library filenames, httpd config directives, and
general layout seem clean and clear -- again, thank you!
Second, I thought I might revise the main INSTALL and configure files a
little to explain certain parameters to configure a bit better. In
particular, the --with-apr and --with-apache2 options mostly don't mention
what kind of path they take: to the "prefix" that was used to install those
packages? To their lib directories? In fact, they both take paths to the
include directories of those packages.
I can't remember if Axis2/C actually needs anything except the httpd
include files ... maybe not. I can't see anything offhand that ldd
shows as having links to their libraries. That would be easier, if true!
(If anything does link against their libraries, though, I think the
Axis2/C configure script might need to get paths for both their include
and library directories. For example, if someone installs httpd using
its --enable-layout option (see the config.layout file in the httpd source
package for details), they have a lot of control over where the
libraries end up: not necessarily in $prefix/lib, next to $prefix/include.
Anyway, my dim memory is that, in fact, Axis2/C doesn't link against
the APR and httpd libraries, so all of this is moot.)
The INSTALL file does explain that --with-apr takes the include
path for APR, however, it doesn't say the same thing about the
--with-apache2 option.
And if you run ./configure --help, you just get:
--with-apache2=PATH use apache2 as server transport.
--with-apr=PATH use apr.
Compare with the following from APR-util configure --help:
--with-berkeley-db=PATH
Find the Berkeley DB header and library in 'PATH/include' and
'PATH/lib'. If PATH is of the form 'HEADER:LIB', then search
for header files in HEADER, and the library in LIB. If you omit
the '=PATH' part completely, the configure script will search
for Berkeley DB in a number of standard places.
So if you can wait a few days, I can edit these a little bit
(or someone else can, of course!)
For example, I was able to successfully build Axis2/C with the
following:
CFLAGS=-I$PREFIX/package/include LDFLAGS=-L$PREFIX/package/lib \
./configure --enable-tests \
--prefix=/tmp/chrisd_build/axis2c \
--with-apr=$PREFIX/package/include/apr-1 \
--with-apache2=$PREFIX/package/include/apache2
Next, the samples ./configure script and INSTALL files should
explain that they need the full path to the Axis2/C include directories,
or else they should append the axis2-1.0 subdirectory automatically.
(BTW, thanks for that versioned subdir!) The ./configure --help
option just says:
--with-axiom=PATH use axiom.
--with-axis2_util=PATH use axis2_util.
Also, the main INSTALL file (not the samples one) says:
> To build the samples:
>
> export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/axis2c/lib/
> cd samples
> ./configure --prefix=${AXIS2C_HOME}
> --with-axis2_util=${AXIS2C_HOME}/include
> --with-axiom=${AXIS2C_HOME}/include
Here's what I had to use to successfully build the samples; note
the axis2-1.0 subdirectories:
LDFLAGS=-L/tmp/chrisd_build/axis2c/lib \
./configure --prefix=/tmp/chrisd_build/axis2c \
--with-axis2_util=/tmp/chrisd_build/axis2c/include/axis2-1.0 \
--with-axiom=/tmp/chrisd_build/axis2c/include/axis2-1.0
Again, if you can wait a few days, I can edit these, or someone
else can certainly tackle it.
Third, the "make check" option isn't quite working right yet,
I think. Running in the source package, you get a segfault right
away unless you have AXIS2C_HOME=/path/to/source/axis2c/package.
(I tried running "make install" and then setting AXIS2C_HOME
to point to the installation location, but it doesn't seem to like
that; you need to pointing to the source package.) The INSTALL
file suggests you'll need AXIS2C_HOME=/path/to/install/axis2c/package
but I'm not sure that's correct.
With it set, more of the tests run fine, but I'm getting a segfault
on test/core/clientapi/test_clientapi. It occurs within the call
to axis2_svc_client_set_options(svc_client, env, options) somewhere
in test_clientapi.c. That's as far I'm likely to get for a day or
so, I fear.
But, overall, looking really nice! Thanks again,
Chris.
--
GPG Key ID: 366A375B
GPG Key Fingerprint: 485E 5041 17E1 E2BB C263 E4DE C8E3 FA36 366A 375B
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
Re: [Vote] [Axis2] Vote for Apache Axis2/C 1.0.0 Release
Posted by Samisa Abeysinghe <sa...@wso2.com>.
Hi Chris,
Many thanks for your valuable feedback. I was about to send out the
release note out, when I saw your mail, you were just in time.
I have fixed the issues you pointed out on the 1.0.0 tag. Will have
to package the release artifacts again. Plan to send out the notice at
the end of day Wednesday after testing.
Thanks,
Samisa...
Chris Darroch wrote:
>Samisa Abeysinghe wrote:
>
>
>
>> Please test, review and vote on the release artifacts for Apache
>>Axis2/C 1.0.0 release.
>>
>>
>
> If you can bear with me for a few days, I'll try to do a bit more
>testing, but here are a few initial notes:
>
>
> First, the include files look so nice and clean! Thank you! On
>first glance the library filenames, httpd config directives, and
>general layout seem clean and clear -- again, thank you!
>
>
> Second, I thought I might revise the main INSTALL and configure files a
>little to explain certain parameters to configure a bit better. In
>particular, the --with-apr and --with-apache2 options mostly don't mention
>what kind of path they take: to the "prefix" that was used to install those
>packages? To their lib directories? In fact, they both take paths to the
>include directories of those packages.
>
> I can't remember if Axis2/C actually needs anything except the httpd
>include files ... maybe not. I can't see anything offhand that ldd
>shows as having links to their libraries. That would be easier, if true!
>
> (If anything does link against their libraries, though, I think the
>Axis2/C configure script might need to get paths for both their include
>and library directories. For example, if someone installs httpd using
>its --enable-layout option (see the config.layout file in the httpd source
>package for details), they have a lot of control over where the
>libraries end up: not necessarily in $prefix/lib, next to $prefix/include.
>Anyway, my dim memory is that, in fact, Axis2/C doesn't link against
>the APR and httpd libraries, so all of this is moot.)
>
> The INSTALL file does explain that --with-apr takes the include
>path for APR, however, it doesn't say the same thing about the
>--with-apache2 option.
>
> And if you run ./configure --help, you just get:
>
> --with-apache2=PATH use apache2 as server transport.
> --with-apr=PATH use apr.
>
> Compare with the following from APR-util configure --help:
>
> --with-berkeley-db=PATH
> Find the Berkeley DB header and library in 'PATH/include' and
> 'PATH/lib'. If PATH is of the form 'HEADER:LIB', then search
> for header files in HEADER, and the library in LIB. If you omit
> the '=PATH' part completely, the configure script will search
> for Berkeley DB in a number of standard places.
>
> So if you can wait a few days, I can edit these a little bit
>(or someone else can, of course!)
>
> For example, I was able to successfully build Axis2/C with the
>following:
>
>CFLAGS=-I$PREFIX/package/include LDFLAGS=-L$PREFIX/package/lib \
> ./configure --enable-tests \
> --prefix=/tmp/chrisd_build/axis2c \
> --with-apr=$PREFIX/package/include/apr-1 \
> --with-apache2=$PREFIX/package/include/apache2
>
>
> Next, the samples ./configure script and INSTALL files should
>explain that they need the full path to the Axis2/C include directories,
>or else they should append the axis2-1.0 subdirectory automatically.
>(BTW, thanks for that versioned subdir!) The ./configure --help
>option just says:
>
> --with-axiom=PATH use axiom.
> --with-axis2_util=PATH use axis2_util.
>
> Also, the main INSTALL file (not the samples one) says:
>
>
>
>> To build the samples:
>>
>> export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/axis2c/lib/
>> cd samples
>> ./configure --prefix=${AXIS2C_HOME}
>> --with-axis2_util=${AXIS2C_HOME}/include
>> --with-axiom=${AXIS2C_HOME}/include
>>
>>
>
> Here's what I had to use to successfully build the samples; note
>the axis2-1.0 subdirectories:
>
>LDFLAGS=-L/tmp/chrisd_build/axis2c/lib \
> ./configure --prefix=/tmp/chrisd_build/axis2c \
> --with-axis2_util=/tmp/chrisd_build/axis2c/include/axis2-1.0 \
> --with-axiom=/tmp/chrisd_build/axis2c/include/axis2-1.0
>
> Again, if you can wait a few days, I can edit these, or someone
>else can certainly tackle it.
>
>
> Third, the "make check" option isn't quite working right yet,
>I think. Running in the source package, you get a segfault right
>away unless you have AXIS2C_HOME=/path/to/source/axis2c/package.
>(I tried running "make install" and then setting AXIS2C_HOME
>to point to the installation location, but it doesn't seem to like
>that; you need to pointing to the source package.) The INSTALL
>file suggests you'll need AXIS2C_HOME=/path/to/install/axis2c/package
>but I'm not sure that's correct.
>
> With it set, more of the tests run fine, but I'm getting a segfault
>on test/core/clientapi/test_clientapi. It occurs within the call
>to axis2_svc_client_set_options(svc_client, env, options) somewhere
>in test_clientapi.c. That's as far I'm likely to get for a day or
>so, I fear.
>
>
> But, overall, looking really nice! Thanks again,
>
>Chris.
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
Re: [Vote] [Axis2] Vote for Apache Axis2/C 1.0.0 Release
Posted by Samisa Abeysinghe <sa...@wso2.com>.
Given that we fixed several issues and re-packaged the artifacts several
time, we should call the fresh vote on the release artifacts.
So I would start a new vote as soon as the new artifacts are ready.
Thanks,
Samisa...
Samisa Abeysinghe wrote:
> Fixed both the issues.
>
> Thanks,
> Samisa...
>
> Chris Darroch wrote:
>> Samisa:
>>
>>
>>> The latest, and final, artifacts are uploaded here:
>>> http://people.apache.org/~samisa/release/1.0.0/final/
>>>
>>> Please test. I plan to send the release note in about 12 hours form
>>> now.
>>>
>>> I have tested all the sources and binaries successfully.
>>>
>>
>> Thanks for all the quick fixes! The configure --help notes and
>> the INSTALL files are much clearer. I successfully built and
>> installed and tested with --enable-tests, and with the samples
>> directory.
>>
>> Two things, one small, one maybe not:
>>
>> The small thing is that is seems like the
>> test/core/clientapi/test_clientapi program fails (with a message now,
>> thank you!) unless AXIS2C_HOME points to the installed location.
>> (I'm guessing it's looking for axis2.xml.) This means you really
>> should run "make && make install", then set
>> AXIS2C_HOME=/path/to/install,
>> and then "make check". That's a little different than the usual
>> "make && make check && make install" process.
>>
>> We should perhaps make that clean in the main INSTALL file, or else
>> alter test_clientapi.c somehow so that it will work if you set
>> AXIS2C_HOME=/path/to/source or something. Then the more
>> typical "check then install" process would function, so long as you
>> had AXIS2C_HOME set to the location of the Axis2/C sources.
>>
>>
>> The maybe not-so-small thing is that for me, at least, on an
>> older RedHat Linux box, util/test/util/test_thread fails sometimes
>> and not other times. That feels like a race condition problem to me.
>> (This is regardless of what AXIS2C_HOME is set to, or even if it's
>> unset; that was a red herring in my previous email.)
>>
>> Here's the output from an unsuccessful run:
>>
>> success - thread_init - axutil_thread_once_init success - thread_init
>> - axutil_thread_mutex_create success - test_axutil_thread_create -
>> axutil_thread_create success - test_axutil_thread_create -
>> axutil_thread_create thread data = 5 x = 1 thread data = 25 x = 2
>> success - test_axutil_thread_create - axutil_thread_join Segmentation
>> fault
>>
>> Here's another, different one:
>>
>> success - thread_init - axutil_thread_once_init success - thread_init
>> - axutil_thread_mutex_create thread data = 5 x = 1 success -
>> test_axutil_thread_create - axutil_thread_create success -
>> test_axutil_thread_create - axutil_thread_create Segmentation fault
>>
>> Here's a backtrace from a failure like the first one above:
>>
>> (gdb) bt
>> #0 0x003854bd in axutil_thread_join (thd=0x80552b0) at
>> thread_unix.c:158
>> #1 0x08048d27 in test_axutil_thread_detach (env=0x80551e0)
>> at test_thread.c:132
>> #2 0x08048fdb in create_env_with_error_log () at test_thread.c:260
>> #3 0x0804915d in __libc_csu_fini ()
>> from
>> /tmp/chrisd_build/axis2c-src-1.0.0/util/test/util/.libs/test_thread
>> #4 0x00125e23 in __libc_start_main () from /lib/tls/libc.so.6
>> #5 0x080489e1 in __do_global_dtors_aux ()
>> from
>> /tmp/chrisd_build/axis2c-src-1.0.0/util/test/util/.libs/test_thread
>>
>> (gdb) frame
>> #0 0x003854bd in axutil_thread_join (thd=0x80552b0) at
>> thread_unix.c:158
>> 158 if (0 == pthread_join(*(thd->td), (void *)(&thread_stat)))
>>
>> (gdb) print *(thd->td)
>> Cannot access memory at address 0x62696c2f
>>
>> I'm not sure if that helps, but it looks to me like something
>> must be getting deallocated at the wrong time here.
>>
>> Chris.
>>
>>
>
>
--
Samisa Abeysinghe : http://www.wso2.org/ (WSO2 Oxygen Tank - Web Services Developers' Portal)
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
Re: [Vote] [Axis2] Vote for Apache Axis2/C 1.0.0 Release
Posted by Samisa Abeysinghe <sa...@wso2.com>.
Fixed both the issues.
Thanks,
Samisa...
Chris Darroch wrote:
> Samisa:
>
>
>> The latest, and final, artifacts are uploaded here:
>> http://people.apache.org/~samisa/release/1.0.0/final/
>>
>> Please test. I plan to send the release note in about 12 hours form now.
>>
>> I have tested all the sources and binaries successfully.
>>
>
> Thanks for all the quick fixes! The configure --help notes and
> the INSTALL files are much clearer. I successfully built and
> installed and tested with --enable-tests, and with the samples directory.
>
> Two things, one small, one maybe not:
>
> The small thing is that is seems like the
> test/core/clientapi/test_clientapi program fails (with a message now,
> thank you!) unless AXIS2C_HOME points to the installed location.
> (I'm guessing it's looking for axis2.xml.) This means you really
> should run "make && make install", then set AXIS2C_HOME=/path/to/install,
> and then "make check". That's a little different than the usual
> "make && make check && make install" process.
>
> We should perhaps make that clean in the main INSTALL file, or else
> alter test_clientapi.c somehow so that it will work if you set
> AXIS2C_HOME=/path/to/source or something. Then the more
> typical "check then install" process would function, so long as you
> had AXIS2C_HOME set to the location of the Axis2/C sources.
>
>
> The maybe not-so-small thing is that for me, at least, on an
> older RedHat Linux box, util/test/util/test_thread fails sometimes
> and not other times. That feels like a race condition problem to me.
> (This is regardless of what AXIS2C_HOME is set to, or even if it's
> unset; that was a red herring in my previous email.)
>
> Here's the output from an unsuccessful run:
>
> success - thread_init - axutil_thread_once_init
> success - thread_init - axutil_thread_mutex_create
> success - test_axutil_thread_create - axutil_thread_create
> success - test_axutil_thread_create - axutil_thread_create
> thread data = 5
> x = 1
> thread data = 25
> x = 2
> success - test_axutil_thread_create - axutil_thread_join
> Segmentation fault
>
> Here's another, different one:
>
> success - thread_init - axutil_thread_once_init
> success - thread_init - axutil_thread_mutex_create
> thread data = 5
> x = 1
> success - test_axutil_thread_create - axutil_thread_create
> success - test_axutil_thread_create - axutil_thread_create
> Segmentation fault
>
> Here's a backtrace from a failure like the first one above:
>
> (gdb) bt
> #0 0x003854bd in axutil_thread_join (thd=0x80552b0) at thread_unix.c:158
> #1 0x08048d27 in test_axutil_thread_detach (env=0x80551e0)
> at test_thread.c:132
> #2 0x08048fdb in create_env_with_error_log () at test_thread.c:260
> #3 0x0804915d in __libc_csu_fini ()
> from /tmp/chrisd_build/axis2c-src-1.0.0/util/test/util/.libs/test_thread
> #4 0x00125e23 in __libc_start_main () from /lib/tls/libc.so.6
> #5 0x080489e1 in __do_global_dtors_aux ()
> from /tmp/chrisd_build/axis2c-src-1.0.0/util/test/util/.libs/test_thread
>
> (gdb) frame
> #0 0x003854bd in axutil_thread_join (thd=0x80552b0) at thread_unix.c:158
> 158 if (0 == pthread_join(*(thd->td), (void *)(&thread_stat)))
>
> (gdb) print *(thd->td)
> Cannot access memory at address 0x62696c2f
>
> I'm not sure if that helps, but it looks to me like something
> must be getting deallocated at the wrong time here.
>
> Chris.
>
>
--
Samisa Abeysinghe : http://www.wso2.org/ (WSO2 Oxygen Tank - Web Services Developers' Portal)
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
Re: [Vote] [Axis2] Vote for Apache Axis2/C 1.0.0 Release
Posted by Chris Darroch <ch...@pearsoncmg.com>.
Samisa:
> The latest, and final, artifacts are uploaded here:
> http://people.apache.org/~samisa/release/1.0.0/final/
>
> Please test. I plan to send the release note in about 12 hours form now.
>
> I have tested all the sources and binaries successfully.
Thanks for all the quick fixes! The configure --help notes and
the INSTALL files are much clearer. I successfully built and
installed and tested with --enable-tests, and with the samples directory.
Two things, one small, one maybe not:
The small thing is that is seems like the
test/core/clientapi/test_clientapi program fails (with a message now,
thank you!) unless AXIS2C_HOME points to the installed location.
(I'm guessing it's looking for axis2.xml.) This means you really
should run "make && make install", then set AXIS2C_HOME=/path/to/install,
and then "make check". That's a little different than the usual
"make && make check && make install" process.
We should perhaps make that clean in the main INSTALL file, or else
alter test_clientapi.c somehow so that it will work if you set
AXIS2C_HOME=/path/to/source or something. Then the more
typical "check then install" process would function, so long as you
had AXIS2C_HOME set to the location of the Axis2/C sources.
The maybe not-so-small thing is that for me, at least, on an
older RedHat Linux box, util/test/util/test_thread fails sometimes
and not other times. That feels like a race condition problem to me.
(This is regardless of what AXIS2C_HOME is set to, or even if it's
unset; that was a red herring in my previous email.)
Here's the output from an unsuccessful run:
success - thread_init - axutil_thread_once_init
success - thread_init - axutil_thread_mutex_create
success - test_axutil_thread_create - axutil_thread_create
success - test_axutil_thread_create - axutil_thread_create
thread data = 5
x = 1
thread data = 25
x = 2
success - test_axutil_thread_create - axutil_thread_join
Segmentation fault
Here's another, different one:
success - thread_init - axutil_thread_once_init
success - thread_init - axutil_thread_mutex_create
thread data = 5
x = 1
success - test_axutil_thread_create - axutil_thread_create
success - test_axutil_thread_create - axutil_thread_create
Segmentation fault
Here's a backtrace from a failure like the first one above:
(gdb) bt
#0 0x003854bd in axutil_thread_join (thd=0x80552b0) at thread_unix.c:158
#1 0x08048d27 in test_axutil_thread_detach (env=0x80551e0)
at test_thread.c:132
#2 0x08048fdb in create_env_with_error_log () at test_thread.c:260
#3 0x0804915d in __libc_csu_fini ()
from /tmp/chrisd_build/axis2c-src-1.0.0/util/test/util/.libs/test_thread
#4 0x00125e23 in __libc_start_main () from /lib/tls/libc.so.6
#5 0x080489e1 in __do_global_dtors_aux ()
from /tmp/chrisd_build/axis2c-src-1.0.0/util/test/util/.libs/test_thread
(gdb) frame
#0 0x003854bd in axutil_thread_join (thd=0x80552b0) at thread_unix.c:158
158 if (0 == pthread_join(*(thd->td), (void *)(&thread_stat)))
(gdb) print *(thd->td)
Cannot access memory at address 0x62696c2f
I'm not sure if that helps, but it looks to me like something
must be getting deallocated at the wrong time here.
Chris.
--
GPG Key ID: 366A375B
GPG Key Fingerprint: 485E 5041 17E1 E2BB C263 E4DE C8E3 FA36 366A 375B
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
Re: openssl
Posted by Wayne Johnson <wd...@yahoo.com>.
Their part of the OpenSSL product. http://www.openssl.org/.
I just got done rebuilding it for our use, so if you need help...
Jim Seipp <Ji...@avid.com> wrote: Hi,
Can someone please tell me where I get the files for
#include
Thanks,
Jim
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
---
Wayne Johnson, | There are two kinds of people: Those
3943 Penn Ave. N. | who say to God, "Thy will be done,"
Minneapolis, MN 55412-1908 | and those to whom God says, "All right,
(612) 522-7003 | then, have it your way." --C.S. Lewis
---------------------------------
Ahhh...imagining that irresistible "new car" smell?
Check outnew cars at Yahoo! Autos.
openssl
Posted by Jim Seipp <Ji...@avid.com>.
Hi,
Can someone please tell me where I get the files for
#include <openssl/ssl.h>
Thanks,
Jim
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
Re: [Vote] [Axis2] Vote for Apache Axis2/C 1.0.0 Release
Posted by Samisa Abeysinghe <sa...@wso2.com>.
The latest, and final, artifacts are uploaded here:
http://people.apache.org/~samisa/release/1.0.0/final/
Please test. I plan to send the release note in about 12 hours form now.
I have tested all the sources and binaries successfully.
Thanks,
Samisa...
Samisa Abeysinghe wrote:
> Devs,
> I have fixed the issues raised by Chris on the tag and the svn head.
> I would package the artifacts again and test. Please kindly test
> the 1.0.0 tag in the mean time and report any issues.
>
> Thanks,
> Samisa...
>
> Chris Darroch wrote:
>
>> Samisa Abeysinghe wrote:
>>
>>
>>
>>> Please test, review and vote on the release artifacts for Apache
>>> Axis2/C 1.0.0 release.
>>>
>>
>>
>> If you can bear with me for a few days, I'll try to do a bit more
>> testing, but here are a few initial notes:
>>
>>
>> First, the include files look so nice and clean! Thank you! On
>> first glance the library filenames, httpd config directives, and
>> general layout seem clean and clear -- again, thank you!
>>
>>
>> Second, I thought I might revise the main INSTALL and configure
>> files a
>> little to explain certain parameters to configure a bit better. In
>> particular, the --with-apr and --with-apache2 options mostly don't
>> mention
>> what kind of path they take: to the "prefix" that was used to install
>> those
>> packages? To their lib directories? In fact, they both take paths
>> to the
>> include directories of those packages.
>>
>> I can't remember if Axis2/C actually needs anything except the httpd
>> include files ... maybe not. I can't see anything offhand that ldd
>> shows as having links to their libraries. That would be easier, if
>> true!
>>
>> (If anything does link against their libraries, though, I think the
>> Axis2/C configure script might need to get paths for both their include
>> and library directories. For example, if someone installs httpd using
>> its --enable-layout option (see the config.layout file in the httpd
>> source
>> package for details), they have a lot of control over where the
>> libraries end up: not necessarily in $prefix/lib, next to
>> $prefix/include.
>> Anyway, my dim memory is that, in fact, Axis2/C doesn't link against
>> the APR and httpd libraries, so all of this is moot.)
>>
>> The INSTALL file does explain that --with-apr takes the include
>> path for APR, however, it doesn't say the same thing about the
>> --with-apache2 option.
>>
>> And if you run ./configure --help, you just get:
>>
>> --with-apache2=PATH use apache2 as server transport.
>> --with-apr=PATH use apr.
>>
>> Compare with the following from APR-util configure --help:
>>
>> --with-berkeley-db=PATH
>> Find the Berkeley DB header and library in 'PATH/include' and
>> 'PATH/lib'. If PATH is of the form 'HEADER:LIB', then search
>> for header files in HEADER, and the library in LIB. If you omit
>> the '=PATH' part completely, the configure script will search
>> for Berkeley DB in a number of standard places.
>>
>> So if you can wait a few days, I can edit these a little bit
>> (or someone else can, of course!)
>>
>> For example, I was able to successfully build Axis2/C with the
>> following:
>>
>> CFLAGS=-I$PREFIX/package/include LDFLAGS=-L$PREFIX/package/lib \
>> ./configure --enable-tests \
>> --prefix=/tmp/chrisd_build/axis2c \
>> --with-apr=$PREFIX/package/include/apr-1 \
>> --with-apache2=$PREFIX/package/include/apache2
>>
>>
>> Next, the samples ./configure script and INSTALL files should
>> explain that they need the full path to the Axis2/C include directories,
>> or else they should append the axis2-1.0 subdirectory automatically.
>> (BTW, thanks for that versioned subdir!) The ./configure --help
>> option just says:
>>
>> --with-axiom=PATH use axiom.
>> --with-axis2_util=PATH use axis2_util.
>>
>> Also, the main INSTALL file (not the samples one) says:
>>
>>
>>
>>> To build the samples:
>>>
>>> export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/axis2c/lib/
>>> cd samples
>>> ./configure --prefix=${AXIS2C_HOME}
>>> --with-axis2_util=${AXIS2C_HOME}/include
>>> --with-axiom=${AXIS2C_HOME}/include
>>>
>>
>>
>> Here's what I had to use to successfully build the samples; note
>> the axis2-1.0 subdirectories:
>>
>> LDFLAGS=-L/tmp/chrisd_build/axis2c/lib \
>> ./configure --prefix=/tmp/chrisd_build/axis2c \
>>
>> --with-axis2_util=/tmp/chrisd_build/axis2c/include/axis2-1.0 \
>> --with-axiom=/tmp/chrisd_build/axis2c/include/axis2-1.0
>>
>> Again, if you can wait a few days, I can edit these, or someone
>> else can certainly tackle it.
>>
>>
>> Third, the "make check" option isn't quite working right yet,
>> I think. Running in the source package, you get a segfault right
>> away unless you have AXIS2C_HOME=/path/to/source/axis2c/package.
>> (I tried running "make install" and then setting AXIS2C_HOME
>> to point to the installation location, but it doesn't seem to like
>> that; you need to pointing to the source package.) The INSTALL
>> file suggests you'll need AXIS2C_HOME=/path/to/install/axis2c/package
>> but I'm not sure that's correct.
>>
>> With it set, more of the tests run fine, but I'm getting a segfault
>> on test/core/clientapi/test_clientapi. It occurs within the call
>> to axis2_svc_client_set_options(svc_client, env, options) somewhere
>> in test_clientapi.c. That's as far I'm likely to get for a day or
>> so, I fear.
>>
>>
>> But, overall, looking really nice! Thanks again,
>>
>> Chris.
>>
>>
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-c-dev-help@ws.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
RE: WSDL2C
Posted by Jim Seipp <Ji...@avid.com>.
Hi Samisa,
I see this file in the util/include folder on the 0.96 release but not
in the 1.0 release
Thanks,
Jim
-----Original Message-----
From: Samisa Abeysinghe [mailto:samisa@wso2.com]
Sent: Tuesday, May 01, 2007 8:05 PM
To: Apache AXIS C Developers List
Subject: Re: WSDL2C
Jim Seipp wrote:
>Hi,
>
>I am having problems using WSDL2C.java
>
>The code generates Axis2/C code but it is referencing a header file
that
>does not exist.
>
>"axis2_log_default.h"
>
>I am getting numerous other compiler errors also.
>
>Should this be working?
>
>
Yes that should work. The header is in include folder.
Did you provide the correct include paths when compiling?
Samisa...
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
Re: WSDL2C
Posted by Milinda Pathirage <mi...@gmail.com>.
Hi Jim,
Please try this nightly build
http://people.apache.org/dist/axis2/nightly/axis2-SNAPSHOT.zip.
Thanks
Milinda
On 5/3/07, Milinda Pathirage <mi...@gmail.com> wrote:
>
> Hi Jim,
> Can you please tell me which version of Axis2/Java is used for code
> generation. It is better if you can get a checkout from Axis2/Java svn trunk
> and build. I updated all the changes in current trunk of Axis2/Java before
> the Axis2/c 1.0.0 release.
>
> Thanks
> Milinda
>
> On 5/2/07, Samisa Abeysinghe <sa...@wso2.com> wrote:
> >
> > Jim Seipp wrote:
> >
> > >Hi Samisa,
> > >
> > >I am using "Apache Axis2 1.2-SNAPSHOT build (May 1 2007)"
> > >
> > >It appears that it is compiling WSDL2C.java to use the header file
> > >'axis2_log_default.h"
> > >
> > >In the Axis2C release folder util/include I see the file
> > >"axutil_log_default.h"
> > >
> > >It appears that the WSDL2C.java program is compiling to use an obsolete
> > >header name?
> > >
> > >
> > Opps, that is a bug :(
> >
> > Is it possible for you to create a Jira issue and attach the WSDL file
> > tat you are using to that Jira?
> >
> > Samisa...
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-c-dev-help@ws.apache.org
> >
> >
>
>
> --
> milinda@wso2.com
> WSO2, Inc: http://www.wso2.com "Oxygenating the Web Service Platform"
> http://www.milindalakmal.wordpress.com
--
milinda@wso2.com
WSO2, Inc: http://www.wso2.com "Oxygenating the Web Service Platform"
http://www.milindalakmal.wordpress.com
Re: WSDL2C
Posted by Milinda Pathirage <mi...@gmail.com>.
Hi Jim,
Can you please tell me which version of Axis2/Java is used for code
generation. It is better if you can get a checkout from Axis2/Java svn trunk
and build. I updated all the changes in current trunk of Axis2/Java before
the Axis2/c 1.0.0 release.
Thanks
Milinda
On 5/2/07, Samisa Abeysinghe <sa...@wso2.com> wrote:
>
> Jim Seipp wrote:
>
> >Hi Samisa,
> >
> >I am using "Apache Axis2 1.2-SNAPSHOT build (May 1 2007)"
> >
> >It appears that it is compiling WSDL2C.java to use the header file
> >'axis2_log_default.h"
> >
> >In the Axis2C release folder util/include I see the file
> >"axutil_log_default.h"
> >
> >It appears that the WSDL2C.java program is compiling to use an obsolete
> >header name?
> >
> >
> Opps, that is a bug :(
>
> Is it possible for you to create a Jira issue and attach the WSDL file
> tat you are using to that Jira?
>
> Samisa...
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-c-dev-help@ws.apache.org
>
>
--
milinda@wso2.com
WSO2, Inc: http://www.wso2.com "Oxygenating the Web Service Platform"
http://www.milindalakmal.wordpress.com
Re: WSDL2C
Posted by Samisa Abeysinghe <sa...@wso2.com>.
Jim Seipp wrote:
>Hi Samisa,
>
>I am using "Apache Axis2 1.2-SNAPSHOT build (May 1 2007)"
>
>It appears that it is compiling WSDL2C.java to use the header file
>'axis2_log_default.h"
>
>In the Axis2C release folder util/include I see the file
>"axutil_log_default.h"
>
>It appears that the WSDL2C.java program is compiling to use an obsolete
>header name?
>
>
Opps, that is a bug :(
Is it possible for you to create a Jira issue and attach the WSDL file
tat you are using to that Jira?
Samisa...
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
RE: WSDL2C
Posted by Jim Seipp <Ji...@avid.com>.
Hi Samisa,
I am using "Apache Axis2 1.2-SNAPSHOT build (May 1 2007)"
It appears that it is compiling WSDL2C.java to use the header file
'axis2_log_default.h"
In the Axis2C release folder util/include I see the file
"axutil_log_default.h"
It appears that the WSDL2C.java program is compiling to use an obsolete
header name?
Thanks,
Jim
-----Original Message-----
From: Samisa Abeysinghe [mailto:samisa@wso2.com]
Sent: Tuesday, May 01, 2007 8:05 PM
To: Apache AXIS C Developers List
Subject: Re: WSDL2C
Jim Seipp wrote:
>Hi,
>
>I am having problems using WSDL2C.java
>
>The code generates Axis2/C code but it is referencing a header file
that
>does not exist.
>
>"axis2_log_default.h"
>
>I am getting numerous other compiler errors also.
>
>Should this be working?
>
>
Yes that should work. The header is in include folder.
Did you provide the correct include paths when compiling?
Samisa...
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
Re: WSDL2C
Posted by Samisa Abeysinghe <sa...@wso2.com>.
Jim Seipp wrote:
>Hi,
>
>I am having problems using WSDL2C.java
>
>The code generates Axis2/C code but it is referencing a header file that
>does not exist.
>
>"axis2_log_default.h"
>
>I am getting numerous other compiler errors also.
>
>Should this be working?
>
>
Yes that should work. The header is in include folder.
Did you provide the correct include paths when compiling?
Samisa...
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
WSDL2C
Posted by Jim Seipp <Ji...@avid.com>.
Hi,
I am having problems using WSDL2C.java
The code generates Axis2/C code but it is referencing a header file that
does not exist.
"axis2_log_default.h"
I am getting numerous other compiler errors also.
Should this be working?
Thanks,
Jim
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
Re: [Vote] [Axis2] Vote for Apache Axis2/C 1.0.0 Release
Posted by Samisa Abeysinghe <sa...@wso2.com>.
Devs,
I have fixed the issues raised by Chris on the tag and the svn head.
I would package the artifacts again and test. Please kindly test the
1.0.0 tag in the mean time and report any issues.
Thanks,
Samisa...
Chris Darroch wrote:
>Samisa Abeysinghe wrote:
>
>
>
>> Please test, review and vote on the release artifacts for Apache
>>Axis2/C 1.0.0 release.
>>
>>
>
> If you can bear with me for a few days, I'll try to do a bit more
>testing, but here are a few initial notes:
>
>
> First, the include files look so nice and clean! Thank you! On
>first glance the library filenames, httpd config directives, and
>general layout seem clean and clear -- again, thank you!
>
>
> Second, I thought I might revise the main INSTALL and configure files a
>little to explain certain parameters to configure a bit better. In
>particular, the --with-apr and --with-apache2 options mostly don't mention
>what kind of path they take: to the "prefix" that was used to install those
>packages? To their lib directories? In fact, they both take paths to the
>include directories of those packages.
>
> I can't remember if Axis2/C actually needs anything except the httpd
>include files ... maybe not. I can't see anything offhand that ldd
>shows as having links to their libraries. That would be easier, if true!
>
> (If anything does link against their libraries, though, I think the
>Axis2/C configure script might need to get paths for both their include
>and library directories. For example, if someone installs httpd using
>its --enable-layout option (see the config.layout file in the httpd source
>package for details), they have a lot of control over where the
>libraries end up: not necessarily in $prefix/lib, next to $prefix/include.
>Anyway, my dim memory is that, in fact, Axis2/C doesn't link against
>the APR and httpd libraries, so all of this is moot.)
>
> The INSTALL file does explain that --with-apr takes the include
>path for APR, however, it doesn't say the same thing about the
>--with-apache2 option.
>
> And if you run ./configure --help, you just get:
>
> --with-apache2=PATH use apache2 as server transport.
> --with-apr=PATH use apr.
>
> Compare with the following from APR-util configure --help:
>
> --with-berkeley-db=PATH
> Find the Berkeley DB header and library in 'PATH/include' and
> 'PATH/lib'. If PATH is of the form 'HEADER:LIB', then search
> for header files in HEADER, and the library in LIB. If you omit
> the '=PATH' part completely, the configure script will search
> for Berkeley DB in a number of standard places.
>
> So if you can wait a few days, I can edit these a little bit
>(or someone else can, of course!)
>
> For example, I was able to successfully build Axis2/C with the
>following:
>
>CFLAGS=-I$PREFIX/package/include LDFLAGS=-L$PREFIX/package/lib \
> ./configure --enable-tests \
> --prefix=/tmp/chrisd_build/axis2c \
> --with-apr=$PREFIX/package/include/apr-1 \
> --with-apache2=$PREFIX/package/include/apache2
>
>
> Next, the samples ./configure script and INSTALL files should
>explain that they need the full path to the Axis2/C include directories,
>or else they should append the axis2-1.0 subdirectory automatically.
>(BTW, thanks for that versioned subdir!) The ./configure --help
>option just says:
>
> --with-axiom=PATH use axiom.
> --with-axis2_util=PATH use axis2_util.
>
> Also, the main INSTALL file (not the samples one) says:
>
>
>
>> To build the samples:
>>
>> export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/axis2c/lib/
>> cd samples
>> ./configure --prefix=${AXIS2C_HOME}
>> --with-axis2_util=${AXIS2C_HOME}/include
>> --with-axiom=${AXIS2C_HOME}/include
>>
>>
>
> Here's what I had to use to successfully build the samples; note
>the axis2-1.0 subdirectories:
>
>LDFLAGS=-L/tmp/chrisd_build/axis2c/lib \
> ./configure --prefix=/tmp/chrisd_build/axis2c \
> --with-axis2_util=/tmp/chrisd_build/axis2c/include/axis2-1.0 \
> --with-axiom=/tmp/chrisd_build/axis2c/include/axis2-1.0
>
> Again, if you can wait a few days, I can edit these, or someone
>else can certainly tackle it.
>
>
> Third, the "make check" option isn't quite working right yet,
>I think. Running in the source package, you get a segfault right
>away unless you have AXIS2C_HOME=/path/to/source/axis2c/package.
>(I tried running "make install" and then setting AXIS2C_HOME
>to point to the installation location, but it doesn't seem to like
>that; you need to pointing to the source package.) The INSTALL
>file suggests you'll need AXIS2C_HOME=/path/to/install/axis2c/package
>but I'm not sure that's correct.
>
> With it set, more of the tests run fine, but I'm getting a segfault
>on test/core/clientapi/test_clientapi. It occurs within the call
>to axis2_svc_client_set_options(svc_client, env, options) somewhere
>in test_clientapi.c. That's as far I'm likely to get for a day or
>so, I fear.
>
>
> But, overall, looking really nice! Thanks again,
>
>Chris.
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org