From: <flynn16@tutanota.com>
To: Guile User <guile-user@gnu.org>
Subject: cat segfaults when compiling Guile 3.0
Date: Sun, 19 Jan 2020 22:46:38 +0100 (CET) [thread overview]
Message-ID: <LyzlP74--3-2@tutanota.com> (raw)
In-Reply-To: <mailman.87.1579453221.27182.guile-user@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 341 bytes --]
Hello, Guile Users:
I was compiling Guile 3.0 on 64-bit Ubuntu 18.04. The configure script was run successfully. A problem occurred running the Makefile. In the process of generating `guile-procedures.texi`, I think `cat` crashed, causing a broken pipe error. The error log is attached below. Is there a workaround to this issue?
-- Flynn
[-- Attachment #2: errorlog.txt --]
[-- Type: text/plain, Size: 2242 bytes --]
SNARF posix.doc
SNARF net_db.doc
SNARF socket.doc
SNARF regex-posix.doc
GEN guile-procedures.texi
Pre-boot error; key: misc-error, args: ("primitive-load-path" "Unable to find file ~S in load path" ("ice-9/boot-9") #f)/bin/bash: line 1: 29053 Broken pipe cat alist.doc array-handle.doc array-map.doc arrays.doc async.doc atomic.doc backtrace.doc boolean.doc bitvectors.doc bytevectors.doc chars.doc control.doc continuations.doc debug.doc deprecated.doc deprecation.doc dynl.doc dynwind.doc eq.doc error.doc eval.doc evalext.doc exceptions.doc expand.doc extensions.doc fdes-finalizers.doc feature.doc filesys.doc fluids.doc foreign.doc fports.doc gc-malloc.doc gc.doc gettext.doc generalized-arrays.doc generalized-vectors.doc goops.doc gsubr.doc guardians.doc hash.doc hashtab.doc hooks.doc i18n.doc init.doc ioext.doc keywords.doc list.doc load.doc macros.doc mallocs.doc memoize.doc modules.doc numbers.doc objprop.doc options.doc pairs.doc ports.doc print.doc procprop.doc procs.doc promises.doc r6rs-ports.doc random.doc rdelim.doc read.doc rw.doc scmsigs.doc script.doc simpos.doc smob.doc sort.doc srcprop.doc srfi-1.doc srfi-4.doc srfi-13.doc srfi-14.doc srfi-60.doc stackchk.doc stacks.doc stime.doc strings.doc strorder.doc strports.doc struct.doc symbols.doc syntax.doc threads.doc throw.doc trees.doc unicode.doc uniform.doc values.doc variable.doc vectors.doc version.doc vports.doc weak-set.doc weak-table.doc weak-vector.doc dynl.doc posix.doc net_db.doc socket.doc regex-posix.doc
29054 Aborted (core dumped) | GUILE_AUTO_COMPILE=0 ../meta/build-env guild snarf-check-and-output-texi > guile-procedures.texi
Makefile:4311: recipe for target 'guile-procedures.texi' failed
make[3]: *** [guile-procedures.texi] Error 1
make[3]: Leaving directory '/home/user/Downloads/guile-3.0.0/libguile'
Makefile:2426: recipe for target 'all' failed
make[2]: *** [all] Error 2
make[2]: Leaving directory '/home/user/Downloads/guile-3.0.0/libguile'
Makefile:1849: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/user/Downloads/guile-3.0.0'
Makefile:1735: recipe for target 'all' failed
make: *** [all] Error 2
next parent reply other threads:[~2020-01-19 21:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.87.1579453221.27182.guile-user@gnu.org>
2020-01-19 21:46 ` flynn16 [this message]
2020-01-19 22:54 ` cat segfaults when compiling Guile 3.0 Matt Wette
2020-01-19 23:38 flynn16
2020-01-19 23:51 ` Matt Wette
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=LyzlP74--3-2@tutanota.com \
--to=flynn16@tutanota.com \
--cc=guile-user@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).