[ADOL-C] Problem adolc-2.4.1 with --enable-debug

[Kshitij Kulshreshtha]

Well the CFLAGS and CXXFLAGS exported by the shell take precedence over
everything. What you pass explicitely --with-cflags= --with-cxxflags=
gets added to that.

Passing --enable-debug or --enable-harddebug to configure changes the
implementation of some functions in ADOL-C and adds extra output on
stderr. So that is not the same as just having debugging symbols,
although they also add -g -O0 to the command line unless overridden by
shell exported CFLAGS CXXFLAGS.

So if you just need the debugging symbols in the library it is best to
simply unset CFLAGS and CXXFLAGS in shell and pass --with-cflags and
--with-cxxflags to configure. So this should work:

     unset CFLAGS CXXFLAGS
     ./configure --with-cflags='-g -O0' --with-cxxflags='-g -O0'


As on 2014-02-26 19:35, Brad Bell did write:
> No, the problem was fixed in ADOL-C-2.5.0, but further investigation
> revealed a related problem.
> 
> It appear that if one wishes to compile a debugging version of adolc,
> one should do the following
>     export CFLAGS='-g -O0'
>     export CXXFLAGS='-g -O0'
>     configure --with-cflags='-g -O0' --with-cxxflags='-g -O0'
> 
> If I do not set CFLAGS and CXXFLAGS as above, and I check config.log, I
> see that the settings for these flags are confused.
> 
> There is some discussion of this under the heading Variable:**CFLAGS on
> http://www.gnu.org/software/autoconf/manual/autoconf-2.67/html_node/Preset-Output-Variables.html
> but it is not entirely clear to me.
> 
> 
> 
> On 2/26/2014 5:44 AM, Kshitij Kulshreshtha wrote:
>> Does the error persist in ADOL-C-2.5.0?
>>

-- 
Dr. Kshitij Kulshreshtha

Institut für Mathematik,
Universität Paderborn,
Warburger Straße 100,
33098 Paderborn.

Büro: A3.235

Privatanschrift:
Arnikaweg 62
33100 Paderborn.