[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Problems Compiling Lilypond with gcc-3.3
From: |
Jonathan Levi MD |
Subject: |
Problems Compiling Lilypond with gcc-3.3 |
Date: |
Sun, 20 Jul 2003 21:08:52 -0400 |
Dear Lilypond Developers:
Recently I attempted to build and install lilypond 1.6.10-2 from
source, using fink (MacOS X 10.2.6) and gcc 3.3.
compilation failed repeatedly, with the messages:
rm -f ./out/a2-engraver.dep;
DEPENDENCIES_OUTPUT="./out/a2-engraver.dep ./out/a2-engraver.o" c++
-c -DHAVE_CONFIG_H -DSTRING_UTILS_INLINED -Iinclude -I./out
-I../flower/include -I../flower/./out -I../flower/include -O2
-finline-functions -g -no-cpp-precomp -I/sw/include -I/sw/include
-O2 -finline-functions -g -no-cpp-precomp -I/sw/include
-I/sw/include -Wall -W -Wmissing-prototypes -Wconversion -o
out/a2-engraver.o a2-engraver.cc
a2-engraver.cc:203:19: missing terminating " character
a2-engraver.cc:212:1: missing terminating " character
a2-engraver.cc:214:19: missing terminating " character
a2-engraver.cc:215:97: missing terminating " character
a2-engraver.cc:217:21: macro "ENTER_DESCRIPTION" passed 11 arguments,
but takes just 6
a2-engraver.cc:217: warning: ISO C++ forbids declaration of `ENTER_DESCRIPTION'
with no type
gnumake[1]: *** [out/a2-engraver.o] Error 1
gnumake: *** [all] Error 2
### execution of ulimit failed, exit code 2
Failed: compiling lilypond-1.6.10-2 failed
One of the members of the fink Beginners' List kindly showed me an
Apple web page, advising of compatibility problems between fink and
gcc 3.3, and explaining how to use the earier gcc 3.1 compiler. When
I did that, lilypond compiled and installed successfully, but still
with warnings like:
a2-engraver.cc:203:19: warning: \
multi-line string literals are deprecated
If it has been planned that the use of multi-line string literals is
to become obsolete, shouldn't the code in the appropriate source
files be changed, i.e. put backslashes before newlines in multiline
string literals? In particular, many of the ENTER_DESCRIPTION entries
have this problem, as in the following (from a2-engraver.cc):
ENTER_DESCRIPTION(A2_engraver,
/* descr */ "Part combine engraver for orchestral scores.
The markings @emph{a2}, @emph{Solo} and @emph{Solo II}, are
created by this engraver. It also acts upon instructions of the part
combiner. Another thing that the this engraver, is forcing of stem,
slur and tie directions, always when both threads are not identical;
up for the musicexpr called @code{one}, down for the musicexpr called
@code{two}.
",...
Thank you for Lilypond,
Jonathan
- Problems Compiling Lilypond with gcc-3.3,
Jonathan Levi MD <=