From: Andy Wingo <wingo@pobox.com>
To: rm@seid-online.de
Cc: guile-user@gnu.org
Subject: Re: Build failure during build from git
Date: Thu, 01 Jul 2010 20:14:29 +0100 [thread overview]
Message-ID: <m3fx03ui96.fsf@unquote.localdomain> (raw)
In-Reply-To: <1277978870.7109.4.camel@mhflaptop01> (Ralf Mattes's message of "Thu, 01 Jul 2010 12:07:50 +0200")
On Thu 01 Jul 2010 11:07, Ralf Mattes <rm@seid-online.de> writes:
> after a fresh checkout from the git repository the build fails with the
> following error message:
>
> make[3]: Entering directory `/SCHEME/guile/libguile'
> cat alist.doc arbiters.doc array-handle.doc array-map.doc .... > guile-procedures.texi || { rm guile-procedures.texi; false; }
>
> guile: uncaught throw to misc-error: (dynamic-link file: ~S, message: ~S (libguile-srfi-srfi-1-v-4 file not found) #f)
> Cannot exit gracefully when init is in progress; aborting.
We are seeing this issue now, yes. A fix should come shortly. In the
meantime, `make -k', then `make' should work.
Andy
--
http://wingolog.org/
prev parent reply other threads:[~2010-07-01 19:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-01 10:07 Build failure during build from git Ralf Mattes
2010-07-01 19:14 ` Andy Wingo [this message]
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=m3fx03ui96.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=guile-user@gnu.org \
--cc=rm@seid-online.de \
/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).