Re: [AVFS] automake status report

> After googling around I confirmed my assumptions so I have two options.
> 1.Force the use of -version-script which only works with GNU ld and the
>   solaris ld.
> 2.Renaming the zlib symbols. Fortunatly the zlib already has some code
>   for this. I tested this and it works fine.
>   Symbol renaming in bzlib (which offers a BZ_API macro to do this) and
>   libneon is also required.
> 
> I prefer the second option even it's more work. A static library doesn't
> contain local or global symbol definition but I'm not sure what happens
> when one links a static avfs lib and a static zlib into a program.
> Symbol collisions could appear the same way.
> 
> I will ask on the libtool mailing list about this problem but I don't
> expect a portable solution to this.

Agreed.

Maybe you can conditionally still use the --version-script, if
available (it shouldn't be too hard to detect it in configure.in).

You could add something like this to Makefile.am:

libavfs_la_LDFLAGS = @VERSIONSCRIPT_OPTS@

And in configure.in conditionally do 

VERSIONSCRIPT_OPTS="-Wl,--version-script,libavfs.map"
AC_SUBST(VERSIONSCRIPT_OPTS)

Miklos




-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.  How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.  
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20