You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-user@axis.apache.org by mark tokheim <ma...@gmail.com> on 2008/05/05 22:25:48 UTC
Solaris 10, clientapi libs not in install area
Hi,
After a successful make and make install on Solaris 10. I noticed that
there are several libs missing from the installation directory's lib dir.
For example libaxis2_clientapi.a and libaxis2_clientapi.la are not there.
I have other components in the lib dir (axiom.a, engine.a, etc) Looking
through the make log, clientapi did successfully build, but nothing happened
on the make install.. I was wondering if I missed something on the
configure or if this is by design. Thanks in advance.
-Mark
Re: Solaris 10, clientapi libs not in install area
Posted by mark tokheim <ma...@gmail.com>.
Ok. Thanks again.
On Mon, May 5, 2008 at 7:36 PM, Sanjaya Ratnaweera <sa...@wso2.com> wrote:
> Hi mark,
> libaxis2_clientapi.la is not installing to the lib directory, because
> it's linked to libaxis2_engine.la. And also following libraries are linked
> to libaxis2_engine.la.
>
> libaxis2_description.la
> libaxis2_receivers.la
> libaxis2_deployment.la
> libaxis2_context.la
> libaxis2_addr.la
> libaxis2_clientapi.la
> libaxis2_phaseresolver.la
> libaxis2_core_utils.la
> libaxutil.la
> libneethi.la
> libaxis2_http_common.la
>
>
> Therefore linking libaxis2_engine.la should be enough.
>
> Thanks
>
> ~sanjaya
>
>
> mark tokheim wrote:
>
> Hi,
> After a successful make and make install on Solaris 10. I noticed
> that there are several libs missing from the installation directory's lib
> dir. For example libaxis2_clientapi.a and libaxis2_clientapi.la are not
> there. I have other components in the lib dir (axiom.a, engine.a, etc)
> Looking through the make log, clientapi did successfully build, but nothing
> happened on the make install.. I was wondering if I missed something on the
> configure or if this is by design. Thanks in advance.
> -Mark
>
>
>
Re: Solaris 10, clientapi libs not in install area
Posted by Sanjaya Ratnaweera <sa...@wso2.com>.
Hi mark,
libaxis2_clientapi.la is not installing to the lib directory,
because it's linked to libaxis2_engine.la. And also following libraries
are linked to libaxis2_engine.la.
libaxis2_description.la
libaxis2_receivers.la
libaxis2_deployment.la
libaxis2_context.la
libaxis2_addr.la
libaxis2_clientapi.la
libaxis2_phaseresolver.la
libaxis2_core_utils.la
libaxutil.la
libneethi.la
libaxis2_http_common.la
Therefore linking libaxis2_engine.la should be enough.
Thanks
~sanjaya
mark tokheim wrote:
> Hi,
> After a successful make and make install on Solaris 10. I noticed
> that there are several libs missing from the installation directory's
> lib dir. For example libaxis2_clientapi.a and libaxis2_clientapi.la
> <http://libaxis2_clientapi.la> are not there. I have other
> components in the lib dir (axiom.a, engine.a, etc) Looking through
> the make log, clientapi did successfully build, but nothing happened
> on the make install.. I was wondering if I missed something on the
> configure or if this is by design. Thanks in advance.
> -Mark