[Pkg-clamav-devel] build clamav with system LLVM

[Scott Kitterman]

On Friday, May 02, 2014 23:10:02 Andreas Cadhalpun wrote:
> Hi,
> 
> On 02.05.2014 22:52, Scott Kitterman wrote:
> > On Friday, May 02, 2014 22:19:03 Andreas Cadhalpun wrote:
> >> An upload to experimental seems like a good idea.
> >> But keep in mind that experimental defaults to LLVM 3.4, while unstable
> >> still defaults to LLVM 3.3 (and wheezy to LLVM 3.0).
> > 
> > Build-deps will only get pulled from Experimental if they aren't satisfied
> > from Unstable, so we can do it with 3.3 or 3.4 depending on what you
> > want.
> It's just that depending on llvm-dev (as I did) will result in 3.4 in
> experimental and in 3.3 in unstable.
> As this shouldn't matter, because it builds fine with both, I'm in favor
> of leaving the generic dependency, i.e. upload to experimental and build
> against 3.4 there and afterwards upload to unstable and build against 3.3.
> 
> More or less related to this, I found on [1]:
> W implicit-declaration others.c:301
> 
> This can be trivially fixed by including the correct header
> (libxml/parser.h), see attached patch.
> Now I'm unsure as to where to push this change?
> To the unstable branch as 0009-*.patch, thus using the same number as
> for the LLVM patch, or to the aca_llvm branch as 0010-*.patch?
> I would tend to the latter and then both can be uploaded to experimental
> together.

The latter is fine, we just need to remember to grab it for an unstable upload 
if we do it before the LLVM situation is finalized.  Also, please file a bug and 
send the change upstream if you haven't.

Scott K
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/pkg-clamav-devel/attachments/20140502/0640f031/attachment.sig>