[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Need help with guile 1.88 or using guile 2.2 with lilypond-2.20

From: Dave Plater
Subject: Need help with guile 1.88 or using guile 2.2 with lilypond-2.20
Date: Mon, 8 Jun 2020 10:24:04 +0200

Hi, I maintain Lilypond for openSUSE and also created guile1 for
lilypond using guile-1.8.8
I have a problem, guile-1.8.8 doesn't build with gcc 10:
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 |
../scripts/snarf-check-and-output-texi          >
guile-procedures.texi || { rm guile-procedures.texi; false; }

Causes a:
15388 Segmentation fault      |
../scripts/snarf-check-and-output-texi > guile-procedures.texi

This is beyond my capabilities, the above command resists gdb --args
so I'm unable to see where the segfault happens. Something in gcc10 is
exposing a problem in guile-1.8.8

My first thought is to update guile to 2.2 but lilypond's configure
complains. I've seen a lot of talk about using guile 2.2,
openSUSE:Factory is at guile-3.0.2 so 2.2 is quite old but I'm
hopefull that it will resist gcc10. Gcc9 is still available for use
but that will be patching a leaky boat. See:
for the full story and
I appreciate any help.
Dave Plater

reply via email to

[Prev in Thread] Current Thread [Next in Thread]