New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade LiDIA to v2.3.0+latte-patches-2019-05-01 #27746
Comments
comment:1
Also, mkoeppe/LiDIA#2 - can this be merged upstream? |
comment:3
What happened in this bug report is that CXX has been set to "g++ -std=gnu++11" (where g++ is the system's clang compiler). |
This comment has been minimized.
This comment has been minimized.
Changed upstream from Reported upstream. Developers acknowledge bug. to Fixed upstream, in a later stable release. |
New commits:
|
Commit: |
Author: Matthias Koeppe |
comment:7
OK, this also needs adjustement w.r.t. to #27212. (Somehow lidia went under the radar there). What is the correct way to configure it if GMP is installed in the standard location, Otherwise, sdh_configure --with-arithmetic=gmp \
--with-extra-includes="$SAGE_GMP_INCLUDE" \
--with-extra-libs="$SAGE_GMP_PREFIX/lib" \
--enable-shared=yes --enable-static=no ok, so an experiment tells me that |
comment:8
otherwise, I checked that things build with gcc 8.3 on linux and with clang 6.0.1 on freebsd. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Attachment: lidia-2.3.0+latte-patches-2014-10-04.p0.log |
Attachment: lidia-2.3.0+latte-patches-2019-05-01.log |
comment:10
in the setting where location of GMP headers and libs has to be specified in C(XX)FLAGS and in LDFLAGS, lidia's configure returns a false negative, as it ignores them for no good reason. So one needs --- /dev/null
+++ b/build/pkgs/lidia/patches/accept_gmp.patch
@@ -0,0 +1,13 @@
+diff --git a/configure b/configure
+index dd9b0ad..77a438a 100755
+--- a/configure
++++ b/configure
+@@ -18092,7 +18092,7 @@ EOF
+ test $ac_status = 0; }; } > /dev/null 2>&1; then
+ lidia_cv_gmp="yes"
+ else
+- lidia_cv_gmp="no"
++ lidia_cv_gmp="yes"
+ fi
+
+ fi to tell it to shut up and trust that Sage has it all sorted already. |
comment:11
The correct fix, of course, would be in lidia's |
comment:12
Of course, but I saw way too many semi-broken homegrown m4 macros to recognise GMP lately to be bothered about it. The only harm of this patch is that, potentially, if something goes horribly wrong, you get a linker error... |
comment:13
@sophiasage, have you pulled the branch of this ticket? |
comment:14
Dima, could you test branch |
comment:15
running
Is it normal? |
comment:16
OK, https://github.com/mkoeppe/LiDIA/tree/config_flags works for me in instead of the patch in comment:10. By the way, not only with clang 6, but with clang 7 too. |
comment:17
Thanks for testing! |
comment:18
once you made a new tarball, and provided a link to it, please feel free to set this to positive review. |
Reviewer: Dima Pasechnik |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
comment:21
Replying to @dimpase:
I see these warnings too, but I decided not to address them at this time. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Changed branch from u/mkoeppe/upgrade_lidia_to_v2_3_0_latte_patches_2019_05_01 to |
This upgrade fixes compile errors on Mac with clang 6.0.1 as reported here:
https://groups.google.com/d/msg/sage-devel/UtdbqZy-1VE/Jlxfj3FxDAAJ
as well as clang 7.
Upstream issues:
mkoeppe/LiDIA#1
Package:
Upstream: Fixed upstream, in a later stable release.
CC: @dimpase @jplab @sophiasage
Component: packages: experimental
Author: Matthias Koeppe
Branch/Commit:
ba3e3e3
Reviewer: Dima Pasechnik
Issue created by migration from https://trac.sagemath.org/ticket/27746
The text was updated successfully, but these errors were encountered: