Re: [Getfem-users] make check error in bimaterial_crack_test on OS X 10.4 on Intel based Mac

[Koenraad Janssens]

In the newer compiler standard isnan is within std. So replacing replacing
isnan by std::isnan fixes the problem.

- Koen

On 3/11/06 10:43, "julien pommier" <address@hidden> wrote:

> Koenraad Janssens wrote:
>> Thanks Julien for helping me with the compile error.
>> 
>> Now the make check runs, but unfortunately another error pops up:
>> 
>> Making check in bimaterial_crack_test
>> make  bimaterial_crack_test
>> if g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I../../src -I../../src
>> -DGMM_USES_BLAS  -O3 -Wall -W -fmessage-length=0 -ftemplate-depth-40
>> -pedantic -Wshadow -Wpointer-arith -Wcast-qual -Wwrite-strings -Wconversion
>> -Wredundant-decls -Wno-long-double -Wno-long-long -MT
>> bimaterial_crack_test.o -MD -MP -MF ".deps/bimaterial_crack_test.Tpo" -c -o
>> bimaterial_crack_test.o bimaterial_crack_test.cc; \
>> then mv -f ".deps/bimaterial_crack_test.Tpo"
>> ".deps/bimaterial_crack_test.Po"; else rm -f
>> ".deps/bimaterial_crack_test.Tpo"; exit 1; fi
>> bimaterial_crack_test.cc: In function 'void
>> sol_ref_infinite_plane(bgeot::scalar_type, bgeot::scalar_type,
>> bgeot::scalar_type, bgeot::scalar_type, bgeot::scalar_type,
>> bgeot::scalar_type, bgeot::base_small_vector&, int, bgeot::base_matrix*)':
>> bimaterial_crack_test.cc:226: error: 'isnan' was not declared in this scope
>> bimaterial_crack_test.cc:231: error: 'isnan' was not declared in this scope
>> make[3]: *** [bimaterial_crack_test.o] Error 1
>> make[2]: *** [check-am] Error 2
>> make[1]: *** [check-recursive] Error 1
>> make: *** [check-recursive] Error 1
>> 
>> Now I understand what this error is and could go ahead and correct it
>> myself, but maybe you can tell me whether I can solve this with a configure
>> option? isnan is in some library, I just don't remember by heart which one.
>>   
> yes, isnan is unfortunately not always available.. I suggest that you
> just remove the offending lines, or just ignore bimaterial_crack_test as
> this program is not a "finished" and is still evolving
>