GNU bug report logs - #11564
"Broken pipe" when compiling from git

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 11564 in the body.
You can then email your comments to 11564 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Mark Skilbeck <m <at> iammark.us>
To: bug-guile <at> gnu.org
Subject: "Broken pipe" when compiling from git
Date: Sat, 26 May 2012 22:04:10 +0100

Hi, all. I've encountered an issue when compiling from the git
repo. The relevant output from make follows:

SNARF  socket.doc
  SNARF  regex-posix.doc
  GEN    guile-procedures.texi
/bin/bash: line 1: 26)22 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 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-6).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 weak-set.doc weak-table.doc weak-vector.doc dynl.doc
posix.doc net_db.doc socket.doc regex-posix.doc
26)23 Segmentation fault      | GUILE_AUTO_COMPILE=0 
../meta/uninstalled-env guild snarf-check-and-output-texi > guile-procedures.texi

     26)23 Segmentation fault      | GUILE_AUTO_COMPILE=)
     ../meta/uninstalled-env guild snarf-check-and-output-texi > guile-procedures.texi
make[3]: *** [guile-procedures.texi] Error 1

Can anybody shed some light on this?

Cheers.

P.S. Please include my email in the reply addresses as I'm not
subscribed to the list.

-- 
- mgsk.

if all you young men / were fish in the water 
how many young girls / would undress and dive after

Message #10 received at 11564-done <at> debbugs.gnu.org (full text, mbox):

From: Mark H Weaver <mhw <at> netris.org>
To: 11564-done <at> debbugs.gnu.org
Subject: Re: bug#11564: "Broken pipe" when compiling from git
Date: Mon, 28 May 2012 00:18:59 -0400

Mark Skilbeck <m <at> iammark.us> writes:
> Hi, all. I've encountered an issue when compiling from the git
> repo. The relevant output from make follows:
[Guile crashed on its first execution while trying to build docs]

I've spoken with Mark on irc and determined that this was due to
building stable-2.0 within a working directory that had previously built
master and not been cleaned properly before rebuilding.  He has now
built stable-2.0 successfully, so I'm closing this bug.

     Mark

Message #13 received at 11564 <at> debbugs.gnu.org (full text, mbox):

From: Mark H Weaver <mhw <at> netris.org>
To: Thien-Thi Nguyen <ttn <at> gnuvola.org>
Cc: 11564 <at> debbugs.gnu.org
Subject: Re: bug#11564: "Broken pipe" when compiling from git
Date: Mon, 28 May 2012 09:42:45 -0400

Thien-Thi Nguyen <ttn <at> gnuvola.org> writes:
>    [crash] was due to building stable-2.0 within a working
>    directory that had previously built master and not been cleaned
>    properly before rebuilding.
>
> What does "cleaned properly" mean?

All I know is that he built and installed the master branch, and then
checked out the stable-2.0 branch and rebuilt, and this later build
created a Guile that crashed.  He doesn't remember what cleaning (if
any) he did between those two builds.  However, when he later did a "git
clean -dxf" and rebuilt, that fixed the problem.

> Can that be codified in the
> makefiles?  Even better would be to codify the actions required
> for rebuilding that altogether avoid having to clean at all.

I agree that this would be ideal.  If someone wants to work on this, I'd
suggest following the steps I outlined above, and trying to reproduce
the problem.

     Best,
      Mark

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.