dolfin team mailing list archive

[Mandus <mandus@xxxxxxxxx>]

On 4/3/06, Anders Logg <logg@xxxxxxxxx> wrote:
> On Mon, Apr 03, 2006 at 10:59:36PM +0200, Mandus wrote:
> > Dear dolfin'ers
> >
> > After doing a relatively plain configure of dolfin, my 'dolfin-config
> > --cflags' return the following (among other things):
> >
> > -DDEBUG=1 -g -O2 -Wall -Werror -ansi -std=c++98
> >
> > The problem is that the -Werror thing cause problem for me, when
> > linking dolfin and our internal software (pycc for those who knows).
> >
> > I'm using dolfin from 'hg', freshly pulled today.
> >
> > Is there a way to turn off those flags?
>
> The debugging flags are set by default to stop developers (including
> myself) from checking in code that compiles with warnings.
>
> Since it may cause problems, I will disable the debug flags by
> default. You can either wait for 30 seconds until I have pushed the
> update to the repository or comment out the following line in
> configure.ac and then run scripts/preconfigure:
>
> enable_debug="yes"

ok - more or less what I already did (actually, I just removed the
-Werror completely from configure.ac...)

I think this is a wise thing to have in the development tree, so it is
probably just me using the "wrong" version (hg vs. release)... The
problem I encounter, among other things, is that swig generates
wrapper code with variables that are never used, which gcc chockes on
when this flag is on. There are also some issues with python header
files combined with /usr/include/features.h, which is included
somehow.

Anyway, thanks

btw:
best regards, _dr_ Åsmund Ø. :-)


--
Mandus
The only mandus around.