[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: LSR is not at the stable release level
From: |
James |
Subject: |
Re: LSR is not at the stable release level |
Date: |
Tue, 2 Oct 2012 17:21:13 +0100 |
Hello,
On 2 October 2012 17:08, Joseph Rushton Wakeling
<address@hidden> wrote:
> On 09/30/2012 02:39 PM, David Kastrup wrote:
>>
>> <URL:http://bugs.launchpad.net/ubuntu/+source/lilypond/+bug/1047693>
>
>
> Regarding Ubuntu, has anybody been contacted about this bug?
> https://bugs.launchpad.net/ubuntu/+source/lilypond/+bug/1021570
Nope. I am not really a dubugger, but have had enough experience with
compiling LilyPond (if not the binary installers) to try to help.
I took a visual scan
--snip--
./configure --disable-checking --enable-debugging \
--prefix=/usr --enable-optimising \
--infodir='${prefix}/share/info' \
--mandir='${prefix}/share/man'
configure: WARNING: unrecognized options: --disable-checking
checking build system type... x86_64-unknown-linux-gnu
checking Package... LILYPOND
checking builddir... /build/buildd/lilypond-2.14.2
checking for stepmake... ./stepmake (${datarootdir}/stepmake not found)
checking host system type... x86_64-unknown-linux-gnu
checking for gmake... no
checking for make... make
checking for find... find
checking for tar... tar
checking for bash... /bin/bash
checking for python... python
checking python version... 2.7.3
checking for python... /usr/bin/python
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether compiler understands -pipe... yes
checking for IEEE-conformance compiler flags... none
checking for fc-list... fc-list
checking New Century Schoolbook PFB files...
/usr/share/fonts/type1/gsfonts/c059016l.pfb
/usr/share/fonts/type1/gsfonts/c059036l.pfb
/usr/share/fonts/type1/gsfonts/c059033l.pfb
/usr/share/fonts/type1/gsfonts/c059013l.pfb
checking for python... /usr/bin/python
checking /usr/bin/python version... 2.7.3
checking for /usr/bin/python... /usr/bin/python
checking gcc version... 4.7.0
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking g++ version... 4.7.0
checking whether explicit instantiation is needed... no
checking for stl.data () method... yes
checking for ar... ar
checking for ranlib... ranlib
checking for dlopen in -ldl... yes
checking for dlopen... yes
checking for bison... bison -y
checking for bison... bison
checking bison version... 2.5
checking for flex... flex
checking how to run the C++ preprocessor... g++ -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking FlexLexer.h usability... yes
checking FlexLexer.h presence... yes
checking for FlexLexer.h... yes
checking for yyFlexLexer.yy_current_buffer... no
checking FlexLexer.h location... /usr/include/FlexLexer.h
checking language... English
checking for gettext in -lintl... no
checking for gettext... yes
checking for msgfmt... msgfmt
checking for mf-nowin... mf-nowin
checking for mpost... mpost
checking for working metafont mode... ljfour
checking for kpsewhich... kpsewhich
checking for guile-config... guile-config
checking guile-config version... 1.8.8
checking guile compile flags... -pthread
checking guile link flags... -pthread -lguile -lltdl
-Wl,-Bsymbolic-functions -lgmp -lcrypt -lm -lltdl
checking libguile.h usability... yes
checking libguile.h presence... yes
checking for libguile.h... yes
checking for scm_boot_guile in -lguile... yes
checking for scm_boot_guile... yes
checking for scm_t_hash_fold_fn... no
checking for scm_t_hash_handle_fn... no
checking for scm_t_subr... no
checking GUILE rational bugfix... ok
checking for python-config... python-config
checking Python.h usability... yes
checking Python.h presence... yes
checking for Python.h... yes
checking for gs... gs
checking for gs... /usr/bin/gs
checking /usr/bin/gs version... 9.05
checking for fontforge... fontforge
checking for fontforge... /usr/bin/fontforge
checking /usr/bin/fontforge version... 20110222
checking for fontforge... (cached) fontforge
checking for fontforge... (cached) /usr/bin/fontforge
checking /usr/bin/fontforge version... 20110222
checking for t1asm... t1asm
checking for t1asm... /usr/bin/t1asm
checking assert.h usability... yes
checking assert.h presence... yes
checking for assert.h... yes
checking grp.h usability... yes
checking grp.h presence... yes
checking for grp.h... yes
checking libio.h usability... yes
checking libio.h presence... yes
checking for libio.h... yes
checking pwd.h usability... yes
checking pwd.h presence... yes
checking for pwd.h... yes
checking for sys/stat.h... (cached) yes
checking wchar.h usability... yes
checking wchar.h presence... yes
checking for wchar.h... yes
checking fpu_control.h usability... yes
checking fpu_control.h presence... yes
checking for fpu_control.h... yes
checking sstream usability... yes
checking sstream presence... yes
checking for sstream... yes
checking whether stat file-mode macros are broken... no
checking for working memcmp... yes
checking for vprintf... yes
checking for _doprnt... no
checking for chroot... yes
checking for fopencookie... yes
checking for gettext... (cached) yes
checking for isinf... yes
checking for memmem... yes
checking for snprintf... yes
checking for vsnprintf... yes
checking for pkg-config... pkg-config
checking pkg-config version... 0.26
checking whether to enable dynamic relocation... no
checking for rpath linkage... no
checking for pangoft2 >= 1.6.0... yes
checking PANGO_FT2_CFLAGS... -pthread -I/usr/include/pango-1.0
-I/usr/include/freetype2 -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include
checking PANGO_FT2_LIBS... -lpangoft2-1.0 -lpango-1.0 -lfreetype
-lfontconfig -lgobject-2.0 -lglib-2.0
checking pango/pangoft2.h usability... yes
checking pango/pangoft2.h presence... yes
checking for pango/pangoft2.h... yes
checking for pango_ft2_font_map_create_context... yes
checking for fontconfig >= 2.4.0... yes
checking FONTCONFIG_CFLAGS...
checking FONTCONFIG_LIBS... -lfontconfig
checking for freetype2 >= 2.1.10... yes
checking FREETYPE2_CFLAGS... -I/usr/include/freetype2
checking FREETYPE2_LIBS... -lfreetype
checking host system type... (cached) x86_64-unknown-linux-gnu
checking host system type... (cached) x86_64-unknown-linux-gnu
checking for some flavor of Windows... no
checking for -windres... no
checking for windres... no
checking for guile... guile
checking for guile... /usr/bin/guile
checking for perl... perl
checking for perl... /usr/bin/perl
checking for makeinfo... makeinfo
checking makeinfo version... 4.13
checking for texi2html... texi2html
checking texi2html version... 1.82
checking for dblatex... no
checking for pdflatex... pdflatex
checking for pngtopnm... no
checking for convert... no
checking for zip... zip
checking for rsync... rsync
configure: creating ./config.status
config.status: creating config.make
config.status: creating config.hh
configure: WARNING: unrecognized options: --disable-checking
WARNING: Please consider installing optional programs: dblatex pngtopnm convert
See INSTALL.txt for more information on how to build LilyPond
Type:
make all to build LilyPond
make install to install LilyPond
make help to see all possible targets
Edit local.make for local Makefile overrides.
--snip--
Then off they go and start to compile. With an unrecognized option and
missing packages. I am not sure they in and of themselves will cause a
SIG11 but I know as sure as eggs is eggs you need dblatex for the doc
It fails on
--snip--
"/build/buildd/lilypond-2.14.2/out/lybook-testdb/snippet-names-1388814376796008757.ly"
Child returned 1
lilypond-book.py (GNU LilyPond) 2.14.2
make[3]: *** [out-test/collated-files.texi] Error 1
rm out-test/weblinks.itexi
make[3]: Leaving directory `/build/buildd/lilypond-2.14.2/input/regression'
make[2]: *** [local-test] Error 2
make[2]: Leaving directory `/build/buildd/lilypond-2.14.2/input/regression'
make[1]: *** [test] Error 2
make[1]: Leaving directory `/build/buildd/lilypond-2.14.2'
make: *** [build-stamp] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
--snip--
So without the snippet log I cannot really tell, but it doesn't look
that clean to start with. Maybe someone else can care comment?
James
- Re: LSR is not at the stable release level, (continued)
- Re: LSR is not at the stable release level, Thomas Morley, 2012/10/03
- Re: LSR is not at the stable release level, Eluze, 2012/10/03
- Re: LSR is not at the stable release level, Eluze, 2012/10/03
- Re: LSR is not at the stable release level, Thomas Morley, 2012/10/03
- Re: LSR is not at the stable release level, James, 2012/10/04
- Re: LSR is not at the stable release level, Eluze, 2012/10/04
- Re: LSR is not at the stable release level, Thomas Morley, 2012/10/04
- Re: LSR is not at the stable release level, Thomas Morley, 2012/10/04
Re: LSR is not at the stable release level, Joseph Rushton Wakeling, 2012/10/02
Re: LSR is not at the stable release level, Joseph Rushton Wakeling, 2012/10/02
- Re: LSR is not at the stable release level,
James <=
- Re: LSR is not at the stable release level, Joseph Rushton Wakeling, 2012/10/02
- Re: LSR is not at the stable release level, James, 2012/10/02
- Re: LSR is not at the stable release level, Joseph Rushton Wakeling, 2012/10/02
- Re: LSR is not at the stable release level, James, 2012/10/02
- Re: LSR is not at the stable release level, Joseph Rushton Wakeling, 2012/10/02