unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: nisse@lysator.liu.se (Niels Möller)
To: Andy Wingo <wingo@pobox.com>
Cc: 10519@debbugs.gnu.org, "Ludovic Courtès" <ludo@gnu.org>,
	"Torbjorn Granlund" <tg@gmplib.org>
Subject: bug#10519: guile and (mini-)gmp
Date: Sat, 02 Mar 2013 22:45:14 +0100	[thread overview]
Message-ID: <nnhaktlbmd.fsf@stalhein.lysator.liu.se> (raw)
In-Reply-To: <87txotbmag.fsf@pobox.com> (Andy Wingo's message of "Sat, 02 Mar 2013 21:04:55 +0100")

Andy Wingo <wingo@pobox.com> writes:

>  1. What is the status of mini-gmp?  I understand that you use it in GMP
>     itself, so hopefully mini-gmp is in a good state, upstream.

The version bundled with gmp-5.1.1 is fairly solid. The first release,
with gmp-5.1.0, had some severe bugs. Testsuite has been improved since.

>  2. Has anyone looked at getting mini-gmp into Gnulib?

No idea. But I think configuration should be straight-forward: Either
you use the "real gmp", or you use mini-gmp. And in the latter case, you
know exactly what you have, so there shouldn't be any additional system
dependencies.

I'd expect the difficult issues to be (i) handling of gmp vs mini-gmp in
public headers, API and ABI, and (ii) any features you need which aren't
supported in mini-gmp. I guess you should rarely want the "system guile"
to be linked with mini-gmp, but use mini-gmp only as an option when
guile is bundled with some application.

Regards,
/Niels

-- 
Niels Möller. PGP-encrypted email is preferred. Keyid C0B98E26.
Internet email is subject to wholesale government surveillance.





      parent reply	other threads:[~2013-03-02 21:45 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-15 21:22 bug#10519: guile and (mini-)gmp Niels Möller
2012-01-16 10:19 ` Mark H Weaver
2012-01-16 14:06   ` Niels Möller
2012-01-16 19:21     ` Mark H Weaver
2012-01-28  9:49   ` Niels Möller
2012-01-28 10:10     ` Mark H Weaver
2012-07-22  9:04   ` Ludovic Courtès
2012-02-03 13:40 ` Andy Wingo
2012-02-03 19:56   ` Niels Möller
2012-02-03 20:01     ` Torbjorn Granlund
2012-02-04 22:46       ` Ludovic Courtès
2012-07-22  9:00 ` Ludovic Courtès
2012-07-22 23:17   ` Niels Möller
2012-08-10 21:51     ` Ludovic Courtès
2012-08-11  9:37       ` Niels Möller
2012-08-11 19:46         ` Ludovic Courtès
2012-08-11 21:50           ` Niels Möller
2012-08-11 22:48             ` Ludovic Courtès
2013-03-02 20:04               ` Andy Wingo
2013-03-02 20:58                 ` Mark H Weaver
2013-03-05 19:09                   ` Mark H Weaver
2013-03-18  0:01                     ` Mark H Weaver
2013-03-18  9:19                       ` Ludovic Courtès
2013-03-26  8:17                       ` Niels Möller
2013-03-27 17:00                         ` Mark H Weaver
2016-10-27 12:29                       ` Niels Möller
2016-11-10 19:56                         ` Andy Wingo
2013-03-02 21:45                 ` Niels Möller [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=nnhaktlbmd.fsf@stalhein.lysator.liu.se \
    --to=nisse@lysator.liu.se \
    --cc=10519@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=tg@gmplib.org \
    --cc=wingo@pobox.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).