From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: guile-user@gnu.org
Subject: Re: ttn-pers-scheme & ttn-do
Date: Wed, 19 Mar 2008 08:35:00 +0100 [thread overview]
Message-ID: <874pb3majf.fsf@ambire.localdomain> (raw)
In-Reply-To: 87iqzj4we8.fsf@moley.moleskin.org
() Sebastian Tennant <sebyte@smolny.plus.com>
() Tue, 18 Mar 2008 22:20:15 +0200
checking if (guile-user) exports `close-all-fdes-except'... no
configure: error: module (guile-user) does not export
close-all-fdes-except; required
Something to do with dynamic linking and/or compiled code? I know
that much from the reference manual, although 'guile-user' isn't in
the index (perhaps it should be)....
That func is available in Guile 1.4.x, an amicable fork of Guile:
http://www.gnuvola.org/software/guile/
I will amend that page's README blurb in the next week or so to include
my hopes about a merging of selected Guile 1.4.x features into Guile
latest. Perhaps `close-all-fdes-except' will be one of those features,
but i doubt it...
http://www.gnuvola.org/software/ttn-do/ttn-do.html.gz
is 'not found on this server'.
Perhaps a transient error (NFS, blech). Please try again.
Happily swotting up on some ttn-pers-scheme-0.50 source code in the
mean time :-)
That stuff is retired; frankly, i rolled the 0.50 release so that i
could do "make install uninstall" w/ it. In info node "Future", there
are pointers to better-maintained (if not better-written, heh) code.
(Gist: ttn-do is where the churn is, now.)
thi
next prev parent reply other threads:[~2008-03-19 7:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-18 20:20 ttn-pers-scheme & ttn-do Sebastian Tennant
2008-03-19 7:35 ` Thien-Thi Nguyen [this message]
2008-03-19 11:08 ` Sebastian Tennant
2008-04-03 11:28 ` Thien-Thi Nguyen
2008-04-03 11:47 ` Thien-Thi Nguyen
2008-04-12 16:36 ` Sebastian Tennant
2008-05-25 18:12 ` Thien-Thi Nguyen
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=874pb3majf.fsf@ambire.localdomain \
--to=ttn@gnuvola.org \
--cc=guile-user@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).