Edward Sanford Sutton writes: >> ==== >> In file work/lilypond-2.2.2/lily/includable-lexer.cc >> Inserted before line 30 the line: >> #define HAVE_FLEXLEXER_YY_CURRENT_BUFFER >> This turns off some code which fails to compile. > > Usually code is in place. Was this code unnecessary, or just turned off > because it was in the way of a successful compile?
Configure checks for this. IWBN if you could find out why HAVE_FLEXLEXER_YY_CURRENT_BUFFER is not defined by configure. >> ==== >> In file work/lilypond-2.2.2/lily/out/FlexLexer.h >> Changed several instances of std::std:: to std:: >> Changed several instances of std:std:: to std:: Btw: if FlexLexer.h needs patching, it means that the distribution (FreeBSD /ports?) is shipping a broken combination of the flex and g++ toolchain. Please report this as bug and get this fixed rather than patching LilyPond. This issue was resolved over 2.5 years ago, it has nothing to do with LilyPond, apart from using flex with g++. >> But - I trying upgrade port in ports tree to version 2.4.4 > > That version is beyond 2.3.20 and will have the makeinfo issues if I > remember right. I think the new lilypond dependency was makeinfo 4.7. Either > texinfo needs to be updated in the base system Yes, please update texinfo one way or the other. We're already stabilizing for lilypond 2.6; please avoid shipping anything else than the latest stable version, if at all possible. > Did the patch work without interfering with other systems too? > I think the best patches are the ones that > go into an original project rather than get applied to one distribution. This patch was taken from CVS HEAD. Thanks, Jan. -- Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
