+
+
+1.4.3.jcn2
+==========
+
+* Included documentatioon and post-flex lexer.cc patch for
+Debian/unstable gcc-3.0.
+
+* Enhanced gcc autoconf and make messages.
+
+* Added -mieee to CFLAGS for alpha.
+
+* Fixed help and documentation of new LilyPond command line.
+
+* Redirected SuSE download to ftp.lilypond.org (where mirror script runs).
+
+1.4.3
+=====
+
1.4.2.jcn4
==========
If you want to compile LilyPond from source, download here:
@itemize @bullet
@item Download development releases from
+@c Hmm, these won't show up in lilypond.org/stats
+@c Otoh, lilypond.org is not updated when release mail arrives
@uref{ftp://ftp.cs.uu.nl/pub/GNU/LilyPond/} by FTP and
@uref{http://ftp.cs.uu.nl/pub/GNU/LilyPond/}, by HTTP.
@item @uref{ftp://sca.uwaterloo.ca/pub/} by FTP (Canadian mirror)
@uref{ftp://ftp.cs.uu.nl/pub/GNU/LilyPond/binaries/}.
You can also compile them yourself. A spec file is in
-@file{make/out/redhat.spec}. This file is distributed along with the
-sources. You can make the rpm by issuing
+@file{make/out/lilypond.redhat.spec}. This file is distributed along
+with the sources. You can make the rpm by issuing
@example
tar xfz lilypond-x.y.z.tar.gz
- rpm -bb lilypond-x.y.z/make/out/redhat.spec
+ rpm -bb lilypond-x.y.z/make/out/lilypond.redhat.spec
rpm -i /usr/src/redhat/RPMS/i386/lilypond-x.y.z
@end example
Some LinuxPPC RPMS should available from
@uref{ftp://ftp.cs.uu.nl/pub/GNU/LilyPond/binaries/}.
-A LinuxPPC RPM can be made using the @file{redhat.spec} file.
+A LinuxPPC RPM can be made using the @file{lilypond.redhat.spec} file.
@subsection SuSE
Some SUSE RPMS should available from
-@uref{ftp://ftp.cs.uu.nl/pub/GNU/LilyPond/binaries/}.
+@uref{ftp://ftp.lilypond.org/pub/LilyPond/binaries/SuSE}.
You can also compile a RPM for SUSE yourself. A spec file is in
-@file{make/out/suse.spec}, see the instructions for building the Red Hat
-RPM.
+@file{make/out/lilypond.suse.spec}, see the instructions for building
+the Red Hat RPM.
You must have the following packages: guile tcsh tetex te_latex te_kpath
te_mpost libpng python gpp libgpp gettext autoconf netpbm libnetpb
Bugs that are not fault of LilyPond are documented here.
+@unnumberedsubsec Debian GNU/Linux unstable gcc-3.0
+
+Flex (2.5.4a-11) in unstable does not produce g++-3.0 compliant C++
+code. To compile LilyPond with gcc-3.0 you may do:
+@example
+ CC=gcc-3.0 CXX=g++-3.0 ./configure
+ make conf=gcc-3.0 -C lily out-gcc-3.0/lexer.cc
+ patch -p1 < lexer-gcc-3.0.patch
+ make conf=gcc-3.0 -C lily
+@end example
+
@unnumberedsubsec NetBSD
@itemize @bullet
-dnl WARNING WARNING WARNING WARNING
-dnl do not edit! this is aclocal.m4, generated from stepmake/aclocal.m4
dnl aclocal.m4 -*-shell-script-*-
dnl StepMake subroutines for configure.in
CFLAGS="$CFLAGS $OPTIMIZE"
CPPFLAGS=${CPPFLAGS:-""}
+
+ AC_MSG_CHECKING([for IEEE-conformance compiler flags])
+ save_cflags="$CFLAGS"
+ case "$host" in
+ alpha*-*-*)
+ dnl should do compile test?
+ AC_MSG_RESULT(-mieee)
+ CFLAGS="-mieee $CFLAGS"
+ ;;
+ *)
+ AC_MSG_RESULT([none])
+ ;;
+ esac
AC_SUBST(cross_compiling)
AC_SUBST(CFLAGS)
AC_SUBST(CPPFLAGS)
])
AC_DEFUN(AC_STEPMAKE_GXX, [
- # ugh autoconf
- # urg, egcs: how to check for egcs >= 1.1?
+ AC_MSG_CHECKING("g++ version")
+ cxx_version=`$CXX --version`
+ AC_MSG_RESULT("$cxx_version")
changequote(<<, >>)dnl
- if $CXX --version | egrep '2\.[89]' > /dev/null ||
- $CXX --version | grep 'egcs' > /dev/null
+ # urg, egcs: how to check for egcs >= 1.1?
+ if expr "$cxx_version" : '.*2\.[89]' > /dev/null ||
+ expr "$cxx_version" : '.*egcs' > /dev/null ||
+ expr "$cxx_version" : '3\.0' > /dev/null
changequote([, ])dnl
then
true
else
- AC_STEPMAKE_WARN(can\'t find g++ 2.8, 2.9 or egcs 1.1)
+ AC_STEPMAKE_WARN(can\'t find g++ 2.8, 2.9, 3.0 or egcs 1.1)
fi
])
AC_ARG_ENABLE(config,
[ --enable-config=CONF put settings in config-CONF.make and config-CONF.h;
do \`make conf=CONF' to get output in ./out-CONF],
- [CONFIGSUFFIX=-$enableval])
+ [CONFIGURATION=$enableval])
+ test -n "$CONFIGURATION" && CONFIGSUFFIX="-$CONFIGURATION"
CONFIGFILE=config$CONFIGSUFFIX
AC_SUBST(CONFIGSUFFIX)
AC_STEPMAKE_END
+test -n "$CONFIGURATION" && mc=" conf=$CONFIGURATION" || mc=""
+
cat <<EOF
Type:
- make all to build LilyPond
- make install to install LilyPond
- make help to see all possible targets
+ make$mc all to build LilyPond
+ make$mc install to install LilyPond
+ make$mc help to see all possible targets
Do not worry if ./Documentation or ./mutopia should not build.
EOF
CFLAGS="$CFLAGS $OPTIMIZE"
CPPFLAGS=${CPPFLAGS:-""}
+
+ AC_MSG_CHECKING([for IEEE-conformance compiler flags])
+ save_cflags="$CFLAGS"
+ case "$host" in
+ alpha*-*-*)
+ dnl should do compile test?
+ AC_MSG_RESULT(-mieee)
+ CFLAGS="-mieee $CFLAGS"
+ ;;
+ *)
+ AC_MSG_RESULT([none])
+ ;;
+ esac
AC_SUBST(cross_compiling)
AC_SUBST(CFLAGS)
AC_SUBST(CPPFLAGS)
])
AC_DEFUN(AC_STEPMAKE_GXX, [
- # ugh autoconf
- # urg, egcs: how to check for egcs >= 1.1?
+ AC_MSG_CHECKING("g++ version")
+ cxx_version=`$CXX --version`
+ AC_MSG_RESULT("$cxx_version")
changequote(<<, >>)dnl
- if $CXX --version | egrep '2\.[89]' > /dev/null ||
- $CXX --version | grep 'egcs' > /dev/null
+ # urg, egcs: how to check for egcs >= 1.1?
+ if expr "$cxx_version" : '.*2\.[89]' > /dev/null ||
+ expr "$cxx_version" : '.*egcs' > /dev/null ||
+ expr "$cxx_version" : '3\.0' > /dev/null
changequote([, ])dnl
then
true
else
- AC_STEPMAKE_WARN(can\'t find g++ 2.8, 2.9 or egcs 1.1)
+ AC_STEPMAKE_WARN(can\'t find g++ 2.8, 2.9, 3.0 or egcs 1.1)
fi
])
AC_ARG_ENABLE(config,
[ --enable-config=CONF put settings in config-CONF.make and config-CONF.h;
do \`make conf=CONF' to get output in ./out-CONF],
- [CONFIGSUFFIX=-$enableval])
+ [CONFIGURATION=$enableval])
+ test -n "$CONFIGURATION" && CONFIGSUFFIX="-$CONFIGURATION"
CONFIGFILE=config$CONFIGSUFFIX
AC_SUBST(CONFIGSUFFIX)
projects / lilypond.git / commitdiff