[Clam-devel] impossible to compile CLAM in debug

David García Garzón dgarcia at iua.upf.edu
Tue May 15 07:19:37 PDT 2007


An 'scons configure' step is needed.

On Tuesday 15 May 2007 15:39:52 Xavier Amatriain wrote:
> Hi,
>
> You mean release=0, right? In any case, I have been debugging
> these past few weeks and find it extremely difficult to know what
> is going on when I change compile options. Have you tried recompiling
> all? Do you at least get debug symbols?
>
> Pau Arumi wrote:
> > i've found that changing the scons option release=1 in CLAM
> > doesn't recompile anything. which is somehow disturbing.
> > diving further i found that env['release'] is not used in the
> > SConscripts.  so now all CLAM_DEBUG_ASSERTS are ignored!
> >
> > i can't remember any change that removed this.
> > david, xavi: ideas?
> >
> > pau
> >
> >
> > _______________________________________________
> > Clam-devel mailing list
> > Clam-devel at llistes.projectes.lafarga.org
> > https://llistes.projectes.lafarga.org/cgi-bin/mailman/listinfo/clam-devel
>
> _______________________________________________
> Clam-devel mailing list
> Clam-devel at llistes.projectes.lafarga.org
> https://llistes.projectes.lafarga.org/cgi-bin/mailman/listinfo/clam-devel






More information about the clam-devel mailing list