Re: [Wrapper-user] About Wrapper lib files

[Andreas W. <and...@em...>]

Leif,

a patch is very simple. You should simply replace the occurance of "ld" with "$(COMPILE)" in the Makefile.linux. It is always better to link also with gcc (it calls ld with the proper options) when using it for compilation.

A quite good overview of tools and its options for creating libraries on a variety of platforms is here: http://www.fortran-2000.com/ArnaudRecipes/sharedlib.html.

Cheers,
Andreas

> 
> Andreas,
> 
> Andreas Wendt wrote:
> 
> >Prashant,
> >
> >to verify, which additional libraries a shared library or an executable depend on, you may issue the command "ldd" on it.
> >So "ldd wrapper" gives me on a SuSE Linux Enterprise 8 (I have no RedHat here):
> >
> >        libc.so.6 => /lib/i686/libc.so.6 (0x40022000)
> >        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
> >
> >For libwrapper.so I get:
> >        statically linked
> >
> >(Leif: was the static linking for the JNI library intentional?)
> >  
> >
> No it was not intentional.  As it long as it does not increase the 
> possibility of users
> having compatibility problems, I would be happy to apply any patches to 
> clean this
> up. :-)
> 
> >The binaries are not linked with explicit library dependency, so the GNU linker decides which libraries to link in my default (libc.so in this case; ld-linux.so is linked in by libc.so and is no direct dependency).
> >
> >ldd will also show you if there are missing dependencies.
> >  
> >
> Cheers,
> Leif
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user