unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
To: Noah Lavine <noah.b.lavine@gmail.com>
Cc: bug-guile@gnu.org
Subject: Re: Build Error in Latest Git Sources
Date: Sun, 13 Jun 2010 13:07:09 +0100	[thread overview]
Message-ID: <87wru3t9ua.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <AANLkTinnDKFsRqxksObeVVPlbL1AV_HVK5h8xIVbnP6E@mail.gmail.com> (Noah Lavine's message of "Sat, 12 Jun 2010 22:10:34 -0400")

Noah Lavine <noah.b.lavine@gmail.com> writes:

> /bin/sh: line 1: 82299 Broken pipe             cat alist.doc
>
> I'm unsure what would cause this, but I'm happy to help track it down if I can.

I saw a problem which I think was like this, but it did not recur after
doing a make -k distclean and then building again from scratch
(i.e. ./autogen.sh; ./configure; make).  Does it recur for you even if
you rebuild in that way?



  reply	other threads:[~2010-06-13 12:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-13  2:10 Build Error in Latest Git Sources Noah Lavine
2010-06-13 12:07 ` Neil Jerram [this message]
2010-06-13 14:08   ` Noah Lavine

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=87wru3t9ua.fsf@ossau.uklinux.net \
    --to=neil@ossau.uklinux.net \
    --cc=bug-guile@gnu.org \
    --cc=noah.b.lavine@gmail.com \
    /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).