From: Brian Small <bsmall2@posteo.net>
To: 34437@debbugs.gnu.org
Subject: bug#34437: Guile 2.2.4 Installation Experience
Date: Tue, 12 Feb 2019 00:03:24 +0900 [thread overview]
Message-ID: <39dda32f8c3e6249b9d06355d67e7485@posteo.net> (raw)
Hello,
Guile and its manual have been teaching me a lot. Thank you.
> Any problems with the installation should be reported to
> bug-guile@gnu.org.
I wrote up some of the details that gave me trouble while installing
guile (GNU Guile) 2.2.4. (fn:1)
For Debian 9 Guile 2.2 seems to require an installation of Guile 2.0
for shared libraries.
Maybe most people that use Guile are developers and already have
-devel packages installed:
> When the messages said I needed libtdl or libunistring, I really needed
> libtdl-dev and libunistring-dev.
For Debian:
> The installation process mentioned the need for bdw-gc. A search(
> showed me that Debian's libgc-dev package would work so a quick #
> apt-get install libgc-dev let me avoid longer download, configure and
> make process.
> The need for libffi was, like libtdl and libunistring, met by Debian's
> -dev package # apt-get install libffi-dev.
I hope this mail will help and not just distract. Eventually I'd like
to use Guile Scheme for basic programming education. The smoother the
installation process goes for non-developers, the more likely it is that
the Guile Scheme notation will be good for general education, the way
Lancelot Hogben in _Mathematics for the Millions_ about the importance
of notation.
Take it easy,
Brian Small
- (fn:1) https://write.as/bs2gs/installing-guile-2-2-4-on-two-computers
-----------------
Brian Small
On-line Writings:
https://ruhrspora.de/u/bsmall2
https://wordsmith.social/bsmall2/
https://write.as/bsmall2/
On-line Photos:
https://pixelfed.social/bsmall2
https://snap.as/bsmall2
https://goblinrefuge.com/mediagoblin/u/bsmall2/
reply other threads:[~2019-02-11 15:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=39dda32f8c3e6249b9d06355d67e7485@posteo.net \
--to=bsmall2@posteo.net \
--cc=34437@debbugs.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).