There are (at least) two issues with the CVS contents of MFTrace 1.2.3:
(1) "sh autogen.sh" produces a "mftrace.spec" file that references two ".pyo"
files that "make" will not create.
(2) After building and installing "mftrace-1.2.3-1.i586.rpm", "mftrace
--version" fails, because of two "Unind
R. Mattes mh-freiburg.de> writes:
> Ok, i found the "bug". It looks like this is triggered
> by using guile-1.6.n instead of guile-1.8 - this also
> explains why Andreas' build failed.
Confirmed. After updating OpenSUSE 10.0 with guile-1.8.0, all is well again.
"make all web" runs to completion w
Am Mittwoch, 9. November 2005 10:36 schrieb Han-Wen Nienhuys:
> I don't understand this patch. Why doesn't str need a cast? What's the
> difference between reinterpret_cast and (const char*)
After updating to OpenSUSE 10.0 with g++ 4.0.2 the problem is gone. The CVS
code compiles without the patch
Dear group,
in order to compile (i.e., "rpmbuild -ba lilypond.spec") the latest CVS
contents on my system (SuSE 9.2 with g++ 3.3.4; all required package updates
are present), I have to applyto file the small
patch attached to this mail.
I would be very pleased to see the cast applied directl
On Friday 03 December 2004 19:11, Christian Hitz wrote:
> The proposed solution is to use instead of . In my
> patch I introduce a new define MACOS_X that controls this.
>
> With this patch applied I compiled the latest CVS this afternoon.
Compiles fine on GNU/Linux as well. Sure, it's a hack, b
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
quot;BSD-conforming" function/macro should be unavailable for use in C++
programs. My best guess is that BSD /only/ has the "isinf" /macro/ in
and no underlying "isinf" system /function/ reachable through a
different interface (like said /template function/ in on Linu
On Friday 19 November 2004 14:52, Han-Wen Nienhuys wrote:
> I've added the Doxygen file to CVS. I'm willing to add doxygen rules
> to the makefile, if someone writes them.
Unfortunately, I'm not proficient with 'autoconf', so I can't provide a
working solution right now. But here's what I've got
Hello list,
Has anyone considered to apply Doxygen to the LilyPond sources? I'm aware
that the internal comments are not doxygen'erated, however, Doxygen is
capable to analyze plain C/C++ codes and to generate at least rudimentary
"documentation" in various output formats.
One of the major ad
