Renato Botelho | 5 Jul 2011 02:32
Picon
Gravatar

Error building clamav 0.97.1 with external llvm 2.9

Hello,

I can build 20110704 snapshot with external llvm-2.9 on FreeBSD
8.2 without problems, but on 0.97.1 i got the following error:

gmake[3]: Leaving directory
`/work/a/ports/security/clamav/work/clamav-0.97.1/libltdl'
gmake[2]: Leaving directory
`/work/a/ports/security/clamav/work/clamav-0.97.1/libltdl'
Making all in libclamav
gmake[2]: Entering directory
`/work/a/ports/security/clamav/work/clamav-0.97.1/libclamav'
gmake  all-recursive
gmake[3]: Entering directory
`/work/a/ports/security/clamav/work/clamav-0.97.1/libclamav'
Making all in c++
gmake[4]: Entering directory
`/work/a/ports/security/clamav/work/clamav-0.97.1/libclamav/c++'
gmake  all-am
gmake[5]: Entering directory
`/work/a/ports/security/clamav/work/clamav-0.97.1/libclamav/c++'
  CXX    libclamavcxx_la-bytecode2llvm.lo
/bin/sh ./libtool --silent --tag=CXX   --mode=compile c++
-DHAVE_CONFIG_H -I.  -I./../.. -I./.. -I./../../  -I/usr/local/include
  -I./../.. -I./.. -I./../../  -I/usr/local/include  -DNDEBUG
-D_GNU_SOURCE -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -O2
-fno-exceptions -fno-rtti -fPIC -Woverloaded-virtual -Wcast-qual
-fexceptions -DLLVM28 -DLLVM29 -O2 -pipe -march=i486
-fno-strict-aliasing -c -o libclamavcxx_la-bytecode2llvm.lo `test -f
'bytecode2llvm.cpp' || echo './'`bytecode2llvm.cpp
(Continue reading)

Török Edwin | 5 Jul 2011 08:14
Favicon

Re: Error building clamav 0.97.1 with external llvm 2.9

