axis-c-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ramesh Gopal <fatuzorin2...@yahoo.com>
Subject Re: Axis2C build on HP 11.11 (32 bit) ---- Pls help me with this problem
Date Thu, 03 Mar 2011 05:00:44 GMT

Hello Thomas,

The script that gets executed is :

archive_cmds='$CC -b -Wl,+s -Wl,+h -Wl,$soname -Wl,+b -Wl,$install_libdir -o $lib $libobjs
$deplibs $compiler_flags


Is it possible to give a direct conversion of this script to use the ld option as you had
suggested.

Is this the right way of probably building Axis and its corresponding so files?

Ramesh.


--- On Wed, 2/3/11, Thomas Gentsch <tg@e-tge.de> wrote:

> From: Thomas Gentsch <tg@e-tge.de>
> Subject: Re: Axis2C build on HP 11.11 (32 bit) ---- Pls help me with this problem
> To: "Apache AXIS C User List" <c-user@axis.apache.org>
> Date: Wednesday, 2 March, 2011, 6:42 PM
> 
> Hi Ramesh,
> 
> sorry for the delay ...
> Here is how I build shared libs on HP-UX PA-Risc (of course
> using some
> Makefile):
> 
> $ ld file1.o file2.o ...
>   -b
>   -B immediate
>   +b:
>   -L. -L/lib/path1 -L/lib/path2 ...
>   +s
>   -lib1 -lib2 ...
>   -omylib.sl
> 
> which means:
>  - a list of object files as usual
>  - -b create a shared lib
>  - -B immediate means "binding immediate, i.e. resolve 
>       all foreign symbols at lib loading"
>  - +b allows to set a runtime library path, +b: is special
> in a way 
>    that it uses all the -L paths for this
> purpose
>  - -L as usual
>  - +s means that SHLIB_PATH is to be activated (the HP-UX
> equivalent of 
>    LD_LIBRARY_PATH)
>  - -l and -o as usual
> 
> This results in:
> $ chatr mylib.sl
> mylib.sl: 
>          shared library 
>          shared library
> dynamic path search:
>          
>    SHLIB_PATH 
>    enabled   second 
>          
>    embedded path 
> enabled   first 
> :.:/lib/path1:/lib/path2
>          shared library
> list:
>          
>    dynamic   /lib/path1/libib1.sl
>          
>    dynamic   /lib/path2/libib2.sl
>              ...
>          shared vtable
> support disabled
>          explicit unloading
> enabled
>          ...
> 
> Now you have a SL that
>  1. tries to use the shared libs as stated above
>  2. tries the embedded library search path
>  3. tries SHLIB_PATH and LD_LIBRARY_PATH
> (I'm not sure about 1. without trying out)
> 
> I never use libtool and don't know what to do in that
> case.
> But the way above works nicely.
> 
> HTH :-)
>   tge
> 
> On Tue, 2011-03-01 at 16:26 +0530, ramesh Gopal wrote:
> > I see that there is a libtool script, I suppose this
> is the one which does the linking phase and there could be
> some parameters which we might need to change to accomplish
> this.
> > 
> > I am trying to see.
> > 
> > In the meanwhile, can anybody tell me if they could
> get an Axis build on HP UX 11.11 working ...
> > 
> > Rgds,
> > Ramesh.
> > 
> > --- On Tue, 1/3/11, ramesh Gopal <fatuzorin2001@yahoo.com>
> wrote:
> > 
> > > From: ramesh Gopal <fatuzorin2001@yahoo.com>
> > > Subject: Re: Axis2C build on HP 11.11 (32 bit)
> > > To: "Apache AXIS C User List" <c-user@axis.apache.org>
> > > Date: Tuesday, 1 March, 2011, 2:14 PM
> > > 
> > > Hello,
> > > 
> > > Pls help me with this issue.
> > > 
> > > There should be a way to suppress the hardcoding
> of the
> > > paths while creating the shared object. Is there
> something
> > > parameter in the configure script which might be
> causing
> > > this behaviour.
> > > 
> > > Ramesh.
> > > 
> > > --- On Tue, 22/2/11, ramesh Gopal <fatuzorin2001@yahoo.com>
> > > wrote:
> > > 
> > > > From: ramesh Gopal <fatuzorin2001@yahoo.com>
> > > > Subject: Re: Axis2C build on HP 11.11 (32
> bit)
> > > > To: "Apache AXIS C User List" <c-user@axis.apache.org>
> > > > Date: Tuesday, 22 February, 2011, 3:46 PM
> > > > 
> > > > Hello Thomas,
> > > > 
> > > > The chatr command displays :
> > > > 
> > > > chatr libaxis2_engine.so 
> > > > libaxis2_engine.so: 
> > > >          shared
> library 
> > > >          shared
> library
> > > > dynamic path search:
> > > >          
> > > >    SHLIB_PATH 
> > > >    enabled  second 
> > > >          
> > > >    embedded path 
> > > > enabled   first 
> > > > /work/AXIS_HP/axis2c-src-1.5.0/lib
> > > >          internal
> name:
> > > >          
> > > >    libaxis2_engine.so.5
> > > >          shared
> library
> > > > list:
> > > >          
> > > >    static   
> > > >
> /work/AXIS_HP/axis2c-src-1.5.0/lib/libneethi.so.5
> > > >          
> > > >    static   
> > > >
> > >
> /work/AXIS_HP/axis2c-src-1.5.0/lib/libaxis2_http_common.so.5
> > > >          
> > > >    static   
> > > >
> > >
> /work/AXIS_HP/axis2c-src-1.5.0/lib/libaxis2_axiom.so.5
> > > >          
> > > >    static   
> > > >
> > >
> /work/AXIS_HP/axis2c-src-1.5.0/lib/libaxis2_parser.so.5
> > > >          
> > > >    static   
> > > >
> /work/AXIS_HP/axis2c-src-1.5.0/lib/libguththila.so.5
> > > >          
> > > >    static   
> > > >
> /work/AXIS_HP/axis2c-src-1.5.0/lib/libaxutil.so.5
> > > >          
> > > >   
> dynamic   /usr/lib/libpthread.1
> > > >          
> > > >   
> dynamic   /usr/lib/libc.2
> > > > 
> > > > Ramesh.
> > > > 
> > > > 
> > > > --- On Fri, 18/2/11, Thomas Gentsch <tg@e-tge.de>
> > > > wrote:
> > > > 
> > > > > From: Thomas Gentsch <tg@e-tge.de>
> > > > > Subject: Re: Axis2C build on HP 11.11
> (32 bit)
> > > > > To: "Apache AXIS C User List" <c-user@axis.apache.org>
> > > > > Date: Friday, 18 February, 2011, 1:45
> AM
> > > > > 
> > > > > Hi Ramesh!
> > > > > 
> > > > > On Thu, 2011-02-17 at 16:14 +0530,
> ramesh Gopal
> > > > wrote:
> > > > > > Hello,
> > > > > > 
> > > > > > I am trying to do an AXIS2C build
> on HP
> > > 11.11
> > > > (32
> > > > > bit).
> > > > > > 
> > > > > > I have modified some CFLAGS and
> LDFLAGS,
> > > and
> > > > > accordingly changed a few source files
> to
> > > include
> > > > platform
> > > > > specific header files. The compilation
> goes fine
> > > and
> > > > also
> > > > > the axis distribution is done.
> > > > > > 
> > > > > > But when I see ldd
> libaxis2_engine.so, I
> > > see
> > > > something
> > > > > like :
> > > > > > 
> > > > > >
> > > > >
> > > >
> > >
> /work/AXIS_HP/axis2c-src-1.5.0/axiom/src/core/engine/.libs/libaxis2_engine.so
> > > > > => 
> > > > >
> > > >
> > >
> /work/AXIS_HP/axis2c-src-1.5.0/axiom/src/core/engine/.libs/libaxis2_engine.so
> > > > > 
> > > > > What is the problem exactly?
> > > > > The fact, that ldd prints the output
> above is
> > > not
> > > > > necessarily bad - ldd
> > > > > just resolves the libs as the loader
> does and if
> > > it
> > > > finds
> > > > > that lib with
> > > > > the path /work/... - fine.
> > > > > 
> > > > > > So, if you see here the portion
> before
> > > "=>"
> > > > has a
> > > > > hard-coded path.
> > > > > > 
> > > > > > So, when I take the axis tar file
> and try
> > > to
> > > > extract
> > > > > on a different machine, because this
> path
> > > > "/work/AXIS_HP"
> > > > > won't exist on other machines, the
> extraction
> > > fails.
> > > > > 
> > > > > If you do the ldd on another machine,
> ldd should
> > > say
> > > > > something like:
> > > > >  libaxis2_engine.so => not
> found 
> > > > > right?
> > > > > 
> > > > > Please provide the command output when
> linking
> > > the
> > > > > libaxis2_engine.so.
> > > > > Also, on HP-UX there is a command
> "chatr" which
> > > tells
> > > > you
> > > > > the libs of
> > > > > dependent libs, locating strategies and
> built-in
> > > > library
> > > > > paths.
> > > > > What does that command say?
> > > > > 
> > > > > BTW: This is PA-RISC? What does "uname
> -a" say?
> > > > > 
> > > > > Rgds,
> > > > >   tge
> > > > > 
> > > > > > On other platforms, HPIA/ AIX/
> Linux etc,
> > > the
> > > > file is
> > 
> > > > > displayed as :
> > > > > > 
> > > > > > libaxis2_engine.so => 
> > > > >
> > > >
> > >
> /work/AXIS/axis2c-src-1.5.0/axiom/src/core/engine/.libs/libaxis2_engine.so
> > > > > > 
> > > > > > 
> > > > > > Can somebody tell me which is the
> flag which
> > > that
> > > > do
> > > > > the trick for me ?
> > > > > > 
> > > > > > Rgds,
> > > > > > Ramesh.
> > > > > > 
> > > > > > 
> > > > > > 
> > > > > >
> > > > >
> > > >
> > >
> ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: c-user-unsubscribe@axis.apache.org
> > > > > > For additional commands, e-mail:
> c-user-help@axis.apache.org
> > > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > >
> > > >
> > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: c-user-unsubscribe@axis.apache.org
> > > > > For additional commands, e-mail: c-user-help@axis.apache.org
> > > > > 
> > > > > 
> > > > 
> > > > 
> > > > 
> > > >
> > >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: c-user-unsubscribe@axis.apache.org
> > > > For additional commands, e-mail: c-user-help@axis.apache.org
> > > > 
> > > > 
> > > 
> > > 
> > > 
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: c-user-unsubscribe@axis.apache.org
> > > For additional commands, e-mail: c-user-help@axis.apache.org
> > > 
> > > 
> > 
> > 
> > 
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: c-user-unsubscribe@axis.apache.org
> > For additional commands, e-mail: c-user-help@axis.apache.org
> > 
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: c-user-unsubscribe@axis.apache.org
> For additional commands, e-mail: c-user-help@axis.apache.org
> 
> 



---------------------------------------------------------------------
To unsubscribe, e-mail: c-user-unsubscribe@axis.apache.org
For additional commands, e-mail: c-user-help@axis.apache.org


Mime
View raw message