Source: lilypond Version: 2.20.0-1 Severity: serious Justification: FTBFS Dear Maintainer,
When trying to rebuild lilypond (before investigating whether the build could be ported to Python 3), I found that the package currently FTBFS. Appropriate section of the log file is as follows: cat alist.doc arbiters.doc async.doc backtrace.doc boolean.doc chars.doc continuations.doc debug.doc deprecation.doc deprecated.doc discouraged.doc dynl.doc dynwind.doc environments.doc eq.doc error.doc eval.doc evalext.doc extensions.doc feature.doc fluids.doc fports.doc futures.doc gc.doc goops.doc gsubr.doc gc-mark.doc gc-segment.doc gc-malloc.doc gc-card.doc guardians.doc hash.doc hashtab.doc hooks.doc i18n.doc init.doc ioext.doc keywords.doc lang.doc list.doc load.doc macros.doc mallocs.doc modules.doc numbers.doc objects.doc objprop.doc options.doc pairs.doc ports.doc print.doc procprop.doc procs.doc properties.doc random.doc rdelim.doc read.doc root.doc rw.doc scmsigs.doc script.doc simpos.doc smob.doc sort.doc srcprop.doc stackchk.doc stacks.doc stime.doc strings.doc srfi-4.doc srfi-13.doc srfi-14.doc strorder.doc strports.doc struct.doc symbols.doc threads.doc throw.doc values.doc variable.doc vectors.doc version.doc vports.doc weaks.doc ramap.doc unif.doc dynl.doc filesys.doc posix.doc net_db.doc socket.doc regex-posix.doc | GUILE="/build/lilypond-jv5Dao/lilypond-2.20.0/guile18/pre-inst-guile" ../scripts/snarf-check-and-output-texi > guile-procedures.texi || { rm guile-procedures.texi; false; } /bin/bash: line 1: 15186 Broken pipe cat alist.doc arbiters.doc async.doc backtrace.doc boolean.doc chars.doc continuations.doc debug.doc deprecation.doc deprecated.doc discouraged.doc dynl.doc dynwind.doc environments.doc eq.doc error.doc eval.doc evalext.doc extensions.doc feature.doc fluids.doc fports.doc futures.doc gc.doc goops.doc gsubr.doc gc-mark.doc gc-segment.doc gc-malloc.doc gc-card.doc guardians.doc hash.doc hashtab.doc hooks.doc i18n.doc init.doc ioext.doc keywords.doc lang.doc list.doc load.doc macros.doc mallocs.doc modules.doc numbers.doc objects.doc objprop.doc options.doc pairs.doc ports.doc print.doc procprop.doc procs.doc properties.doc random.doc rdelim.doc read.doc root.doc rw.doc scmsigs.doc script.doc simpos.doc smob.doc sort.doc srcprop.doc stackchk.doc stacks.doc stime.doc strings.doc srfi-4.doc srfi-13.doc srfi-14.doc strorder.doc strports.doc struct.doc symbols.doc threads.doc throw.doc values.doc variable.doc vectors.doc version.doc vports.doc weaks.doc ramap.doc unif.doc dynl.doc filesys.doc posix.doc net_db.doc socket.doc regex-posix.doc 15187 Segmentation fault | GUILE="/build/lilypond-jv5Dao/lilypond-2.20.0/guile18/pre-inst-guile" ../scripts/snarf-check-and-output-texi > guile-procedures.texi make[5]: *** [Makefile:2689: guile-procedures.texi] Error 1 make[5]: Leaving directory '/build/lilypond-jv5Dao/lilypond-2.20.0/guile18/libguile' make[4]: *** [Makefile:799: all] Error 2 make[4]: Leaving directory '/build/lilypond-jv5Dao/lilypond-2.20.0/guile18/libguile' make[3]: *** [Makefile:668: all-recursive] Error 1 make[3]: Leaving directory '/build/lilypond-jv5Dao/lilypond-2.20.0/guile18' make[2]: *** [Makefile:511: all] Error 2 make[2]: Leaving directory '/build/lilypond-jv5Dao/lilypond-2.20.0/guile18' make[1]: *** [debian/rules:102: override_dh_auto_configure] Error 2 make[1]: Leaving directory '/build/lilypond-jv5Dao/lilypond-2.20.0' make: *** [debian/rules:94: build] Error 2 guile segfaults as soon as it is started (with or without docs on stdin). The backtrace is as follows in case the problem jumps out. /build/lilypond-jv5Dao/lilypond-2.20.0/guile18/libguile/.libs$ LD_LIBRARY_PATH=. gdb ./guile Reading symbols from ./guile... (gdb) r Starting program: /build/lilypond-jv5Dao/lilypond-2.20.0/guile18/libguile/.libs/guile Program received signal SIGSEGV, Segmentation fault. scm_mark_locations (x=0x7fffffffe948, n=18446744073709551562) at gc-mark.c:435 435 SCM obj = * (SCM *) &x[m]; (gdb) bt #0 scm_mark_locations (x=0x7fffffffe948, n=18446744073709551562) at gc-mark.c:435 #1 0x00007ffff7f5edcd in scm_threads_mark_stacks () at threads.c:1408 #2 0x00007ffff7f178a8 in scm_mark_all () at gc-mark.c:82 #3 0x00007ffff7f171cb in scm_i_gc (what=what@entry=0x7ffff7f7a43f "cells") at gc.c:596 #4 0x00007ffff7f173a9 in scm_gc_for_newcell ( freelist=0x7ffff7fadd60 <scm_i_master_freelist2>, free_cells=0x555555559300) at gc.c:507 #5 0x00007ffff7f48e1c in scm_double_cell (cdr=140737348583488, ccr=7051895308, cbr=93824992284640, car=5) at ../libguile/inline.h:201 #6 scm_i_c_make_symbol (name=name@entry=0x7ffff7f7e3ff "caaadr", len=len@entry=6, flags=flags@entry=0, hash=hash@entry=7051895308, props=0x7ffff7ab4040) at strings.c:436 #7 0x00007ffff7f5d83a in scm_i_c_mem2symbol (name=name@entry=0x7ffff7f7e3ff "caaadr", len=6) at symbols.c:150 #8 0x00007ffff7f5dc45 in scm_from_locale_symbol (sym=sym@entry=0x7ffff7f7e3ff "caaadr") at symbols.c:388 #9 0x00007ffff7f3afac in scm_c_make_subr (name=0x7ffff7f7e3ff "caaadr", type=type@entry=93, fcn=<optimized out>) at procs.c:69 #10 0x00007ffff7f3b047 in scm_c_define_subr (name=<optimized out>, type=type@entry=93, fcn=<optimized out>) at procs.c:80 #11 0x00007ffff7f34da2 in scm_init_pairs () at pairs.c:197 #12 0x00007ffff7f25119 in scm_i_init_guile (base=base@entry=0x7fffffffe948) at init.c:485 #13 0x00007ffff7f5eb90 in scm_i_init_thread_for_guile (parent=0x0, base=0x7fffffffe948) at threads.c:590 #14 scm_i_init_thread_for_guile (base=0x7fffffffe948, parent=0x0) at threads.c:573 #15 0x00007ffff7f5ebfb in scm_i_with_guile_and_parent ( func=func@entry=0x7ffff7f24ea0 <invoke_main_func>, data=data@entry=0x7fffffffe970, parent=<optimized out>) at threads.c:732 #16 0x00007ffff7f5ec4c in scm_with_guile (func=func@entry=0x7ffff7f24ea0 <invoke_main_func>, data=data@entry=0x7fffffffe970) at threads.c:721 #17 0x00007ffff7f24fb5 in scm_boot_guile (argc=<optimized out>, argv=<optimized out>, main_func=<optimized out>, closure=<optimized out>) at init.c:350 #18 0x0000555555555072 in main (argc=<optimized out>, argv=<optimized out>) at guile.c:63 regards Stuart