Stephen Gran wrote:
>> This reminds me of https://wwws.clamav.net/bugzilla/show_bug.cgi?id=272
>>
>
> Yes, that's exactly the same issue.
>
Hi Stephen,
Check out latest SVN (r3462), it uses version maps.
The cli_* symbols have a different "version", they are marked
CLAMAV_PRIVATE.
I got t
On Tue, Nov 20, 2007 at 09:59:21PM +0200, Török Edwin said:
> Stephen Gran wrote:
> > Hi all,
> >
> > So I've been thinking about how to reduce the breakage that occasionally
> > happens to other bits of software on upgrades of libclamav, and I think
> > I've come up with something that might be of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
currently libclamav is used in a "static" way while
compiled as shared, I mean that all internal
functions are in the .so and binary that links
that are using them from the .so
cli_x functions should be internals and the executables
should link
Stephen Gran wrote:
> Hi all,
>
> So I've been thinking about how to reduce the breakage that occasionally
> happens to other bits of software on upgrades of libclamav, and I think
> I've come up with something that might be of some use. libtool lets you
> use a version script to (on platforms tha
Hi all,
So I've been thinking about how to reduce the breakage that occasionally
happens to other bits of software on upgrades of libclamav, and I think
I've come up with something that might be of some use. libtool lets you
use a version script to (on platforms that support it) hide symbols from
