On Sunday 28 November 2004 16:25, Christian Hitz wrote:
> I got lilypond 2.5.2 to compile by doing the following things:
>
> - set _GLIBCPP_USE_C99 before #include in the files that use
> isinf/isnan
> - replace each occurrence of isinf/isnan with std::isinf/std::isnan
>
> I don't know if this bre
Hello list,
I have tried to analyze the "isinf issue", resulting from my "#include
cleanup" patch for LilyPond 2.5, and want to submit the following results,
created with gcc/g++/libc/libstdc++ 3.3.4 on SuSE Linux 9.2.
If you look at the LilyPond C++ sources you find that the issue with "isinf"
