From: No Itisnt <theseaisinhere@gmail.com>
To: guile-devel <guile-devel@gnu.org>
Subject: Build problem & unrelated patch
Date: Thu, 3 Jun 2010 20:45:02 -0500 [thread overview]
Message-ID: <AANLkTinCnpxPcAi7ol86y6h58_7BWwqoo--qlNKdXvFu@mail.gmail.com> (raw)
Recently I get a build failure on libguile/guile-procedures.texi:
guile: uncaught throw to misc-error: (dynamic-link file: ~S, message:
~S (libguile-srfi-srfi-1-v-4 file not found) #f)
Which would appear to be because srfi/ is not yet built. Anyone get
the same problem? I'm not sure how to go about fixing it.
Here is a patch that uses AM_SILENT_RULES
(http://www.flameeyes.eu/autotools-mythbuster/automake/silent.html) to
pare down build output, and also adds some files to .gitignore. I
think it's a good idea.
next reply other threads:[~2010-06-04 1:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-04 1:45 No Itisnt [this message]
2010-06-04 4:37 ` Build problem & unrelated patch No Itisnt
2010-06-06 19:41 ` Andy Wingo
2010-06-06 21:37 ` No Itisnt
2010-06-08 21:27 ` Ludovic Courtès
2010-06-17 15:30 ` No Itisnt
2010-06-06 14:13 ` Ludovic Courtès
2010-06-06 20:42 ` Ludovic Courtès
2010-06-06 22:44 ` 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=AANLkTinCnpxPcAi7ol86y6h58_7BWwqoo--qlNKdXvFu@mail.gmail.com \
--to=theseaisinhere@gmail.com \
--cc=guile-devel@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).