unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Douglas Mencken <dougmencken@gmail.com>
To: bug-guile@gnu.org
Subject: build errors: 9172 Broken pipe and 9173 Segmentation fault
Date: Thu, 24 Mar 2011 02:05:06 +0100	[thread overview]
Message-ID: <AANLkTimFpR=ti0UihqCk3ZCch+9O-mLiY87nECKqxZ6W@mail.gmail.com> (raw)

I don't have any idea how to fix that (I even tried to remove all
offline docs generating stuff with no success).
Guile version: guile-v2.0.0-122-gad301b6 (from git stable-2.0 branch).

  SNARF  net_db.doc
  SNARF  socket.doc
  SNARF  regex-posix.doc
  GEN      guile-procedures.texi
/bin/bash: line 1:  9172 Broken pipe             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 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 filesys.doc posix.doc net_db.doc
socket.doc regex-posix.doc
      9173 Segmentation fault      | GUILE_AUTO_COMPILE=0
../meta/uninstalled-env guile-tools snarf-check-and-output-texi >
guile-procedures.texi
make[3]: *** [guile-procedures.texi] Error 1
make[3]: Leaving directory
`/root/build-farm/guile-v2.0.0-122-gad301b6.builddir/libguile'
make[2]: *** [all] Error 2
make[2]: Leaving directory
`/root/build-farm/guile-v2.0.0-122-gad301b6.builddir/libguile'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/root/build-farm/guile-v2.0.0-122-gad301b6.builddir'
make: *** [all] Error 2



             reply	other threads:[~2011-03-24  1:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-24  1:05 Douglas Mencken [this message]
2011-03-24  1:45 ` build errors: 9172 Broken pipe and 9173 Segmentation fault Neil Jerram
     [not found]   ` <AANLkTindvcPaJ4qYr7OCvWbitFCzb2oALNO1ya6x0_Y4@mail.gmail.com>
2011-03-29 17:07     ` Douglas Mencken
2011-04-01  9:08       ` Andy Wingo
2011-04-16 11:19         ` Douglas Mencken
2011-04-16 16:01           ` Andy Wingo
2011-04-17  2:34           ` Mark H Weaver
2011-04-18 21:16             ` Ludovic Courtès
2011-04-18 23:45               ` Mark H Weaver
2011-04-21 10:28                 ` Andy Wingo
2011-04-17  2:38           ` Mark H Weaver

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='AANLkTimFpR=ti0UihqCk3ZCch+9O-mLiY87nECKqxZ6W@mail.gmail.com' \
    --to=dougmencken@gmail.com \
    --cc=bug-guile@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).