On 07/05/2011 03:32 AM, Renato Botelho wrote:
> Hello,
> 
> I can build 20110704 snapshot with external llvm-2.9 on FreeBSD
> 8.2 without problems, but on 0.97.1 i got the following error:
> 
> gmake[3]: Leaving directory
> `/work/a/ports/security/clamav/work/clamav-0.97.1/libltdl'
> gmake[2]: Leaving directory
> `/work/a/ports/security/clamav/work/clamav-0.97.1/libltdl'
> Making all in libclamav
> gmake[2]: Entering directory
> `/work/a/ports/security/clamav/work/clamav-0.97.1/libclamav'
> gmake  all-recursive
> gmake[3]: Entering directory
> `/work/a/ports/security/clamav/work/clamav-0.97.1/libclamav'
> Making all in c++
> gmake[4]: Entering directory
> `/work/a/ports/security/clamav/work/clamav-0.97.1/libclamav/c++'
> gmake  all-am
> gmake[5]: Entering directory
> `/work/a/ports/security/clamav/work/clamav-0.97.1/libclamav/c++'
>   CXX    libclamavcxx_la-bytecode2llvm.lo
> /bin/sh ./libtool --silent --tag=CXX   --mode=compile c++
> -DHAVE_CONFIG_H -I.  -I./../.. -I./.. -I./../../  -I/usr/local/include
>   -I./../.. -I./.. -I./../../  -I/usr/local/include  -DNDEBUG
> -D_GNU_SOURCE -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -O2
> -fno-exceptions -fno-rtti -fPIC -Woverloaded-virtual -Wcast-qual
> -fexceptions -DLLVM28 -DLLVM29 -O2 -pipe -march=i486
> -fno-strict-aliasing -c -o libclamavcxx_la-bytecode2llvm.lo `test -f
(Continue reading)

Renato Botelho | 5 Jul 2011 16:08
Picon
Gravatar

Re: Error building clamav 0.97.1 with external llvm 2.9

2011/7/5 Török Edwin <edwin <at> clamav.net>:
>
> The file is in git in two places, but only one was in Makefile.am, and 'make dist' only included one of them,
not both.
> When building with internal LLVM it uses llvm/include/llvm/Analysis/PointerTracking.h, which is
included in the tarball,
> with external LLVM it simply wants to use PointerTracking.h, which was not.
> I fixed the makefile on master, so that on next release we don't make this mistake again.
>
> Here is the PointerTracking.h file that you can add to the ports collection:
> http://git.clamav.net/gitweb?p=clamav-devel.git;a=blob_plain;f=libclamav/c%2B%2B/PointerTracking.h;hb=ba1dc7ffcbbec724f61ba9ec5c3da7df25a8bc0b
> It has to go in libclamav/c++/PointerTracking.h

Thanks Török, it worked fine, i'll commit it tonight.

--

-- 
Renato Botelho
_______________________________________________
http://lurker.clamav.net/list/clamav-devel.html
Please submit your patches to our Bugzilla: http://bugs.clamav.net

Andrey V. Martyanov | 8 Jul 2011 23:26
Picon
Gravatar

Is clamav lgpl compatible?

Hi! I see that Immunet uses libclamav.dll. Doesn't this violate the clamav
license? For example, I'd like to build my own closed source commercial
antivirus kit with the clamav engine. May I do that?
_______________________________________________
http://lurker.clamav.net/list/clamav-devel.html
Please submit your patches to our Bugzilla: http://bugs.clamav.net

Török Edwin | 9 Jul 2011 09:03
Picon

Re: Is clamav lgpl compatible?

On 07/09/2011 12:26 AM, Andrey V. Martyanov wrote:
> Hi! I see that Immunet uses libclamav.dll. Doesn't this violate the clamav
> license?

Immunet is part of Sourcefire.

> For example, I'd like to build my own closed source commercial
> antivirus kit with the clamav engine. May I do that?

No.

Best regards,
--Edwin
_______________________________________________
http://lurker.clamav.net/list/clamav-devel.html
Please submit your patches to our Bugzilla: http://bugs.clamav.net

Andrey V. Martyanov | 9 Jul 2011 09:49
Picon
Gravatar

Re: Is clamav lgpl compatible?

Thanks for your explanation. And what options do I have? Clamwin uses
interprocess communication with clamscan. Is it the only option? I
found COPYING.LGPL in clamav source tree. What parts of the software are
covered under this license? Sorry, but I can't find any useful information
on the topic except clamav's GPL v2 compatibility marked on it's site.

2011/7/9 Török Edwin <edwintorok <at> gmail.com>

> On 07/09/2011 12:26 AM, Andrey V. Martyanov wrote:
> > Hi! I see that Immunet uses libclamav.dll. Doesn't this violate the
> clamav
> > license?
>
> Immunet is part of Sourcefire.
>
> > For example, I'd like to build my own closed source commercial
> > antivirus kit with the clamav engine. May I do that?
>
> No.
>
> Best regards,
> --Edwin
> _______________________________________________
> http://lurker.clamav.net/list/clamav-devel.html
> Please submit your patches to our Bugzilla: http://bugs.clamav.net
>
_______________________________________________
http://lurker.clamav.net/list/clamav-devel.html
Please submit your patches to our Bugzilla: http://bugs.clamav.net

(Continue reading)

Chris Rees | 9 Jul 2011 12:25
Picon
Favicon
Gravatar

Re: Is clamav lgpl compatible?

On 9 July 2011 08:49, Andrey V. Martyanov <realduke <at> gmail.com> wrote:
> Thanks for your explanation. And what options do I have? Clamwin uses
> interprocess communication with clamscan. Is it the only option? I
> found COPYING.LGPL in clamav source tree. What parts of the software are
> covered under this license? Sorry, but I can't find any useful information
> on the topic except clamav's GPL v2 compatibility marked on it's site.
>

You could release your software as free software? If ClamAV has saved
you from writing your own engine then surely you could return the
favour?

Remember free/open-source doesn't mean no cost...

Chris
_______________________________________________
http://lurker.clamav.net/list/clamav-devel.html
Please submit your patches to our Bugzilla: http://bugs.clamav.net

Andrey V. Martyanov | 9 Jul 2011 12:50
Picon
Gravatar

Re: Is clamav lgpl compatible?

My company prefer closed source strategy, there are several reasons. Yes,
ClamAV can save us from writing custom engine. Our goal is to develop
all-in-one antivirus solution (realtime scanner, update manager etc). Now
it's unreasonable to build custom anti-virus engine, signature bases, memory
scanner and all the stuff. The best solution is to attach the libclamav and
to use the native antivirus bases. But we don't want to violate the GPL
license. LGPL can save us, but it's unclear which parts of ClamAV
destributed under the LGPL license.

On Sat, Jul 9, 2011 at 3:25 PM, Chris Rees <crees <at> freebsd.org> wrote:

> On 9 July 2011 08:49, Andrey V. Martyanov <realduke <at> gmail.com> wrote:
> > Thanks for your explanation. And what options do I have? Clamwin uses
> > interprocess communication with clamscan. Is it the only option? I
> > found COPYING.LGPL in clamav source tree. What parts of the software are
> > covered under this license? Sorry, but I can't find any useful
> information
> > on the topic except clamav's GPL v2 compatibility marked on it's site.
> >
>
> You could release your software as free software? If ClamAV has saved
> you from writing your own engine then surely you could return the
> favour?
>
> Remember free/open-source doesn't mean no cost...
>
> Chris
> _______________________________________________
> http://lurker.clamav.net/list/clamav-devel.html
> Please submit your patches to our Bugzilla: http://bugs.clamav.net
(Continue reading)

Chris Rees | 9 Jul 2011 13:07
Picon
Favicon
Gravatar

Re: Is clamav lgpl compatible?

On 9 July 2011 11:50, Andrey V. Martyanov <realduke <at> gmail.com> wrote:
> My company prefer closed source strategy, there are several reasons. Yes,
> ClamAV can save us from writing custom engine. Our goal is to develop
> all-in-one antivirus solution (realtime scanner, update manager etc). Now
> it's unreasonable to build custom anti-virus engine, signature bases, memory
> scanner and all the stuff. The best solution is to attach the libclamav and
> to use the native antivirus bases. But we don't want to violate the GPL
> license. LGPL can save us, but it's unclear which parts of ClamAV
> destributed under the LGPL license.
>

The usual protocol is to approach the copyright holders and negotiate
an alternative license.

You'll have more luck on:

https://clamsupport.sourcefire.com/

Chris
_______________________________________________
http://lurker.clamav.net/list/clamav-devel.html
Please submit your patches to our Bugzilla: http://bugs.clamav.net

Marc Balmer | 9 Jul 2011 13:27
Picon
Favicon

Re: Is clamav lgpl compatible?

Am 09.07.2011 12:50, schrieb Andrey V. Martyanov:
> My company prefer closed source strategy, there are several reasons. Yes,
> ClamAV can save us from writing custom engine. Our goal is to develop
> all-in-one antivirus solution (realtime scanner, update manager etc). Now
> it's unreasonable to build custom anti-virus engine, signature bases, memory
> scanner and all the stuff. The best solution is to attach the libclamav and
> to use the native antivirus bases. But we don't want to violate the GPL
> license. LGPL can save us, but it's unclear which parts of ClamAV
> destributed under the LGPL license.

The documentation states rather clearly that LibClamAV is GPL, not LGPL.
See http://www.clamav.net/doc/latest/html/node35.html.

Why don't you run the ClamAV daemon unaltered (you could even start it
from your software) and then use the well documented interface for
scanning? (see http://www.clamav.net/doc/latest/html/node28.html).

There is no performance penality in that, and when using file descriptor
passing on Unix, it is indeed very fast.

> 
> On Sat, Jul 9, 2011 at 3:25 PM, Chris Rees <crees <at> freebsd.org> wrote:
> 
>> On 9 July 2011 08:49, Andrey V. Martyanov <realduke <at> gmail.com> wrote:
>>> Thanks for your explanation. And what options do I have? Clamwin uses
>>> interprocess communication with clamscan. Is it the only option? I
>>> found COPYING.LGPL in clamav source tree. What parts of the software are
>>> covered under this license? Sorry, but I can't find any useful
>> information
>>> on the topic except clamav's GPL v2 compatibility marked on it's site.
(Continue reading)


Gmane