ni...@lysator.liu.se (Niels Möller) writes:
Should make it easier to reach the goal of being able to build gcc using
mini-gmp for its modest bignum needs.
This makes a lot of sense from the perspective of GCC. It might hurt
GMP in an awkward way because GCC developers will no longer tend t
Dear Niels,
> Nice, thanks for the update.
>
> I'd still recommend to have mini-gmp.[ch] bundled with mpfr and let the
> configure flag --enable-mini-gmp set everything up to use it, but that's
> your call, of course.
>
> Should make it easier to reach the goal of being able to build gcc
paul zimmermann writes:
> as far as I remember, it worked at the end. See the doc/mini-gmp file in the
> MPFR svn repo (reproduced below). This was with GMP 6.0.0. I did not test it
> with more recent GMP snapshot. Maybe some changes in mini-gmp.c and mini-gmp.h
> are no longer necessary. Cf MPFR
Dear Niels,
> From: ni...@lysator.liu.se (Niels Möller)
> Date: Mon, 15 Jun 2015 09:57:39 +0200
>
> Zimmermann Paul writes:
>
> > I tried to compile MPFR with mini-gmp. I needed to do a few changes:
>
> Replying to an old mail. How did this work out? How do you deal with gmp
> vs mini-g
Zimmermann Paul writes:
> I tried to compile MPFR with mini-gmp. I needed to do a few changes:
Replying to an old mail. How did this work out? How do you deal with gmp
vs mini-gmp in public mpfr header files and the mpfr ABI?
Regards,
/Niels
--
Niels Möller. PGP-encrypted email is preferred.
