From: "Stewart, Adam James" <ajstewart@anl.gov>
To: 23911@debbugs.gnu.org
Subject: bug#23911: Cat broken pipe segmentation fault when building Guile
Date: Thu, 7 Jul 2016 16:03:28 +0000 [thread overview]
Message-ID: <9F5501637440B04B9DE4C86279C60B6E4A571E30@PAYTON.anl.gov> (raw)
[-- Attachment #1: Type: text/plain, Size: 2211 bytes --]
Hello,
I'm trying to install Guile 2.0.11 but I'm running into problems. Make crashes with this error message:
cat: write error: Broken pipe
/bin/sh: line 1: 53341 Done(1) cat alist.doc arbiters.doc array-handle.doc array-map.doc arrays.doc async.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 expand.doc extensions.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 root.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 threads.doc throw.doc trees.doc uniform.doc values.doc variable.doc vectors.doc version.doc vports.doc weaks.doc dynl.doc posix.doc net_db.doc socket.doc regex-posix.doc
53342 Segmentation fault (core dumped) | GUILE_INSTALL_LOCALE=1 GUILE_AUTO_COMPILE=0 ../meta/uninstalled-env guild snarf-check-and-output-texi > guile-procedures.texi
make[3]: *** [guile-procedures.texi] Error 1
make[3]: Leaving directory `/scratch/ajstewart/spack-stage/spack-stage-7gx45p/guile-2.0.11/libguile'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/scratch/ajstewart/spack-stage/spack-stage-7gx45p/guile-2.0.11/libguile'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/scratch/ajstewart/spack-stage/spack-stage-7gx45p/guile-2.0.11'
make: *** [all] Error 2
Let me know if you would like the rest of my build output or the config.log.
Adam J. Stewart
Assistant Systems Administrator
Laboratory Computing Resource Center
Computing, Environment and Life Sciences
Argonne National Laboratory
[-- Attachment #2: Type: text/html, Size: 3093 bytes --]
next reply other threads:[~2016-07-07 16:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 16:03 Stewart, Adam James [this message]
2016-07-10 12:42 ` bug#23911: Cat broken pipe segmentation fault when building Guile Andy Wingo
[not found] ` <9F5501637440B04B9DE4C86279C60B6E4A574FC1@PAYTON.anl.gov>
2016-07-11 15:55 ` Andy Wingo
[not found] ` <9F5501637440B04B9DE4C86279C60B6E4A575001@PAYTON.anl.gov>
2016-07-11 19:35 ` Andy Wingo
2016-07-13 17:00 ` Stewart, Adam James
2016-07-13 20:45 ` Stewart, Adam James
2016-07-14 10:11 ` Andy Wingo
2017-03-01 8:12 ` Andy Wingo
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=9F5501637440B04B9DE4C86279C60B6E4A571E30@PAYTON.anl.gov \
--to=ajstewart@anl.gov \
--cc=23911@debbugs.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).