Read in INSTALL.txt about problems with incompatibility between
certain versions of gcc 3.x and flex. Also, you will find lots
of comments on these problems if you search the mailing list
archives for bug-lilypond and lilypond-user.

Mats

Chris Staskewicz wrote:
I've been trying to compile lilypond 2.0 on a FreeBSD machine.  Configure
completed with a "warning".  However, I tried to compile anyway.  It seems
that the warning and the compile error are independent of each other.  I
was wondering if there was a work-around or an update?

Thanks,

Chris.


# Warning


checking kpathsea/kpathsea.h usability... no
checking kpathsea/kpathsea.h presence... yes
configure: WARNING: kpathsea/kpathsea.h: present but cannot be compiled
configure: WARNING: kpathsea/kpathsea.h: check for missing prerequisite headers?
configure: WARNING: kpathsea/kpathsea.h: proceeding with the preprocessor's result
configure: WARNING:     ## ------------------------------------ ##
configure: WARNING:     ## Report this to [EMAIL PROTECTED] ##
configure: WARNING:     ## ------------------------------------ ##
checking for kpathsea/kpathsea.h... yes
checking for kpse_find_file in -lkpathsea... yes
checking for kpse_find_file... yes
checking whether to use kpathsea... yes

# Compile time error

gmake[1]: Entering directory `/usr/local/lilypond-2.0.1/lily'
rm -f ./out/lexer.dep; DEPENDENCIES_OUTPUT="./out/lexer.dep ./out/lexer.o"
/usr/local/bin/g++32 -c -DHAVE_CONFIG_H  -DSTRING_UTILS_INLINED -Iinclude -I./out
-I../flower/include -I../flower/./out -I../flower/include -O2 -finline-functions -g
-I/usr/local/include/kpathsea -I/usr/local/include/python2.3
-I/usr/local/include     -O2 -finline-functions -g
-I/usr/local/include/kpathsea -I/usr/local/include/python2.3 -I/usr/local/include 
-Wall  -W
-Wmissing-prototypes -Wconversion  -o out/lexer.o out/lexer.cc
In file included from
/usr/local/lib/gcc-lib/i386-portbld-freebsd4.9/3.2.3/include/g++-v3/backward/iostream.h:31,
                 from /usr/local/include/FlexLexer.h:47,
                 from out/lexer.cc:243:
/usr/local/lib/gcc-lib/i386-portbld-freebsd4.9/3.2.3/include/g++-v3/backward/backward_warning.h:32:2:
warning:
#warning This file includes at least one deprecated or antiquated header.
Please consider using one of the 32
headers found in section 17.4.1.2 of the C++ standard. Examples include
substituting the <X> header for the
<X.h> header for C++ includes, or <sstream> instead of the deprecated
header <strstream.h>. To disable this
warning use -Wno-deprecated.
In file included from /usr/local/include/FlexLexer.h:47,
                 from out/lexer.cc:243:
/usr/local/lib/gcc-lib/i386-portbld-freebsd4.9/3.2.3/include/g++-v3/backward/iostream.h:36:
using
   declaration `istream' introduced ambiguous type `istream'
out/lexer.cc: In member function `virtual int My_lily_lexer::yylex()':
out/lexer.cc:4176: cannot convert `std::istream*' to `istream*' in
assignment
out/lexer.cc: In member function `void
yyFlexLexer::yy_load_buffer_state()':
out/lexer.cc:4699: cannot convert `istream*' to `std::istream*' in
assignment
out/lexer.cc: In member function `void
   yyFlexLexer::yy_init_buffer(yy_buffer_state*, std::istream*)':
out/lexer.cc:4750: cannot convert `std::istream*' to `istream*' in
assignment
/usr/local/lib/gcc-lib/i386-portbld-freebsd4.9/3.2.3/include/g++-v3/bits/locale_facets.h:
At
   top level:
out/lexer.cc:3193: warning: `int yy_start_stack_ptr' defined but not used
out/lexer.cc:3194: warning: `int yy_start_stack_depth' defined but not
used
out/lexer.cc:3195: warning: `int*yy_start_stack' defined but not used



_______________________________________________
Bug-lilypond mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-lilypond

-- ============================================= Mats Bengtsson Signal Processing Signals, Sensors and Systems Royal Institute of Technology SE-100 44 STOCKHOLM Sweden Phone: (+46) 8 790 8463 Fax: (+46) 8 790 7260 Email: [EMAIL PROTECTED] WWW: http://www.s3.kth.se/~mabe =============================================



_______________________________________________
Bug-lilypond mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-lilypond

Reply via email to