[Pkg-clamav-devel] package status for jessie

Scott Kitterman debian at kitterman.com
Mon Aug 25 21:31:07 UTC 2014


On August 25, 2014 5:19:42 PM EDT, Andreas Cadhalpun <andreas.cadhalpun at googlemail.com> wrote:
>Hi Sebastian,
>
>On 25.08.2014 21:25, Sebastian Andrzej Siewior wrote:
>> On 2014-08-25 00:38:55 [+0200], Andreas Cadhalpun wrote:
>>> Unless I'm missing something, linking statically against LLVM is the
>only
>>> option.
>>
>> either the debian LLVM package is br0ken or upstream. So I removed
>> -static option and rebuild on sid-i386 and nothing changed. Then I
>> applied this piece:
>>
>[...]
>>
>> it built and the testsuite passed. No unresovled symbols.
>
>Great!
>You didn't mention that the size of libclamav is reduced substantially 
>as well.
>
>>> Therefore I think we must add a Built-Using field [2] containing the
>>> corresponding LLVM version.
>>
>> Yeah. Or could we get llvm to link against the .so file? It seems to
>> work. It looks like the problem is with llvm-config. Its --libs
>option
>> lists all the -l switch for all .a files. It would make sense to link
>> against .so lib instead. I wonder why they do it this way because
>they
>> ship a .so file but there is no way to link against without
>hardcoding
>> the lib name…
>
>LLVM's llvm-config is a mess...
>So for now, I just hardcoded '-lLLVM-$llvmver' in configure.ac.
>
> > I just learnt that this is a bug in llvm-config and a bug
> > report + patch is welcome.
> > Will do this once my bigeasy branch gets merged…
>
>I would recommend to add a proper pkg-config file to LLVM instead of 
>trying to fix llvm-config. This should be simpler and the result more 
>likely to be useful. For example you can tell pkg-config, whether or
>not 
>you want to link statically.

I recall llvm 3.5 has some significant changes in its build system. I don't recall the details. It might be worth having a look to see how the changes might affect this. 

Scott K




More information about the Pkg-clamav-devel mailing list