t...@gmplib.org (Torbjörn Granlund) writes:
--- a/Makefile.am Wed Nov 16 23:07:02 2016 +0100
+++ b/Makefile.am Thu Nov 17 07:12:08 2016 +0100
@@ -433,7 +433,7 @@ check-mini-gmp:
MINI_GMP_DIR="$$abs_srcdir/mini-gmp" \
LDFLAGS="-L../../.libs" \
LIBS="-lgmp -lm" \
- CC="$(CC_FOR_BUILD)" EXTRA_CFLAGS="-g -I../.." check
+ CC="$(CC)" EXTRA_CFLAGS="$(CFLAGS) -g -I../.." check
I will put this in now. (I'd like to move back to getting some dev work
done. That needs a cleaner test reporting state.)
I made that and another change to now get the test to run on the
majority of our systems. The other change was this one:
https://gmplib.org/repo/gmp/rev/88fead579828
This makes sure linking knows the ABI. I am not sure there are no
side-effects conflicting with the author's intended Makefile behaviour.
With these changes, it was feasible to mark the remaining mini-gmp
falures as "expected" to get a manageable report page again. (I also
marked the PIC/static issue with which I am supposed to work as
expected; that issue now affects a handful machines as more machines
have been upgraded to newer Debian stretch versions.)
Another problem with the Makefile.am check-mini-gmp code has surfaced.
It overrides LD_LIBRARY_PATH (and DYLD_LIBRARY_PATH) for the entire
mini-gmp build. That includes gcc, which as you know is linked to GMP.
The result is compilation problems on at least one platform.
The authors need to make sure only the test binary execution get a
modified LD_LIBRARY_PATH.
There is also a problem with t-signed on ppc64 machines.
I updated https://gmplib.org/devel/mini-gmp-status.html; please keep it
up-to-date with your changes.
--
Torbjörn
Please encrypt, key id 0xC8601622
_______________________________________________
gmp-devel mailing list
gmp-devel@gmplib.org
https://gmplib.org/mailman/listinfo/gmp-devel
