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 Samisa Abeysinghe <sa...@yahoo.com> on 2004/11/23 13:39:59 UTC
Ant build [WAS: Re: Run fails [WAS:Re: Build error log ...}]
I cannot just run ant build on Linux after checking out source from CVS in AXISCPP_HOME.
I get the error:
/home/samisa/autoCVS/cvsAutoBuild/build/buildClient.xml:7: Directory /home/obj/objects creation
was not successful for an unknown reason.
If I fix this I get few more...
I could fix those and let the user run ant on source tree as it is.
It it OK to change
dir.obj = ${basedir}/../../../obj
to
dir.obj = ${basedir}/deploy/obj
and
dir.zips = ${basedir}/../../../zips
to
dir.zips = ${basedir}/deploy/zips
Would this have any side effects to the nightly build?
Thanks,
Samisa...
--- Samisa Abeysinghe <sa...@yahoo.com> wrote:
> I tried the noghly build today and it is not blocking.
> Is this something to do with the GNU make build? Has there been any files removed lately from
> the
> source that the GNU make build is not updated for?
>
> I also have few comments on the nightly build:
>
> 1. so files are named with ".so.1.4.0" postfix. Can we make it just .so as -l option only picks
> those
>
> 2. libs are placed in axis-c-1.4.0-Linux-bin/axis/lib. However they are placed in deploy/lib
> usually. So can we place the libs in axis-c-1.4.0-Linux-bin/deploy/lib
>
> 3. There are neoumourous name differences in the so files available with the nightly build and
> those build with GNU make system. (Simply speaking they are not consistant) I think .so file
> names
> that come with nightly build are more appropriate. We have to make the GNU make to build the
> same
> and also change the docs accordingly.
>
> 4. Nither ant not make could be used to build samples. I had to use g++ on command line. Why not
> have the samples built for the nightly build?
>
> 5. simple_axis_server is placed in bin, usually this is placed in deploy/bin
>
> 6. Excecute rights are not set on simple_axis_server binary
>
>
>
> --- Samisa Abeysinghe <sa...@yahoo.com> wrote:
>
> > I will try the nightly build.
> >
> > However, I am still facing the same problem with the CVS checkout with GNU make build.
> >
> > Samisa...
> > --- John Hawkins <HA...@uk.ibm.com> wrote:
> >
> > >
> > >
> > >
> > >
> > > Our build from the 19th did not have this problem. Perhaps try the
> > > overnight build on the web-site?
> > >
> > > John Hawkins
> > >
> > >
> > >
> > >
> > >
> > > Samisa Abeysinghe
> > > <samisa_abeysingh
> > > e@yahoo.com> To
> > > Apache AXIS C Developers List
> > > 22/11/2004 10:01 <ax...@ws.apache.org>
> > > cc
> > >
> > > Please respond to Subject
> > > "Apache AXIS C Re: Run fails [WAS:Re: Build error
> > > Developers List" log for CVS source - Summary: build
> > > success}
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > Is anybody else experiancing this?
> > >
> > > I think it is failing to go past lock() call in
> > > DeserializerPool::getInstance() of
> > > src/engine/DeserializerPool.cpp.
> > >
> > > However, I am still strugling to find a solution. Appreciate any help.
> > >
> > > Thanks,
> > > Samisa...
> > >
> > > --- Samisa Abeysinghe <sa...@yahoo.com> wrote:
> > >
> > > > When I try to run clients with the latest CVS code, the client hangs
> > > infinitely.
> > > >
> > > > Ruuning with gdb and intrrupting shows that it client is waiting for a
> > > lock. Unfortunately gdb
> > > > does not show where the lock is being used.
> > > >
> > > > (gdb) bt
> > > > #0 0x00f627a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
> > > > #1 0x003f2cbe in __lll_mutex_lock_wait () from /lib/tls/libpthread.so.0
> > > > #2 0x003efc84 in _L_mutex_lock_29 () from /lib/tls/libpthread.so.0
> > > > #3 0x00ba8338 in ?? () from
> > > /home/samisa/autoCVS/cvsAutoBuild/deploy/lib/libaxiscpp_client.so.0
> > > > #4 0x09b97c48 in ?? ()
> > > > #5 0x00d6affc in ?? () from /lib/tls/libc.so.6
> > > > #6 0x09b96598 in ?? ()
> > > > #7 0x09ba1c60 in ?? ()
> > > > #8 0xfee53778 in ?? ()
> > > > #9 0x00d1bebf in pthread_mutex_lock () from /lib/tls/libc.so.6
> > > > Previous frame identical to this frame (corrupt stack?)
> > > >
> > > > Any thoughts whay this is happening.
> > > >
> > > > Thanks,
> > > > Samisa...
> > > >
> > > >
> > > >
> > > > __________________________________
> > > > Do you Yahoo!?
> > > > Meet the all-new My Yahoo! - Try it today!
> > > > http://my.yahoo.com
> > > >
> > > >
> > > >
> > >
> > >
> > >
> > >
> > > __________________________________
> > > Do you Yahoo!?
> > > The all-new My Yahoo! - Get yours free!
> > > http://my.yahoo.com
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
> >
> > __________________________________
> > Do you Yahoo!?
> > The all-new My Yahoo! - Get yours free!
> > http://my.yahoo.com
> >
> >
> >
>
>
>
>
> __________________________________
> Do you Yahoo!?
> Meet the all-new My Yahoo! - Try it today!
> http://my.yahoo.com
>
>
>
__________________________________
Do you Yahoo!?
Meet the all-new My Yahoo! - Try it today!
http://my.yahoo.com