From: "Bryce L Nordgren" <bnordgren@gmail.com>
To: bug-guile@gnu.org
Subject: Re: Guile 1.8.2 / SLIB 3a4 incompatibility
Date: Thu, 20 Sep 2007 08:17:25 -0600 [thread overview]
Message-ID: <8b60e61a0709200717t34dce606qcae6c33650225874@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1016 bytes --]
Ludovic,
Thanks for the help. I edited ice-9/slib.scm as you specified, and now I'm
getting behavior which might be right and might not be: error on the first
try and success on the second:
# guile
guile> (use-modules (ice-9 slib))
ERROR: Unbound variable: system
ABORT: (unbound-variable)
guile> (use-modules (ice-9 slib))
guile>
Unfortunately, this is apparently not good enough for GnuCash, as the
following ./configure snippet fails:
if ${GUILE} -c "(use-modules (ice-9 slib)) (require 'printf)" > /dev/null
2>&1
then
{ echo "$as_me:$LINENO: result: yes"
>&5
echo "${ECHO_T}yes" >&6;
}
else
{ { echo "$as_me:$LINENO:
error:
Cannot find SLIB. Are you sure you have it
installed?
See http://bugzilla.gnome.org/show_bug.cgi?id=347922
"
>&5
Since the test in the configure script seems reasonable, and the
fail-first-time behavior was demonstrated on the command line, it would seem
appropriate to further pursue the solution here... Any ideas why the same
thing both succeeds and fails?
[-- Attachment #1.2: Type: text/html, Size: 4705 bytes --]
[-- Attachment #2: Type: text/plain, Size: 137 bytes --]
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile
next reply other threads:[~2007-09-20 14:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-20 14:17 Bryce L Nordgren [this message]
2007-10-02 3:37 ` Guile 1.8.2 / SLIB 3a4 incompatibility Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2007-09-18 14:23 Bryce L Nordgren
2007-09-19 20:13 ` Ludovic Courtès
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=8b60e61a0709200717t34dce606qcae6c33650225874@mail.gmail.com \
--to=bnordgren@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).