From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-user@gnu.org
Subject: Re: The Guile license and the use of LGPL libs (like GMP).
Date: Thu, 16 May 2002 18:17:07 -0500 [thread overview]
Message-ID: <874rh7n0ng.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <20020516164045.C24385@gas-o> ("Jeff Read"'s message of "Thu, 16 May 2002 16:40:45 -0400")
"Jeff Read" <bitwize@snet.net> writes:
> It would be something of a hassle, yes. My main use for Guile is as
> a scripting workhorse. Wherever I go, I'd like Guile to go with me
> (inasmuch as my movement is restricted to vaguely unixoid systems)
> with a minimum of fuss. Depending on another external lib
> complicates that. Guile depends on qthreads as it is, but that is
> essentially resolved by bundling qthreads with Guile. Which is why I
> mentioned bundling GMP.
OK, well we should keep that in mind, though as long as GMP supports
the target architecture, and we arrange guile to handle a
--with-gmp=/some/prefix argument, I'm not sure that keeping a copy of
GMP's source tree inside ours buys much over just making sure the GMP
tarfile is handy, and that we have good docs about any required
configure args, etc.
This is all presuming we were in a situation where you had to have
GMP, i.e we didn't take the route allowing --without-gmp, or similar.
--
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C 64AE 78FE E5FE F0CB A0AD
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-05-16 23:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-09 20:17 Project: a good floating point printer/reader Marius Vollmer
2002-05-13 21:01 ` Rob Browning
2002-05-15 18:30 ` Marius Vollmer
2002-05-16 15:35 ` The Guile license and the use of LGPL libs (like GMP) Rob Browning
2002-05-16 16:44 ` Greg Troxel
2002-05-16 17:01 ` Bruce Korb
2002-05-16 17:12 ` Rob Browning
2002-05-21 19:55 ` Carl R. Witty
2002-05-21 23:44 ` Rob Browning
2002-05-16 17:21 ` Jeff Read
2002-05-16 17:22 ` Rob Browning
2002-05-16 20:40 ` Jeff Read
2002-05-16 23:17 ` Rob Browning [this message]
2002-05-16 23:35 ` Jeff Read
2002-05-17 0:02 ` Rob Browning
2002-05-28 18:56 ` Marius Vollmer
2002-05-28 18:28 ` Marius Vollmer
2002-05-28 18:54 ` Bruce Korb
2002-05-28 19:23 ` Marius Vollmer
2002-05-28 19:39 ` Bruce Korb
2002-05-28 19:54 ` Marius Vollmer
2002-05-28 20:16 ` Bruce Korb
2002-06-01 16:01 ` Marius Vollmer
2002-05-28 19:02 ` Rob Browning
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=874rh7n0ng.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.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).