On Sun, 30 Jul 2023, FX Coudert wrote:
Attached is a diff that fixes most of the warnings. It does three things:
- raise autoconf requirement to 2.69 (released in 2012, and what you already
use currently for production of the tarballs)
- replaces AC_FD_CC with AS_MESSAGE_LOG_FD, its new name
FX Coudert writes:
PS: second patchlet, to deal with these two macros:
> warning: The macro `AC_HEADER_STDC' is obsolete.
> warning: The macro `AC_HEADER_TIME' is obsolete.
If you, Marc, can take a look at those proposed changes, I think they
should be applied to the head gmp repo, not
FX Coudert writes:
One other question: our Linux builder, which is running from Github Actions,
fails to download from gmplib.org
I thought only the mercurial repo was firewalled, is that not the case?
Github is firewalled off in its entirety. The firewall cannot inspect
packets to make
PS: second patchlet, to deal with these two macros:
> warning: The macro `AC_HEADER_STDC' is obsolete.
> warning: The macro `AC_HEADER_TIME' is obsolete.
time.diff
Description: Binary data
___
gmp-bugs mailing list
gmp-bugs@gmplib.org
> First, a large number of warnings can be a bit scary.
Attached is a diff that fixes most of the warnings. It does three things:
- raise autoconf requirement to 2.69 (released in 2012, and what you already
use currently for production of the tarballs)
- replaces AC_FD_CC with
On Sun, 30 Jul 2023, FX Coudert wrote:
Sorry about that. I knew there were problems with old autotools and quickly
tried updating them before the release, but that caused too many problems.
What are the problems? Our workaround is to rerun the latest autoreconf, and it
emits a lot of
Hi Marc,
> Sorry about that. I knew there were problems with old autotools and quickly
> tried updating them before the release, but that caused too many problems.
What are the problems? Our workaround is to rerun the latest autoreconf, and it
emits a lot of warnings, but it does not create
On Sun, 30 Jul 2023, FX Coudert wrote:
Compilation of newly released GMP 6.3.0 on macOS (both Intel and ARM) leads to
wrongly compiled libraries, with a flat namespace. This is generally avoided
(and enforced by various build tools) on macOS since many OS versions, because
it can cause
Hi,
Compilation of newly released GMP 6.3.0 on macOS (both Intel and ARM) leads to
wrongly compiled libraries, with a flat namespace. This is generally avoided
(and enforced by various build tools) on macOS since many OS versions, because
it can cause linker errors due to name collisions.
The
赵世忠 writes:
The last digit should be '8', but mpf_get_str outputs '7'.
"Should be"?
Please read the GMP documentation, and if you still think there is a
bug, please write a bug report where you motivate what you think is not
right with GMP's current behaviour.
--
Torbjörn
Please encrypt,
mpf_t x;
mpf_init2(x,3000);
mpf_set_str(x,"0.6931471805599453094172321214581765680755001343602552541206800094933936219696947156058633269964186875",10);
char str[300];
mp_exp_t myexp;
mpf_get_str(str, , 10, 99, x);
mpf_clear(x);
printf("%s\n",str);
The last digit should be '8', but mpf_get_str
11 matches
Mail list logo
