Dave Plater <[email protected]> writes: > 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 | > GUILE="/home/abuild/rpmbuild/BUILD/guile-1.8.8/pre-inst-guile" > ../scripts/snarf-check-and-output-texi > > guile-procedures.texi || { rm guile-procedures.texi; false; } > > Causes a: > 15388 Segmentation fault |
Last time I checked, a successful Guile-1.8 build needed to use the branch_release-1-8 branch from the Guile repository (which has a few commits on top). However, I don't know whether this will already help with your GCC 10 problem: I don't remember anything related to that. If it doesn't, you might want to ask Thien-Thi Nguyen (who has made this branch tip work so far) to take a look. -- David Kastrup
