From: Ralf Mattes <rm@seid-online.de>
To: Matthew Keeter <matt.j.keeter@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: Solid modeling in Guile
Date: Sun, 21 Aug 2016 14:00:06 +0200 [thread overview]
Message-ID: <20160821120006.mke6f2d3ejvjp53n@seid-online.de> (raw)
In-Reply-To: <D17D9C55-F63D-4AC0-8BA8-B5E9BB48D53F@gmail.com>
One other thing,
your script (ao-guile) starts with a hash-bang "/usr/bin/env guile".
At least on Debian that might not work since guile might well be a link
to guile-1.8
Maybe you need to make the guile binary a configuration option?
Cheers, RalfD
prev parent reply other threads:[~2016-08-21 12:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-18 21:44 Solid modeling in Guile Matthew Keeter
2016-08-19 1:26 ` dsmich
2016-08-19 7:37 ` Mark H Weaver
2016-09-22 17:40 ` Mark H Weaver
2016-09-22 17:42 ` Matthew Keeter
2016-08-19 9:29 ` Alex Kost
2016-08-25 16:08 ` Thien-Thi Nguyen
2016-08-19 17:05 ` Thompson, David
2016-08-20 13:23 ` Ralf Mattes
2016-08-20 14:26 ` Matthew Keeter
2016-08-21 11:54 ` Ralf Mattes
2016-08-21 12:00 ` Ralf Mattes [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=20160821120006.mke6f2d3ejvjp53n@seid-online.de \
--to=rm@seid-online.de \
--cc=guile-user@gnu.org \
--cc=matt.j.keeter@gmail.com \
/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).