#8664 closed enhancement (fixed)
Upgrade Sage's MPIR spkg to version 2.1.3
Reported by:  was  Owned by:  GeorgSWeber 

Priority:  major  Milestone:  sage4.8 
Component:  packages: standard  Keywords:  sd32, GMP ECM execstack Fedora 14 extension module library dependencies Darwin 11 MacOS X 10.7 Lion 
Cc:  was, leif, drkirkby, jdemeyer, wbhart, jpflori  Merged in:  sage4.8.alpha0 
Authors:  Mike Hansen, Leif Leonhardy  Reviewers:  Leif Leonhardy, Dmitrii Pasechnik 
Report Upstream:  N/A  Work issues:  
Branch:  Commit:  
Dependencies:  #5847, #9858, #11896  Stopgaps: 
Description (last modified by )
Hi, OK, after all this, the build finally completed. The only changes I made were: * Updated mpir to rc3 * patched ecm as explained here: http://lists.gforge.inria.fr/pipermail/ecmdiscuss/2009August/004070.html (Though this had to be slightly modified  just search for the same command, which moved.) I then ran the long Sage test suite, and some tests fail. http://sage.math.washington.edu/home/wstein/build/mpir2/sage4.3.5/testlong.log  The following tests failed: sage t long "devel/sage/doc/en/tutorial/tour_numtheory.rst" sage t long "devel/sage/doc/fr/tutorial/tour_numtheory.rst" sage t long "devel/sage/sage/modular/cusps.py" sage t long "devel/sage/sage/modular/modsym/boundary.py" sage t long "devel/sage/sage/modular/modsym/ambient.py" sage t long "devel/sage/sage/libs/pari/gen.pyx" sage t long "devel/sage/sage/rings/arith.py" sage t long "devel/sage/sage/rings/integer.pyx" sage t long "devel/sage/sage/rings/polynomial/multi_polynomial_ideal.py" sage t long "devel/sage/sage/tests/book_stein_ent.py" sage t long "devel/sage/sage/schemes/elliptic_curves/heegner.py" Total time for all tests: 7170.6 seconds  I looked and it appears that maybe all of these are the result of the XGCD behavior in MPIR changing again. Has it changed to be like GMP now? That would be convenient. william
New spkg: http://sage.math.washington.edu/home/leif/Sage/spkgs/mpir2.1.3.p4.spkg
md5sum: 197c652a6bdbf20c2e47be9176a8616e mpir2.1.3.p4.spkg
Apply trac_8664fix_extmod_deps_for_MPIR_genericallysagelibrebased_to_4.7.2.alpha2.patch to the Sage library (after installation of the spkgs and a rebuild of dependent packages).
See comment(s) below on how to "manually" install and test the new packages. (ECM has to be updated, too, package is at #5847.)
#9522 can be closed as invalid / duplicate once this ticket has been merged.
Attachments (7)
Change History (146)
comment:1 Changed 11 years ago by
 Summary changed from upgrade sage's mpir spkg to version 2.0.0 to upgrade sage's mpir spkg to version 2.0.1
comment:2 Changed 11 years ago by
 Summary changed from upgrade sage's mpir spkg to version 2.0.1 to upgrade sage's mpir spkg to version 2.1.1
comment:3 Changed 11 years ago by
 Summary changed from upgrade sage's mpir spkg to version 2.1.1 to Upgrade Sage's MPIR spkg to version 2.1.1
comment:4 Changed 11 years ago by
 Cc was added
 Status changed from new to needs_review
I've put an spkg at http://sage.math.washington.edu/home/mhansen/mpir2.1.1.spkg
Interestingly, I did not get any of the failures listed above.
comment:5 Changed 11 years ago by
 Component changed from build to packages
comment:6 Changed 11 years ago by
 Cc leif added
comment:7 Changed 11 years ago by
Hmmm, spkginstall
could be cleaned up further, e.g.
 Dave's comment has somehow been truncated(?) a while ago ("... if" what?)
s/`uname`/$UNAME/
 Especially for parallel builds, it's more convenient to begin every error message with
"Error"
(or at least the message should contain that word).  Simplify the "fat binary" section for Linux; it doesn't make sense to call
uname m
three times, nor does it to compare its result again if it already matched one of the tested. Acase
esac
would be appropriate, also merging the identicali386
andi686
thenbranches. Btw,uname m
can also bei486
ori586
on 32bit Linuces.  Is the
! [ $? eq 0 ]
some required Cygwin "idiom"?
Also, spkgcheck
doesn't print any messages, and uses make
instead of $MAKE
.
The dependencies ("None") in SPKG.txt
are wrong; MPIR at least depends on iconv, which Sage ships, though Sage's version is only used/built on some systems. I'm not sure if readline should be added to spkg/standard/deps
. (MPIR's configure
looks for much more, but apparently  as currently shipped  doesn't need/use all of that.) The Changelog could perhaps mention further changes, too.
If nobody else wants to, I could make the changes, i.e. a reviewer patch. Just let me know...
Going to test the new spkg with Sage 4.5.3.alpha2 and 4.6.prealpha3 (on Linuces only).
comment:8 Changed 11 years ago by
 Cc drkirkby added
Dave, as it seems you're addicted to testing, you could also test this new spkg (e.g. on Solaris, OpenSolaris)... ;)
comment:9 Changed 11 years ago by
I guess unless we bump the patch levels of all packages that depend on GMP/MPIR (and ECM), this package breaks upgrading Sage (at least with the current upgrade process), due to interface change (in conjunction with shared library versioning).
The same applies to testing this package (and/with ECM 6.3 from #5847); one has to either build from scratch or delete spkg/installed/<packagename>
for all packages that depend on those two.
Perhaps one could simply (conditionally) do the latter in spkg/install
, which also gets updated during upgrade.
comment:10 followup: ↓ 11 Changed 11 years ago by
Defining SAGE_SPKG
to sagespkg f
in spkg/standard/deps
should in principle also work, but doesn't... apparently because not really all shared libraries that use libgmpxx.so
get rebuilt, so some still refer to the old, deleted libgmpxx.so.3
.
Rebuilding Sage 4.5.3.alpha2 with MPIR 2.1.1 and ECM 6.3 from scratch worked on Ubuntu 10.04 x86_64 (parallel build with 32 jobs); ptestlong
passed all tests.
comment:11 in reply to: ↑ 10 ; followup: ↓ 12 Changed 11 years ago by
Replying to leif:
Defining
SAGE_SPKG
tosagespkg f
inspkg/standard/deps
should in principle also work, but doesn't... apparently because not really all shared libraries that uselibgmpxx.so
get rebuilt, so some still refer to the old, deletedlibgmpxx.so.3
.
I think this could be fixed by making extension modules also depend on (some of) the libraries they use (in module_list.py
), with the disadvantage that these modules would get rebuilt whenever their libraries "change", even if the interfaces stay the same (and even if just the modification time changed due to a rebuild/reinstallation).
Rebuilding Sage 4.5.3.alpha2 with MPIR 2.1.1 and ECM 6.3 from scratch worked on Ubuntu 10.04 x86_64 (parallel build with 32 jobs);
ptestlong
passed all tests.
Same for Fedora 13 x86 (parallel build with 6 jobs), also ptestlong
.
Unfortunately, there seems to be some incompatibility between the new PARI (2.4.3.svn12577.p4) or  more precisely  the required changes to Sage's interface to PARI in order to upgrade PARI (Sage 4.6.prealpha3, see #9343 and the NewPARI Wiki page) and MPIR 2.1.1:
On Ubuntu 10.04 x86_64 (Core2, gcc 4.4.3) exactly two of all doctests (ptestlong
) segfault (in sage/schemes/elliptic_curves/ell_point.py
).
On Fedora 13 x86 (Pentium 4 Prescott, gcc 4.4.4) the same two doctests and another one in ell_rational_field.py
segfault, and in addition one doctest in the latter file raises an unexpected exception (TypeError
), which seems to be the result of some other failure.
Maybe all are due to memory (or stack) corruption. See http://trac.sagemath.org/sage_trac/ticket/9343#comment:327 ff. for details; we haven't yet opened a separate ticket.
(For testing with Sage 4.6.prealpha3, I copied the MPIR 2.1.1 and ECM 6.3 spkgs to spkg/standard
, and built Sage from scratch  without problems. I also reinstalled the PARI, MPIR and ECM packages later with env SAGE_CHECK=yes ./sage f ...
; all test suites passed.)
comment:12 in reply to: ↑ 11 ; followup: ↓ 13 Changed 11 years ago by
Replying to leif:
Unfortunately, there seems to be some incompatibility between the new PARI (2.4.3.svn12577.p4 / Sage 4.6.prealpha3, see #9343 and the NewPARI Wiki page) and MPIR 2.1.1:
On Ubuntu 10.04 x86_64 (Core2, gcc 4.4.3) exactly two of all doctests (
ptestlong
) segfault (insage/schemes/elliptic_curves/ell_point.py
).
On Fedora 13 x86 (Pentium 4 Prescott, gcc 4.4.4) the same two doctests and another one in
ell_rational_field.py
segfault, and in addition one doctest in the latter file raises an unexpected exception (TypeError
), which seems to be the result of some other failure.
This is due to the new PARI using undocumented features of GMP (that MPIR doesn't support). and is now addressed at #9837.
comment:13 in reply to: ↑ 12 ; followup: ↓ 14 Changed 11 years ago by
Replying to leif:
This is due to the new PARI using undocumented features of GMP (that MPIR doesn't support). and is now addressed at #9837.
This is not necessarily the (only) cause. Jeroen has found a definite bug in MPIR 2.1.1 he'll report upstream; see #9837.
Leaving the ticket "needs review", though I don't think we should upgrade MPIR until that bug is fixed, in a later release.
comment:14 in reply to: ↑ 13 Changed 11 years ago by
Replying to leif:
Leaving the ticket "needs review", though I don't think we should upgrade MPIR until that bug is fixed, in a later release.
Sounds good to me.
comment:15 Changed 11 years ago by
The problem of ticket #9837 has been fixed in MPIR svn, it was purely a bug in MPIR 2.1.1.
comment:16 Changed 11 years ago by
 Status changed from needs_review to needs_work
Please upgrade to MPIR 2.1.2, where #9837 is fixed.
comment:17 Changed 11 years ago by
 Cc jdemeyer added
comment:18 followup: ↓ 19 Changed 11 years ago by
Apparently they've released MPIR 2.1.2 with just this bug fixed today.
Haven't tested that yet.
comment:19 in reply to: ↑ 18 Changed 11 years ago by
 Milestone changed from sage4.5.3 to sage4.6
Replying to leif:
Apparently they've released MPIR 2.1.2 with just this bug fixed today.
Haven't tested that yet.
At least passes all (long) tests in sage/schemes/elliptic_curves/
with Sage 4.6.prealpha3 on Fedora 13 x86 (Pentium 4 Prescott, gcc 4.4.4), where previously the segfaults occurred.
The diff shows they just fixed that single bug, bumped the MPIR version number (patch level) and incremented the revision numbers of both shared libraries. (In addition, they changed the date of the documentation without actually changing the docs themselves. The file src/.gdbinit
in the MPIR 2.1.1 spkg must have been added by Mike or someone else.)
comment:20 Changed 11 years ago by
 Summary changed from Upgrade Sage's MPIR spkg to version 2.1.1 to Upgrade Sage's MPIR spkg to version 2.1.2
comment:21 Changed 10 years ago by
FLINT also needs to be updated (from 1.5.0[.p5] to 1.5.2) to work with the new MPIR; otherwise the test suite won't build. See #9858.
comment:22 followups: ↓ 23 ↓ 24 ↓ 26 Changed 10 years ago by
Before the 4.6.alphaX build fails on the ia64 Skynet machines cleo and iras because of a bug in GCC 4.5.1 (see #9863), there's an apparent parallel make install
failure with MPIR:
[...] make[6]: Entering directory `/home/mpatel/build/cleo/sage4.6.alpha2/spkg/build/ mpir1.2.2.p1/src' make[6]: warning: jN forced in submake: disabling jobserver mode. (cd /home/mpatel/build/cleo/sage4.6.alpha2/local/include && rm f gmp.h && c p mpir.h gmp.h) /usr/bin/install c m 644 'mpir.h' '/home/mpatel/build/cleo/sage4.6.alpha2/lo cal/include/mpir.h' cp: cannot stat `mpir.h': No such file or directory make[6]: *** [installdatahook] Error 1 make[6]: Leaving directory `/home/mpatel/build/cleo/sage4.6.alpha2/spkg/build/mpir1.2.2.p1/src' make[5]: *** [installdataam] Error 2 make[5]: *** Waiting for unfinished jobs.... [...]
Has anyone else seen this? The full logs are here.
I noticed that MPIR 2.1.3 is out with a fix in mpf_get_d_2exp
. But I don't think Sage uses (m)any of the mpf_*
functions.
comment:23 in reply to: ↑ 22 Changed 10 years ago by
Replying to mpatel:
Before the 4.6.alphaX build fails on the ia64 Skynet machines cleo and iras because of a bug in GCC 4.5.1 (see #9863), there's an apparent parallel
make install
failure with MPIR:
I've also seen this on Skynet's menas.
comment:24 in reply to: ↑ 22 Changed 10 years ago by
Replying to mpatel:
Before the 4.6.alphaX build fails on the ia64 Skynet machines cleo and iras because of a bug in GCC 4.5.1 (see #9863), there's an apparent parallel
make install
failure with MPIR:
[...] make[6]: Entering directory `/home/mpatel/build/cleo/sage4.6.alpha2/spkg/build/ mpir1.2.2.p1/src' make[6]: warning: jN forced in submake: disabling jobserver mode. (cd /home/mpatel/build/cleo/sage4.6.alpha2/local/include && rm f gmp.h && cp mpir.h gmp.h) /usr/bin/install c m 644 'mpir.h' '/home/mpatel/build/cleo/sage4.6.alpha2/local/include/mpir.h' cp: cannot stat `mpir.h': No such file or directory make[6]: *** [installdatahook] Error 1 make[6]: Leaving directory `/home/mpatel/build/cleo/sage4.6.alpha2/spkg/build/mpir1.2.2.p1/src' make[5]: *** [installdataam] Error 2 make[5]: *** Waiting for unfinished jobs.... [...]
Has anyone else seen this?
Sorry for the delay; I frequently see this since a while on Ubuntus (9.04 & 10.04) when building Sage with e.g. 16 or 32 jobs, with the old MPIR, too; also reported elsewhere (but incidentally also first saw this with MPIR 2.1.1 and the new PARI).
I cannot find obvious errors in the Makefile though; the relevant parts are identical to those of GMP btw, IIRC.
As another incident, I ran into this race condition again yesterday when building Sage 4.4.4 (!) from scratch with MAKE="make j16"
.
comment:25 followup: ↓ 88 Changed 10 years ago by
W.r.t. the race condition, cf. http://trac.sagemath.org/sage_trac/ticket/9343#comment:324
(I currently don't recall if I reported this elsewhere, or my results of inspecting the Makefile... :( )
comment:26 in reply to: ↑ 22 Changed 10 years ago by
 Cc wbhart added
Replying to mpatel:
I noticed that MPIR 2.1.3 is out with a fix in
mpf_get_d_2exp
. But I don't think Sage uses (m)any of thempf_*
functions.
That last statement is wrong. Bill Hart corrects me on sagedevel:
cddlib, ecl, mpmath, mpfr, singular, sympy all, as far as I can see, make extensive use of mpf functions.
Sorry about my mistake!
comment:27 Changed 10 years ago by
 Summary changed from Upgrade Sage's MPIR spkg to version 2.1.2 to Upgrade Sage's MPIR spkg to version 2.1.3 or later
 Work issues set to Fix extension module dependencies; upgrade upstream; fix execstack issue.
I would have taken the latest version anyway...
A trivial fix for the executable stack issue is to add the following to spkginstall
:
case "$UNAME" in Linux) # implies a GNU linker LDFLAGS="$LDFLAGS Wl,z,noexecstack" # already exported by sageenv ;; # perhaps other platforms, too esac
comment:28 Changed 10 years ago by
Copy and paste with typos included... It should of course be Wl,z,noexecstack
.
comment:29 Changed 10 years ago by
 Keywords GMP ECM execstack Fedora 14 added
 Reviewers set to Leif Leonhardy
 Status changed from needs_work to needs_review
 Work issues changed from Fix extension module dependencies; upgrade upstream; fix execstack issue. to Fix extension module dependencies
New spkg: http://spkgupload.googlecode.com/files/mpir2.1.3.p0.spkg
md5sum: f65cbb309ee471d2a64f59e52e592494 mpir2.1.3.p0.spkg
New spkg with updated upstream, "reviewer" changes, fix for Fedora 14 (based on Mike's 2.1.1 spkg).
Setting this to needs review though we still need a patch to the Sage library to fix the extension module dependencies. Can be tested "standalone" (with SAGE_CHECK=yes
), but should be installed together with the new ECM 6.3 spkg from #5847 (also needing review by a third person), since otherwise ECM doesn't build (i.e., the old version doesn't work with GMP 5.x or MPIR 2.x).
Steps to install:
 Download the new MPIR spkg and the ecm6.3.p0.spkg from #5847.
 Copy both files into
$SAGE_ROOT/spkg/standard
(such that 'make' will "see" them).  Then do:
$ export SAGE_CHECK=yes # optional, but recommended $ export SAGE_UPGRADING=yes # required to rebuild all dependent spkgs, too $ export SAGE_PARALLEL_SPKG_BUILD=yes # optional $ export MAKE="make jN" # optional; N: number of 'make' jobs $ time make build # just rebuild Sage (without the documentation) $ # (logs go to install.log and spkg/logs/*) $ ./sage baforce # rebuild the whole Sage library, necessary until # we fix the dependencies in module_list.py $ time make ptestlong NUM_THREADS=N # Use N threads instead of the default number # (also rebuilds the documentation as needed)
 Report back... ;)
(I've so far tested both packages with Sage 4.6.1.alpha0 on Ubuntu 9.04 x86 and Ubuntu 10.04 x86_64.)
comment:30 Changed 10 years ago by
Ooops, I just noticed the hint to rerun make
if the install failed is in the wrong place (it is actually shown if the build failed), but that's IMHO a minor issue I'll perhaps fix later.
comment:31 Changed 10 years ago by
Built and tested on sage.math.washington.edu without problems.
Changed 10 years ago by
Sage library patch. Fixes extension modules not getting rebuilt though depending on MPIR. Based on Sage 4.6.1.alpha0.
comment:32 followup: ↓ 34 Changed 10 years ago by
 Description modified (diff)
comment:33 followups: ↓ 36 ↓ 47 Changed 10 years ago by
 Keywords extension module library dependencies added
 Work issues Fix extension module dependencies deleted
Replying to leif:
Setting this to needs review though we still need a patch to the Sage library to fix the extension module dependencies. [...]
I've attached a patch that fixes the dependency issue with extension modules of the Sage library.
Updated steps to test / install:
 Download the new MPIR spkg and the ecm6.3.p0.spkg from #5847.
 Copy both files into
$SAGE_ROOT/spkg/standard
(such thatmake
will "see" them).  Download the patch to the Sage library. Do not yet apply the patch. (We first rebuild / reinstall dependent spkgs, of which the Sage library is one, so the patched version could get overwritten.)
 Then do:
$ export SAGE_CHECK=yes # optional, but recommended $ export SAGE_UPGRADING=yes # required to rebuild all dependent spkgs, too $ export SAGE_PARALLEL_SPKG_BUILD=yes # optional $ export MAKE="make jN" # optional; N: number of 'make' jobs $ time make build # just rebuild Sage (without the documentation) $ # (logs go to install.log and spkg/logs/*) $ cd devel/sage $ hg import /path/to/trac_8664fix_extmod_deps_for_MPIR_genericallysagelib.patch $ cd ../.. $ ./sage b # rebuild the Sage library; only dependent modules $ time make ptestlong NUM_THREADS=N # Use N threads instead of the default number # (also rebuilds the documentation as needed)
 Report back... ;)
comment:34 in reply to: ↑ 32 ; followup: ↓ 40 Changed 10 years ago by
Replying to jdemeyer:
Don't mess with my ticket while I'm posting... ;)
Can you (or did you) include the patch to the Sage library?
comment:35 Changed 10 years ago by
P.S.: My patch shouldn't conflict with #10094, only the line numbers will change.
comment:36 in reply to: ↑ 33 ; followups: ↓ 38 ↓ 93 Changed 10 years ago by
Replying to leif:
 Download the patch to the Sage library. Do not yet apply the patch. (We first rebuild / reinstall dependent spkgs, of which the Sage library is one, so the patched version could get overwritten.)
Please explain. When can setup.py
be overwritten? This patchedfilesbeingoverwrittenthing has bitten me already several times.
comment:37 Changed 10 years ago by
 Description modified (diff)
comment:38 in reply to: ↑ 36 ; followup: ↓ 39 Changed 10 years ago by
Replying to jdemeyer:
Replying to leif:
 Download the patch to the Sage library. Do not yet apply the patch. (We first rebuild / reinstall dependent spkgs, of which the Sage library is one, so the patched version could get overwritten.)
Please explain. When can
setup.py
be overwritten? This patchedfilesbeingoverwrittenthing has bitten me already several times.
I can only cite from the Sage library's spkginstall
: ;)
... sage syncbuild # Pull in changes from the archive just downloaded. hg pull "$CUR" hg merge tip hg ci m "merge" # Make the pulled in changes take effect. hg update ...
sage syncbuild
calls local/bin/sagesyncbuild.py
.
comment:39 in reply to: ↑ 38 Changed 10 years ago by
Replying to leif:
I can only cite from the Sage library's
spkginstall
: ;)
"In principle"^{TM}, this shouldn't invalidate newer patches already applied (and committed) to the Sage library.
comment:40 in reply to: ↑ 34 Changed 10 years ago by
Replying to leif:
Can you include the patch to the Sage library?
Now it should be also merged, same spkg file.
comment:41 followups: ↓ 42 ↓ 43 Changed 10 years ago by
Does the problem in comment 22 occur during $MAKE install
?
comment:42 in reply to: ↑ 41 Changed 10 years ago by
Replying to mpatel:
Does the problem in comment 22 occur during
$MAKE install
?
I have not encountered this problem (yet), I've built on sage.math.washington.edu
without problems.
If you feel like it, you could put http://sage.math.washington.edu/home/jdemeyer/release/sage4.6.1.alpha0mpir/sage4.6.1.alpha0mpir.tar on the buildbots and see what happens...
comment:43 in reply to: ↑ 41 ; followup: ↓ 44 Changed 10 years ago by
Replying to mpatel:
Does the problem in comment 22 occur during
$MAKE install
?
(cd /home/mpatel/build/cleo/sage4.6.alpha2/local/include && rm f gmp.h && cp mpir.h gmp.h) /usr/bin/install c m 644 'mpir.h' '/home/mpatel/build/cleo/sage4.6.alpha2/local/include/mpir.h'
Smells like it does, doesn't it? ;)
Or did I misunderstand you? (As mentioned in a comment above, the hint to rerun make
is given in the wrong situation.)

spkginstall
diff git a/spkginstall b/spkginstall
a b 123 123 $MAKE 124 124 if [ $? ne 0 ]; then 125 125 echo "Error building MPIR." 126 echo ""127 echo "If you see a message like:"128 cat <<EOF129 cp: cannot stat 'mpir.h': No such file or directory130 make[6]: *** [installdatahook] Error 1131 make[6]: Leaving directory ...132 make[5]: *** [installdataam] Error 2133 make[5]: *** Waiting for unfinished jobs....134 EOF135 echo "above, this is just due to a rare race condition."136 echo "Please simply rerun 'make' (or 'sage i ...')."137 echo ""138 126 exit 1 139 127 fi 140 128 … … 146 134 if [ $? ne 0 ]; then 147 135 if [ "$UNAME" != "CYGWIN" ]; then # On Cygwin an error is not fatal. 148 136 echo "Error installing MPIR." 137 echo "" 138 echo "If you see a message like:" 139 cat <<EOF 140 cp: cannot stat 'mpir.h': No such file or directory 141 make[6]: *** [installdatahook] Error 1 142 make[6]: Leaving directory ... 143 make[5]: *** [installdataam] Error 2 144 make[5]: *** Waiting for unfinished jobs.... 145 EOF 146 echo "above, this is just due to a rare race condition." 147 echo "Please simply rerun 'make' (or 'sage i ...')." 148 echo "" 149 149 exit 1 150 150 fi 151 151 fi
comment:44 in reply to: ↑ 43 Changed 10 years ago by
Replying to leif:
Replying to mpatel: Or did I misunderstand you? (As mentioned in a comment above, the hint to rerun
make
is given in the wrong situation.)
Oooops, I missed your comment. Thanks for pointing it out.
comment:45 Changed 10 years ago by
 Description modified (diff)
comment:46 followup: ↓ 139 Changed 10 years ago by
Any reason to keep
SAGE_CONF_OPTS="enableshared disablestatic"
(i.e., why not build the static library, too)?
comment:47 in reply to: ↑ 33 ; followup: ↓ 48 Changed 10 years ago by
 Status changed from needs_review to needs_work
Replying to leif:
I tried to build mpir2.1.3.p0.spkg on MacOSX 10.5 PPC, and it did not work; sage f mpir2.1.3.p0.spkg bails out with the following:
... gcc std=gnu99 c DHAVE_CONFIG_H g O3 D__GMP_WITHIN_GMP I.. DOPERATION_popcount I. I.. tmppopcount.s fnocommon DPIC o .libs/popcount.o tmppopcount.s:127:vspltisb vector instruction is optional for the PowerPC (not allowed without force_cpusubtype_ALL option) tmppopcount.s:128:vspltisb vector instruction is optional for the PowerPC (not allowed without force_cpusubtype_ALL option) ... etc etc etc ... tmppopcount.s:239:stvx vector instruction is optional for the PowerPC (not allowed without force_cpusubtype_ALL option) make[2]: *** [popcount.lo] Error 1 make[1]: *** [allrecursive] Error 1 make: *** [all] Error 2 Error building MPIR.
comment:48 in reply to: ↑ 47 ; followup: ↓ 49 Changed 10 years ago by
Replying to dimpase:
Replying to leif:
I tried to build mpir2.1.3.p0.spkg on MacOSX 10.5 PPC, and it did not work; sage f mpir2.1.3.p0.spkg bails out with [...]
... tmppopcount.s:127:vspltisb vector instruction is optional for the PowerPC (not allowed without force_cpusubtype_ALL option) ...
Thanks for testing this.
Would adding Wa,force_cpusubtype_ALL
on MacOS PPCs work? (Unless SAGE_FAT_BINARY=yes
... Don't know what to do in that case, i.e. if enablefat
works in that case, too.)
(I think PPC implies [32bit] MacOS X 10.4 or 10.5 in Sage.)
Or do we have to make further distinctions on the CPU type?
For 32bit x86 builds on MacOS X < 10.6 we currently remove a lot of assembly files:
remove_pic_osx_32_bit() { # Assumes we are in src/ echo "Deleting assembly files which depend on PIC assembly" \ "working or 32 bit OSX on Intel hardware..." rm mpn/x86/dive_1.asm rm mpn/x86/diveby3.asm rm mpn/x86/pentium4/sse2/dive_1.asm rm mpn/x86/pentium4/sse2/mode1o.asm rm mpn/x86/pentium4/sse2/diveby3.asm rm mpn/x86/pentium4/mmx/popham.asm rm mpn/x86/pentium4/mmx/rshift.asm rm mpn/x86/p6/mode1o.asm rm mpn/x86/p6/dive_1.asm rm mpn/x86/pentium/hamdist.asm rm mpn/x86/pentium/mod_1.asm rm mpn/x86/pentium/popcount.asm rm mpn/x86/pentium/mode1o.asm rm mpn/x86/pentium/dive_1.asm }
We should report this upstream. Bill, can you forward this?
comment:49 in reply to: ↑ 48 ; followups: ↓ 50 ↓ 51 Changed 10 years ago by
Replying to leif:
Would adding
Wa,force_cpusubtype_ALL
on MacOS PPCs work?
I.e.
$ env CFLAGS="Wa,force_cpusubtype_ALL" ./sage f mpir2.1.3.p0.spkg
Even if this works for you, I'm not sure if MPIR only enables that code on CPUs that really support these instructions. Jeroen apparently has built this spkg on a MacOS X 10.4 PPC G5.
comment:50 in reply to: ↑ 49 ; followup: ↓ 52 Changed 10 years ago by
Replying to leif:
Replying to leif:
Would adding
Wa,force_cpusubtype_ALL
on MacOS PPCs work?Even if this works for you, I'm not sure if MPIR only enables that code on CPUs that really support these instructions. Jeroen apparently has built this spkg on a MacOS X 10.4 PPC G5.
yes, it at least builds without errors this way, on MacOSX 10.5 G4 PPC, with gcc 4.2.1 (Apple Inc. build 5577). Tell me what I should test. (I don't want to rerun the whole Sage testsuite, as it takes ages on this machine, and I use it otherwise too)
comment:51 in reply to: ↑ 49 Changed 10 years ago by
Replying to leif:
Jeroen apparently has built this spkg on a MacOS X 10.4 PPC G5.
Yes, I did. If it helps, I've put the log at http://sage.math.washington.edu/home/jdemeyer/moufang/mpir2.1.3.p0.log.
comment:52 in reply to: ↑ 50 ; followups: ↓ 53 ↓ 57 Changed 10 years ago by
Replying to dimpase:
Replying to leif:
Replying to leif:
Would adding
Wa,force_cpusubtype_ALL
on MacOS PPCs work?Even if this works for you, I'm not sure if MPIR only enables that code on CPUs that really support these instructions. Jeroen apparently has built this spkg on a MacOS X 10.4 PPC G5.
yes, it at least builds without errors this way, on MacOSX 10.5 G4 PPC, with gcc 4.2.1 (Apple Inc. build 5577). Tell me what I should test. (I don't want to rerun the whole Sage testsuite, as it takes ages on this machine, and I use it otherwise too)
Nice, thanks.
Did you run MPIR's test suite (i.e., installed with SAGE_CHECK=yes
)?
I'll update the ECM package (#5847) with the upstream patch, then you could also test this.
I don't know if you already broke your Sage installation by now having successfully installed the new MPIR, since we delete all older versions, which other parts of Sage will still try to use unless you also rebuild the dependent packages.
You can of course always force the reinstallation of the old MPIR (and ECM) package with sage f ...
, then Sage will again work as before.
comment:53 in reply to: ↑ 52 ; followup: ↓ 61 Changed 10 years ago by
Replying to leif:
Replying to dimpase:
Replying to leif:
Replying to leif:
Would adding
Wa,force_cpusubtype_ALL
on MacOS PPCs work?
P.S.: Does Apple's XCode gcc
understand force_cpusubtype_ALL
(i.e., without Wa,
)?
I just noticed at least recent "originals" do on Darwin, but it's perhaps safer to directly pass it to the assembler.
Still need to now what happens on Linux PPC (with gas
)...
comment:54 followup: ↓ 56 Changed 10 years ago by
 Status changed from needs_work to needs_review
New spkg with Darwin fixes: http://spkgupload.googlecode.com/files/mpir2.1.3.p1.spkg
md5sum: 0f13106ed6c8af933f93fa4a8981c453 mpir2.1.3.p1.spkg
I've uploaded a new p1 spkg that fixes the assembler error on Darwin PPC. Attached patch reflects changes between this and the previous one (p0). Use this link to download or apply the patch.
mpir2.1.3.p1 (Leif Leonhardy, November 5th, 2010)
 #8664: Upgrade Sage's MPIR spkg to version 2.1.3
 Fix Darwin assembler errors on PPC by passing the option to allow use of extended instruction set to it. (See also #5847.)
 Enable the build of a static MPIR library, to be e.g. used by ECM.
 Support additional 'configure' options given by MPIR_EXTRA_OPTS, and print messages how we configure.
 Print various environment variable settings (CC, CFLAGS et al.).
 Move hint to rerun 'make' on *install* errors to correct place.
 Further comments added.
comment:55 Changed 10 years ago by
P.S.: Except for the filename, test / installation instructions remain the same. (See above.)
comment:56 in reply to: ↑ 54 ; followup: ↓ 58 Changed 10 years ago by
 Status changed from needs_review to needs_work
Replying to leif:
New spkg with Darwin fixes: http://spkgupload.googlecode.com/files/mpir2.1.3.p1.spkg
md5sum:
0f13106ed6c8af933f93fa4a8981c453 mpir2.1.3.p1.spkg
I've uploaded a new p1 spkg that fixes the assembler error on Darwin PPC. Attached patch reflects changes between this and the previous one (p0). Use this link to download or apply the patch.
This won't work just like this. Ineed:
$ uname m Power Macintosh $ uname a Darwin cantor.local 9.8.0 Darwin Kernel Version 9.8.0: Wed Jul 15 16:57:01 PDT 2009; root:xnu1228.15.4~1/RELEASE_PPC Power Macintosh
so it's not 'ppc', it's 'Power Macintosh' on OSX 10.5, apparently...
comment:57 in reply to: ↑ 52 ; followup: ↓ 59 Changed 10 years ago by
Replying to leif:
Replying to dimpase:
Replying to leif:
Replying to leif:
Would adding
Wa,force_cpusubtype_ALL
on MacOS PPCs work?Even if this works for you, I'm not sure if MPIR only enables that code on CPUs that really support these instructions. Jeroen apparently has built this spkg on a MacOS X 10.4 PPC G5.
yes, it at least builds without errors this way, on MacOSX 10.5 G4 PPC, with gcc 4.2.1 (Apple Inc. build 5577). Tell me what I should test. (I don't want to rerun the whole Sage testsuite, as it takes ages on this machine, and I use it otherwise too)
Nice, thanks.
Did you run MPIR's test suite (i.e., installed with
SAGE_CHECK=yes
)?
I just rerun the installation of p0 with SAGE_CHECK=yes, and all the tests passed. So I suppose it's very close, only that small config fix remains...
I'll update the ECM package (#5847) with the upstream patch, then you could also test this.
I don't know if you already broke your Sage installation by now having successfully installed the new MPIR, since we delete all older versions, which other parts of Sage will still try to use unless you also rebuild the dependent packages.
You can of course always force the reinstallation of the old MPIR (and ECM) package with
sage f ...
, then Sage will again work as before.
Thanks for the reminder, but I am quite familiar with sage f, spkginstall, etc etc... I am involved in maintaining of *gap*.spkg and cvxopt*.spkg...
comment:58 in reply to: ↑ 56 ; followup: ↓ 60 Changed 10 years ago by
Replying to dimpase:
This won't work just like this. Ineed:
$ uname m Power Macintosh $ uname a Darwin cantor.local 9.8.0 Darwin Kernel Version 9.8.0: Wed Jul 15 16:57:01 PDT 2009; root:xnu1228.15.4~1/RELEASE_PPC Power Macintosh
so it's not 'ppc', it's 'Power Macintosh' on OSX 10.5, apparently...
WTF? Which uname
? Some Apple XXXX?
I've never seen any configure
or config.guess
script testing for "Power Macintosh", since this is neither a CPU nor an architecture. (The space is nice, too.)
I'll make a special case for your machine... ;)
[Ok, I've searched now and the only one I've found is Singular's. Some others test for Power*
.]
comment:59 in reply to: ↑ 57 Changed 10 years ago by
Replying to dimpase:
Replying to leif:
I don't know if you already broke your Sage installation by now having successfully installed the new MPIR, since we delete all older versions, which other parts of Sage will still try to use unless you also rebuild the dependent packages.
You can of course always force the reinstallation of the old MPIR (and ECM) package with
sage f ...
, then Sage will again work as before.Thanks for the reminder, but I am quite familiar with sage f, spkginstall, etc etc... I am involved in maintaining of *gap*.spkg and cvxopt*.spkg...
:) Certainly, just ignore... (cf.this nice comment)
But there are other people less familiar with this. (In fact this is a slightly modified copy of what I mailed someone else. I then became aware of not having it mentioned here at all.)
comment:60 in reply to: ↑ 58 ; followup: ↓ 63 Changed 10 years ago by
Replying to leif:
so it's not 'ppc', it's 'Power Macintosh' on OSX 10.5, apparently...
WTF? Which
uname
? Some Apple XXXX?
What a Terrible Failure indeed:
/usr/bin/uname
The choice "Power Macintosh" is undoubtedly the result of an out of court settlement between IBM and Apple :)
comment:61 in reply to: ↑ 53 Changed 10 years ago by
Replying to leif:
Replying to leif:
Replying to dimpase:
Replying to leif:
Replying to leif:
Would adding
Wa,force_cpusubtype_ALL
on MacOS PPCs work?P.S.: Does Apple's XCode
gcc
understandforce_cpusubtype_ALL
(i.e., withoutWa,
)?
yes Apple's gcc 4.2.1 does. As well as gcc4.0.1, which is probably more usual on OSX PPC...
comment:62 Changed 10 years ago by
 Status changed from needs_work to needs_review
Updated p1 spkg: http://spkgupload.googlecode.com/files/mpir2.1.3.p1.spkg (same place)
md5sum: 08dfaa24301ba4e4481cfbbbc77156b3 mpir2.1.3.p1.spkg
Now also recognizes PPCs giving "Power*
" as uname m
.
comment:63 in reply to: ↑ 60 ; followup: ↓ 64 Changed 10 years ago by
Replying to dimpase:
Replying to leif:
so it's not 'ppc', it's 'Power Macintosh' on OSX 10.5, apparently...
WTF? Which
uname
? Some Apple XXXX?What a Terrible Failure indeed:
/usr/bin/uname
What do /bin/uname
and /usr/local/bin/uname
give?
(Consider installing GNU coreutils, and / or perhaps changing the PATH
... ;) )
There are other packages in Sage that won't recognize "Power Macintosh".
The choice "Power Macintosh" is undoubtedly the result of an out of court settlement between IBM and Apple :)
Well, POWER^{TM} is IBMs; the PowerPC was a later joint venture of Apple, IBM and Motorola.
Changed 10 years ago by
SPKG patch. Apply to MPIR 2.1.3.p0 to get the p1. Fixes Darwin assembler error, corrects hint; some improvements.
comment:64 in reply to: ↑ 63 ; followup: ↓ 65 Changed 10 years ago by
 Reviewers changed from Leif Leonhardy to Leif Leonhardy, Dmitrii Pasechnik
Replying to leif:
Replying to dimpase:
Replying to leif:
so it's not 'ppc', it's 'Power Macintosh' on OSX 10.5, apparently...
WTF? Which
uname
? Some Apple XXXX?What a Terrible Failure indeed:
/usr/bin/uname
What do
/bin/uname
and/usr/local/bin/uname
give?(Consider installing GNU coreutils, and / or perhaps changing the
PATH
... ;) )
GNU's uname says:
$ /usr/local/bin/uname m Power Macintosh $ /usr/local/bin/uname a Darwin cantor.local 9.8.0 Darwin Kernel Version 9.8.0: Wed Jul 15 16:57:01 PDT 2009; root:xnu1228.15.4~1/RELEASE_PPC Power Macintosh powerpc PowerBook5,5 Darwin
There are other packages in Sage that won't recognize "Power Macintosh".
The choice "Power Macintosh" is undoubtedly the result of an out of court settlement between IBM and Apple :)
Well, POWER^{TM} is IBMs; the PowerPC was a later joint venture of Apple, IBM and Motorola.
comment:65 in reply to: ↑ 64 Changed 10 years ago by
Replying to dimpase:
GNU's uname says:
$ /usr/local/bin/uname m Power Macintosh $ /usr/local/bin/uname a Darwin cantor.local 9.8.0 Darwin Kernel Version 9.8.0: Wed Jul 15 16:57:01 PDT 2009; root:xnu1228.15.4~1/RELEASE_PPC Power Macintosh powerpc PowerBook5,5 Darwin
Report upstream... ;)
I should have added [Pp]ower*
:/
comment:66 Changed 10 years ago by
 Status changed from needs_review to needs_info
p1 builds and passes all tests on OSX 10.5 PPC (G4), with gcc4.2.1. Except that somewhere in the log I see:
... make[4]: Entering directory `/usr/local/src/sage/sage4.6/spkg/build/mpir2.1.3.p1/src/tests/cxx' ... PASS: tistream Replacing decimal point didn't work, tests skipped PASS: tlocale ...
This does not happen on Debian x64. Probably a harmless (for Sage) C++specific issue. Can this be ignored?
comment:67 followup: ↓ 68 Changed 10 years ago by
however, Sage does not start on OSX 10.5 PPC: I get
$ ./sage b ... g++ o libcsage.dylib single_module flat_namespace undefined dynamic_lookup dynamiclib src/convert.os src/interrupt.os src/mpn_pylong.os src/mpz_pylong.os src/mpz_longlong.os src/stdsage.os src/gmp_globals.os src/ZZ_pylong.os src/ntl_wrap.os L/usr/local/src/sage/sage4.6/local/lib L/usr/local/src/sage/sage4.6/local/lib/python/config lntl lgmp lpari lpython2.6 ld: file not found: /usr/local/src/sage/sage4.6/local/lib/libgmp.3.dylib collect2: ld returned 1 exit status scons: *** [libcsage.dylib] Error 1 ERROR: There was an error building c_lib.
I don't know whether this is a result of this spkg upgrade, or something else was broken even before. I'll see.
comment:68 in reply to: ↑ 67 ; followup: ↓ 70 Changed 10 years ago by
Replying to dimpase:
however, Sage does not start on OSX 10.5 PPC: I get
$ ./sage b ... g++ o libcsage.dylib single_module flat_namespace undefined dynamic_lookup dynamiclib src/convert.os src/interrupt.os src/mpn_pylong.os src/mpz_pylong.os src/mpz_longlong.os src/stdsage.os src/gmp_globals.os src/ZZ_pylong.os src/ntl_wrap.os L/usr/local/src/sage/sage4.6/local/lib L/usr/local/src/sage/sage4.6/local/lib/python/config lntl lgmp lpari lpython2.6 ld: file not found: /usr/local/src/sage/sage4.6/local/lib/libgmp.3.dylib collect2: ld returned 1 exit status scons: *** [libcsage.dylib] Error 1 ERROR: There was an error building c_lib.
I don't know whether this is a result of this spkg upgrade, or something else was broken even before. I'll see.
Did you rebuild all dependent packages, i.e. use SAGE_UPGRADING=yes
?
What MPIR versions do you have in local/lib/
?
I guess the locale issue is a minor thing (hopefully). Perhaps Bill knows better.
(I almost always build with LC_ALL=C
.)
comment:69 Changed 10 years ago by
P.S.: Could you attach the full MPIR build log, or its make install
part?
comment:70 in reply to: ↑ 68 ; followup: ↓ 71 Changed 10 years ago by
Replying to leif:
Did you rebuild all dependent packages, i.e. use
SAGE_UPGRADING=yes
?
I tried
$ SAGE_UPGRADING=yes ../../sage f mpir2.1.3.p1.spkg $ ../../sage b
with the same outcome. Installing the version 1.* mpir spkg cures the installation, i.e. I get a working copy of Sage back.
What MPIR versions do you have in
local/lib/
?
here are mpirs and gmps I have:
rwxrxrx 1 dima wheel 500140 Nov 6 18:48 ../../local/lib/libmpir.8.2.3.dylib lrwxrxrx 1 dima wheel 19 Nov 6 18:48 ../../local/lib/libmpir.8.dylib > libmpir.8.2.3.dylib rwrr 1 dima wheel 2487088 Nov 6 18:48 ../../local/lib/libmpir.a lrwxrxrx 1 dima wheel 19 Nov 6 18:48 ../../local/lib/libmpir.dylib > libmpir.8.2.3.dylib rwxrxrx 1 dima wheel 829 Nov 6 18:48 ../../local/lib/libmpir.la rwxrxrx 1 dima wheel 25592 Nov 6 18:48 ../../local/lib/libmpirxx.2.2.11.dylib lrwxrxrx 1 dima wheel 22 Nov 6 18:48 ../../local/lib/libmpirxx.2.dylib > libmpirxx.2.2.11.dylib rwrr 1 dima wheel 699424 Nov 6 18:48 ../../local/lib/libmpirxx.a lrwxrxrx 1 dima wheel 22 Nov 6 18:48 ../../local/lib/libmpirxx.dylib > libmpirxx.2.2.11.dylib rwxrxrx 1 dima wheel 894 Nov 6 18:48 ../../local/lib/libmpirxx.la rwxrxrx 1 dima wheel 500140 Nov 6 18:48 ../../local/lib/libgmp.8.2.3.dylib lrwxrxrx 1 dima wheel 18 Nov 6 18:48 ../../local/lib/libgmp.8.dylib > libgmp.8.2.3.dylib rwrr 1 dima wheel 2487088 Nov 6 18:48 ../../local/lib/libgmp.a lrwxrxrx 1 dima wheel 18 Nov 6 18:48 ../../local/lib/libgmp.dylib > libgmp.8.2.3.dylib rwxrxrx 1 dima wheel 822 Nov 6 18:48 ../../local/lib/libgmp.la rwxrxrx 1 dima wheel 25592 Nov 6 18:48 ../../local/lib/libgmpxx.2.2.11.dylib lrwxrxrx 1 dima wheel 21 Nov 6 18:48 ../../local/lib/libgmpxx.2.dylib > libgmpxx.2.2.11.dylib rwrr 1 dima wheel 699424 Nov 6 18:48 ../../local/lib/libgmpxx.a lrwxrxrx 1 dima wheel 21 Nov 6 18:48 ../../local/lib/libgmpxx.dylib > libgmpxx.2.2.11.dylib rwxrxrx 1 dima wheel 886 Nov 6 18:48 ../../local/lib/libgmpxx.la
I'm trying the following:
$ cd local/lib $ ln s libgmp.dylib libgmp.3.dylib $ ../../sage b
and this seems to work (triggering a large recompile of extensions that still is running)
comment:71 in reply to: ↑ 70 ; followup: ↓ 72 Changed 10 years ago by
Replying to dimpase:
Replying to leif:
Did you rebuild all dependent packages, i.e. use
SAGE_UPGRADING=yes
?I tried
$ SAGE_UPGRADING=yes ../../sage f mpir2.1.3.p1.spkg $ ../../sage b
with the same outcome.
SAGE_UPGRADING=yes
only works with make
, not sage i ...
etc. (and only if all [new] spkgs are in spkg/standard/
).
Installing the version 1.* mpir spkg cures the installation, i.e. I get a working copy of Sage back.
Yep.
What MPIR versions do you have in
local/lib/
?here are mpirs and gmps I have:
rwxrxrx 1 dima wheel 500140 Nov 6 18:48 ../../local/lib/libmpir.8.2.3.dylib lrwxrxrx 1 dima wheel 19 Nov 6 18:48 ../../local/lib/libmpir.8.dylib > libmpir.8.2.3.dylib rwrr 1 dima wheel 2487088 Nov 6 18:48 ../../local/lib/libmpir.a lrwxrxrx 1 dima wheel 19 Nov 6 18:48 ../../local/lib/libmpir.dylib > libmpir.8.2.3.dylib rwxrxrx 1 dima wheel 829 Nov 6 18:48 ../../local/lib/libmpir.la rwxrxrx 1 dima wheel 25592 Nov 6 18:48 ../../local/lib/libmpirxx.2.2.11.dylib lrwxrxrx 1 dima wheel 22 Nov 6 18:48 ../../local/lib/libmpirxx.2.dylib > libmpirxx.2.2.11.dylib rwrr 1 dima wheel 699424 Nov 6 18:48 ../../local/lib/libmpirxx.a lrwxrxrx 1 dima wheel 22 Nov 6 18:48 ../../local/lib/libmpirxx.dylib > libmpirxx.2.2.11.dylib rwxrxrx 1 dima wheel 894 Nov 6 18:48 ../../local/lib/libmpirxx.la ...
These are the correct new ones, same basenames as on other systems. (Note that the version number of libgmpxx*
is now smaller than in MPIR 1.2.2, which was 3[.1.6]
.)
I'm trying the following:
$ cd local/lib $ ln s libgmp.dylib libgmp.3.dylib $ ../../sage b
and this seems to work (triggering a large recompile of extensions that still is running)
So the patch to the Sage library apparently works for you. :)
The libcsage
linker error occurs because some other library (NTL or PARI) still refers to the old MPIR library, i.e. hasn't been rebuilt.
Can you check the modification times of spkg/installed/*
(e.g. ls rtl spkg/installed
)?
(Or just ls 1rt local/lib/lib{gmp,ntl,pari}*
; all PARI and NTL libraries should be below MPIR's.)
comment:72 in reply to: ↑ 71 ; followups: ↓ 73 ↓ 76 Changed 10 years ago by
Replying to leif:
The
libcsage
linker error occurs because some other library (NTL or PARI) still refers to the old MPIR library, i.e. hasn't been rebuilt.Can you check the modification times of
spkg/installed/*
(e.g.ls rtl spkg/installed
)? (Or justls 1rt local/lib/lib{gmp,ntl,pari}*
; all PARI and NTL libraries should be below MPIR's.)
Is ecm6.2.1 compatible with mpir 2.1.3? Just wondering.
I'm going to rebuild Sage from scratch and with mpir 2.1.3. It will take a night, but it's already pretty later over here.
comment:73 in reply to: ↑ 72 Changed 10 years ago by
Replying to dimpase:
Replying to leif:
The
libcsage
linker error occurs because some other library (NTL or PARI) still refers to the old MPIR library, i.e. hasn't been rebuilt.Can you check the modification times of
spkg/installed/*
(e.g.ls rtl spkg/installed
)? (Or justls 1rt local/lib/lib{gmp,ntl,pari}*
; all PARI and NTL libraries should be below MPIR's.)Is ecm6.2.1 compatible with mpir 2.1.3?
Rather not. (See #5847.)
I'm going to rebuild Sage from scratch and with mpir 2.1.3. It will take a night, but it's already pretty later over here.
You could try faking ecm6.3.p0.spkg (or the old one if you haven't copied the new spkg) was already installed, then at least the build should pass.
comment:74 followup: ↓ 75 Changed 10 years ago by
I asked Bill by email about Leif's comments above. Please see mpirdevel.
comment:75 in reply to: ↑ 74 Changed 10 years ago by
Replying to mpatel:
I asked Bill by email about Leif's comments above. Please see mpirdevel.
I tried a vanilla build from the source, i.e. untarred the spkg, then
$ cd src/ $ ./configure $ make
and it just works, picking up the flag force_cpusubtype_ALL without any help.
comment:76 in reply to: ↑ 72 ; followup: ↓ 79 Changed 10 years ago by
 Status changed from needs_info to needs_review
Replying to dimpase:
Replying to leif:
The
libcsage
linker error occurs because some other library (NTL or PARI) still refers to the old MPIR library, i.e. hasn't been rebuilt.Can you check the modification times of
spkg/installed/*
(e.g.ls rtl spkg/installed
)? (Or justls 1rt local/lib/lib{gmp,ntl,pari}*
; all PARI and NTL libraries should be below MPIR's.)Is ecm6.2.1 compatible with mpir 2.1.3? Just wondering.
I'm going to rebuild Sage from scratch and with mpir 2.1.3. It will take a night, but it's already pretty later over here.
rebuilt Sage 4.6 from scratch with p1 spk of this ticket, the Sage library patch of this ticket applied to sage spkg, and with tweaked ECM spkg (see the ECM ticket). All works, as well as passes testlong (>12 hours on this machine).
Dima
It all worked, as well as all
comment:77 Changed 10 years ago by
 Status changed from needs_review to positive_review
comment:78 Changed 10 years ago by
 Description modified (diff)
comment:79 in reply to: ↑ 76 ; followup: ↓ 80 Changed 10 years ago by
comment:80 in reply to: ↑ 79 Changed 10 years ago by
Replying to jdemeyer:
Replying to dimpase:
and with tweaked ECM spkg (see #5847).
Which "tweaked" ECM spkg do you mean?
The one I made from the spkg on the ticket that 1) avoids the linker crash by supplying a longer assembler program in configure 2) runs ./configure disableasmredc in spkginstall.
I did not yet try the configure patch suggested by Paul:
in fact this bug is already fixed upstream (in revision 1516), see https://gforge.inria.fr/tracker/index.php func=detail&aid=10646&group_id=135&atid=623
comment:81 Changed 10 years ago by
 Merged in set to sage4.6.1.alpha1
 Resolution set to fixed
 Status changed from positive_review to closed
comment:82 Changed 10 years ago by
 Merged in sage4.6.1.alpha1 deleted
 Resolution fixed deleted
 Status changed from closed to new
comment:83 Changed 10 years ago by
 Status changed from new to needs_review
comment:84 Changed 10 years ago by
 Status changed from needs_review to positive_review
comment:85 Changed 10 years ago by
Unmerged from sage4.6.1.alpha1 because of the problems with the ECM package, see #10252.
comment:86 Changed 10 years ago by
 Milestone changed from sage4.6.1 to sage4.6.2
comment:87 Changed 10 years ago by
 Description modified (diff)
comment:88 in reply to: ↑ 25 ; followup: ↓ 89 Changed 10 years ago by
Replying to leif:
W.r.t. the race condition, cf. http://trac.sagemath.org/sage_trac/ticket/9343#comment:324
(I currently don't recall if I reported this elsewhere, or my results of inspecting the Makefile... :( )
I've reported the parallel make install
error on mpirdevel.
comment:89 in reply to: ↑ 88 ; followup: ↓ 90 Changed 10 years ago by
Replying to mpatel:
Replying to leif:
W.r.t. the race condition, cf. http://trac.sagemath.org/sage_trac/ticket/9343#comment:324
(I currently don't recall if I reported this elsewhere, or my results of inspecting the Makefile... :( )
I've reported the parallel
make install
error on mpirdevel.
Just yesterday ran into this for the first time on an old 32bit singlecore HT Pentium 4 (with 8 jobs); I previously only encountered it on Core2s with e.g. 16 or 32 jobs.
comment:90 in reply to: ↑ 89 ; followup: ↓ 92 Changed 10 years ago by
Replying to leif:
Replying to mpatel:
I've reported the parallel
make install
error on mpirdevel.Just yesterday ran into this for the first time on an old 32bit singlecore HT Pentium 4 (with 8 jobs); I previously only encountered it on Core2s with e.g. 16 or 32 jobs.
This has now been fixed in MPIR 2.1.4 (released today), but I'm not going to make any further changes on this ticket.
(I'll open a followup ticket anyway, since I already have an MPIR 2.1.3.p2 spkg with other improvements; MPIR 2.2 is on the way, too.)
comment:91 Changed 10 years ago by
 Summary changed from Upgrade Sage's MPIR spkg to version 2.1.3 or later to Upgrade Sage's MPIR spkg to version 2.1.3
comment:92 in reply to: ↑ 90 Changed 10 years ago by
Replying to leif:
This has now been fixed in MPIR 2.1.4 (released today), but I'm not going to make any further changes on this ticket.
(I'll open a followup ticket anyway, since I already have an MPIR 2.1.3.p2 spkg with other improvements; MPIR 2.2 is on the way, too.)
MPIR 2.2.0 was released today... ;)
comment:93 in reply to: ↑ 36 Changed 10 years ago by
Replying to jdemeyer:
Replying to leif:
 Download the patch to the Sage library. Do not yet apply the patch. (We first rebuild / reinstall dependent spkgs, of which the Sage library is one, so the patched version could get overwritten.)
Please explain. When can
setup.py
be overwritten? This patchedfilesbeingoverwrittenthing has bitten me already several times.
A problem with SAGE_UPGRADING
(whose "external" use is inofficial anyway) is that if the Sage library gets reinstalled because some of its dependencies got rebuilt (which is the typical case), Sage unconditionally switches back to the main
branch without any warning, so previously applied patches to a clone take no longer effect (though they are still there, but no longer in the afterwards current branch, sagemain
). It took me some time to realize that (or in fact track down weird errors caused by this)... ;)
The Sage library's spkginstall
should at least issue a warning when it switches the current branch; perhaps there should be some option to avoid this, since it is IMHO convenient to do e.g. env SAGE_UPGRADING=yes make ptestlong
rather than patching the main
branch or first building a new source distribution to build from scratch (or a new patched Sage library spkg to be installed).
comment:94 followup: ↓ 95 Changed 10 years ago by
 Status changed from positive_review to needs_work
The old mpir spkg compiles with march=<...>, the new spkg here doesn't do that. That is definately a bug.
comment:95 in reply to: ↑ 94 ; followup: ↓ 96 Changed 10 years ago by
 Status changed from needs_work to needs_info
Replying to jdemeyer:
The old mpir spkg compiles with march=<...>, the new spkg here doesn't do that. That is definately a bug.
isn't mpir's config intelligent enough to figure out the right arch?
comment:96 in reply to: ↑ 95 Changed 10 years ago by
 Status changed from needs_info to needs_work
Replying to dimpase:
isn't mpir's config intelligent enough to figure out the right arch?
Yes, but Sage's CFLAGS
override mpir
's optimized CFLAGS
(and this does not happen with the current mpir1.2.2)
comment:97 followup: ↓ 98 Changed 10 years ago by
 Work issues set to Use MPIR's optimized CFLAGS
comment:98 in reply to: ↑ 97 Changed 10 years ago by
Replying to jdemeyer:
as MPIR is at version 2.3.1 already, should all this be rebased? (well, I don't know if it works with ECM 6.3...)
Dima
comment:99 followup: ↓ 100 Changed 10 years ago by
Probably, yes, it should be rebased.
But also the CFLAGS
issue still needs to be fixed...
comment:100 in reply to: ↑ 99 ; followup: ↓ 102 Changed 10 years ago by
Replying to jdemeyer:
Probably, yes, it should be rebased.
But also the
CFLAGS
issue still needs to be fixed...
8S See my comment above.
I still can't believe this ticket didn't get merged month ago, just because (apparently) nobody felt able to give the ECM one (#5847) a final positive review.
The CFLAGS
(or march=
) issue is IMHO completely unrelated  if not irrelevant. ;)
It's easy to extract and merge the relevant parts of MPIR's CFLAGS
without ignoring a user's settings, which I did in the followup spkg (IIRC), mentioned above.
I'll try to take a look at its state during the next days; I'm currently not even sure if I hadn't already uploaded it onto google code...
Cheers.
comment:101 Changed 10 years ago by
Oh, not to mention #9858 (FLINT). :)
(And I guess MPFR also still should be upgraded, an MPC spkg provided...)
comment:102 in reply to: ↑ 100 ; followup: ↓ 103 Changed 10 years ago by
Replying to leif:
The
CFLAGS
(ormarch=
) issue is IMHO completely unrelated  if not irrelevant. ;)
The current MPIR spkg does use machinespecific CFLAGS, the new spkg on this ticket does not. This is a step backwards.
If you think it is irrelevant, please explain why...
comment:103 in reply to: ↑ 102 Changed 10 years ago by
Replying to jdemeyer:
Replying to leif:
The
CFLAGS
(ormarch=
) issue is IMHO completely unrelated  if not irrelevant. ;)The current MPIR spkg does use machinespecific CFLAGS, the new spkg on this ticket does not. This is a step backwards.
If you think it is irrelevant, please explain why...
Give me a realistic showcase where that matters... (i.e., causes a significant decrease in performance) ;)
First of all, the important parts of MPIR are (more or less) handoptimized assembly code, selected by MPIR's configure
(or its parameters*) to best match the detected architecture (where MPIR's config.guess
doesn't always necessarily choose the current nearest one btw.).
A properly configured GCC is usually sufficient, i.e. should default to something like march=native
(or a small subset of processors the actual CPU fits into), at least for people to whom performance is really crucial.
With my current spkg here, the user can always (intentionally or not) use the "global" CFLAGS
, i.e. specify whatever is most appropriate to him or her.
The spkg had been extensively tested  as is, month ago. As always: New changes, new pitfalls. [And even more delay due to a new test / review cycle. That's why I did not make any further changes on this ticket. Speaking of the devil, can someone please give #5847 a positive review?]
 If I haven't already, one (or me) should implement
MPIR_EXTRA_OPTS
or whatever it was called (but I think I already did).
P.S.: Ah, I see. It's already in the p1 here.
comment:104 followup: ↓ 105 Changed 10 years ago by
We really need to get MPIR updated in Sage. What's the status of this?
comment:105 in reply to: ↑ 104 ; followup: ↓ 106 Changed 10 years ago by
Replying to mhansen:
We really need to get MPIR updated in Sage. What's the status of this?
The package builds and works. However, there is still the CFLAGS issue. Me and William Stein think the package should not be merged in its current state, but others disagree.
comment:106 in reply to: ↑ 105 Changed 10 years ago by
Replying to jdemeyer:
Replying to mhansen:
We really need to get MPIR updated in Sage. What's the status of this?
The package builds and works. However, there is still the CFLAGS issue. Me and William Stein think the package should not be merged in its current state, but others disagree.
Ok, I've asked Mercurial about my p2 (which was intended to be a followup):
+=== mpir2.1.3.p2 (Leif Leonhardy, November 24th, 2010) === + * #8664: Upgrade Sage's MPIR spkg to version 2.1.3 + * Further improvements: +  Let MPIR select CPUspecific code generation parameters (for CFLAGS) even + if we (also) pass our own (or userspecified) CC and CFLAGS; these might + be used by MPFR and GMPECM later, too, since MPIR's settings are recorded + in 'gmp.h' / 'mpir.h'. + Don't override usersettings (and respect SAGE_FAT_BINARY, SAGE_DEBUG + etc.) though. Add 'marchnative' if appropriate and supported. + * Recognize also lowercase 'power*' arch (from 'uname m'). + * Major restructuring / reformatting; more comments and messages added.
I'm not sure right now if it's ready for release, at least it is functional as far as I remember; haven't yet committed all changes though.
Still believe we could [and maybe should] merge the p1 as is; upstream has to be updated anyway (once again, sooner or later, but IMHO definitely on a followup ticket).
comment:107 Changed 10 years ago by
 Dependencies set to #5847
Changed 10 years ago by
Sage library patch. Fixes extension modules not getting rebuilt though depending on MPIR. Rebased to Sage 4.7.1.alpha4.
comment:108 followup: ↓ 109 Changed 10 years ago by
MPIR 2.4.0 has now been out over a month: http://mpir.org/ We really, really need to get this upgraded.
comment:109 in reply to: ↑ 108 Changed 10 years ago by
Replying to was:
MPIR 2.4.0 has now been out over a month: http://mpir.org/ We really, really need to get this upgraded.
Well, we could have merged this last year...
Further upstream upgrades should IMHO be made on followups, but shouldn't be a problem once this is in.
Hopefully I can make a FLINT 1.5.2 spkg (cf. #9858) this week, rebasing the one I already have on the latest changes to our 1.5.0, and check / finish the p2 mentioned above which fixes the "CFLAGS
issue" (though I still consider that kind of ridiculous, at least not a reason to delay an overdue major upgrade for month).
The also required new GMPECM package at #5847 was reverted from positive review to "needs work" just because a more or less optional patch to the Sage library would have to be rebased on another that had not even been merged into the at that time current devel release. I did so, but it now again technically needs review.
Changed 10 years ago by
Preliminary "preview" diff between the p1 and the upcoming p2 with improved option handling (CFLAGS etc.)
comment:110 Changed 10 years ago by
I've attached a "preview" diff of the p2 in case that makes anyone happy...
comment:111 Changed 10 years ago by
I have a new p3, but now I'm having the "usual" trouble with PPL (in Sage 4.7.1.rc0).
I.e., installing MPIR works, but after the installation GCC is broken inside Sage, because it tries to use Sage's PPL which still refers to the old libgmpxx.so.3
which got deleted upon installation. (Others are having trouble with unresolved symbols not provided by Sage's PPL.)
It was IMHO a very bad idea to include PPL into Sage using the same name for the shared library, apparently without taking any care of these issues. (GMP / MPIR, MPFR and the  currently optional IIRC  MPC, all used by more recent versions of GCC, are in principle likely dangerous.)
Fortunately^{TM} I can just change my CC
setting to cure the installation, not deleting or copying any libraries or creating symbolic links...
(Apropos, I by incident saw that GAP's spkginstall
is unsetting CC
because not doing so is said to "break the install". That's very very odd as well.)
I'll update the MPIR spkg again to not delete its old shared libraries as a quick fix.
Changed 10 years ago by
Diff between the formerly positively reviewed p1 and the p4. For reference / review.
comment:112 Changed 10 years ago by
 Description modified (diff)
 Keywords Darwin 11 MacOS X 10.7 added
 Status changed from needs_work to needs_review
 Work issues Use MPIR's optimized CFLAGS deleted
New spkg is up:
md5sum:
f84278504f4e1b696030c41cac6e4719 mpir2.1.3.p4.spkg
From a user's view, fixes the "CFLAGS
issue", adds support for MacOS X 10.7 and some messages.
Installation instructions remain the same; I'll perhaps put them into the description later.
mpir2.1.3.p4 (Leif Leonhardy, July 19th, 2011)
 #8664: Upgrade Sage's MPIR spkg to version 2.1.3
 Do not delete old GMP/MPIR shared libraries as Sage's versions of libraries used by GCC might still refer to them, such that their deletion would break GCC inside Sage. (PPL e.g. refers to libgmpxx; MPFR and MPC are equally dangerous, since they're [also] used by recent versions of GCC.)
 Some more messages (e.g on rebuilding the Sage library and other packages after installation) and comments added.
 "Patches" section added.
 Also refreshed the patched gmph.in for SunOS. ;)
mpir2.1.3.p3 (Leif Leonhardy, July 18th, 2011)
 #8664: Upgrade Sage's MPIR spkg to version 2.1.3
 Support MacOS 10.7 (Darwin 11) and later.
 Add warning if SAGE_DEBUG=yes since we then disable optimization.
mpir2.1.3.p2 (Leif Leonhardy, November 24th, 2010)
 #8664: Upgrade Sage's MPIR spkg to version 2.1.3
 Further improvements:
 Let MPIR select CPUspecific code generation parameters (for CFLAGS) even if we (also) pass our own (or userspecified) CC and CFLAGS; these might be used by MPFR and GMPECM later, too, since MPIR's settings are recorded in 'gmp.h' / 'mpir.h'. Don't override usersettings (and respect SAGE_FAT_BINARY, SAGE_DEBUG etc.) though. Add 'marchnative' if appropriate and supported.
 Recognize also lowercase 'power*' arch (from 'uname m').
 Major restructuring / reformatting; more comments and messages added.
(Changes I made relative to the p1 which already had positive review, but got unmerged later.)
Further upstream upgrade to MPIR 2.4.0 (or 2.3.1 if more upstream issues should arise) will come soon on another ticket. We IMHO first should get this welltested upstream release in.
Please build, test and review...
comment:113 Changed 10 years ago by
P.S.: It would perhaps be convenient to either have a testing distribution or at least a Sage (library) package with the patch here applied, since during the automatic rebuild of dependent packages Sage switches back to the "main" branch and may invalidate an already applied patch. The behavior seems to have meanwhile changed a bit though.
comment:114 followup: ↓ 115 Changed 10 years ago by
Ok, to ease testing, I've uploaded a Sage 4.7.1.rc0 library spkg with both patches (from here and #5847) already applied.
You can either build Sage 4.7.1.rc0 from scratch with these three spkgs, or take a Sage 4.7.1.rc0 installation and just install them, automatically rebuilding (only) the dependent spkgs.
 Copy the MPIR spkg and the GMPECM spkg into
$SAGE_ROOT/spkg/standard/
.  Replace the
sage4.7.1.rc0.spkg
with this one (i.e., copy it to$SAGE_ROOT/spkg/standard
and delete the original sincenewest_version
would otherwise take the wrong one).  Build:
 For a build from scratch, simply type
make
.  For rebuilding an existing installation with the new spkgs, type
env SAGE_UPGRADING=yes make
 For a build from scratch, simply type
Note that you currently must not set SAGE_CHECK
to yes
in the above procedures, since the test suite of our current FLINT won't build with the new MPIR.
To run MPIR's and GMPECM's test suites, I'd suggest to simply reinstall them afterwards with env SAGE_CHECK=yes ./sage f mpir2.1.3.p4 ecm6.3.p2
. Likewise, you can also play with different CFLAGS
settings (empty, some nonprocessorspecific flags, with some march=...
or mtune=...
etc. included).
Then preferably run make testlong
or make ptestlong
, though both upstream releases have IMHO already been quite excessively tested.
comment:115 in reply to: ↑ 114 ; followups: ↓ 116 ↓ 117 Changed 10 years ago by
Replying to leif:
I'm currently running this on MacOSX 10.6. Will report as soon as it's done
comment:116 in reply to: ↑ 115 ; followup: ↓ 118 Changed 10 years ago by
comment:117 in reply to: ↑ 115 Changed 10 years ago by
comment:118 in reply to: ↑ 116 Changed 10 years ago by
 Status changed from needs_review to positive_review
comment:119 Changed 10 years ago by
 Milestone changed from sage4.7.1 to sage4.7.2
comment:120 followup: ↓ 121 Changed 10 years ago by
 Milestone changed from sage4.7.2 to sagepending
because it depends on a notyetpositivelyreviewed ticket
comment:121 in reply to: ↑ 120 Changed 10 years ago by
Replying to jdemeyer:
because it depends on a notyetpositivelyreviewed ticket
Well, can't you rereview #5847, which you set back to "needs work"?
The only single thing that has changed there is that the oneline patch to module_list.py
got rebased to Sage 4.7.1.alpha4, in particular it is the same patch, differing just in line numbers (or, more precisely, a single aftercontext line):

../patches/
old new 1 1 # HG changeset patch 2 2 # User Leif Leonhardy <not.really@online.de> 3 # Date 130 704311172004 # Node ID e7b1b631a38756bb37aa5edc7a0e31ff10eaa86a5 # Parent fb00ec75853019eb9799fd863b193fe82ee97c743 # Date 1309863032 7200 4 # Node ID 556a3825c961b6871451652dede6ec3742705482 5 # Parent 8532a2ad1e558cbc91ddaaa6b7cc79956dd1e8ba 6 6 #5847: Add 'noexecstack' flag when linking libecm extension module on Linux. 7 7 8 8 (Not doing so caused trouble on a SkyNet Fedora machine with Sage 4.7.1.alpha1 9 9 and GMPECM 6.3.p2 from #5847, GCC 4.6.0; didn't occur previously.) 10 10 11 diff r fb00ec758530 r e7b1b631a387 module_list.py 12  a/module_list.py Wed May 11 22:39:05 2011 +0000 13 +++ b/module_list.py Thu Jun 02 21:31:51 2011 +0200 14 @@ 561,6 +561,8 @@ 11 (Rebased patch for Sage 4.7.1.alpha4 / #11377) 12 13 diff r 8532a2ad1e55 r 556a3825c961 module_list.py 14  a/module_list.py Sun Jul 03 14:23:12 2011 +0000 15 +++ b/module_list.py Tue Jul 05 12:50:32 2011 +0200 16 @@ 568,6 +568,8 @@ 15 17 Extension('sage.libs.libecm', 16 18 sources = ['sage/libs/libecm.pyx'], 17 19 libraries = ['ecm', 'gmp'], 18 20 + extra_link_args = uname_specific("Linux", ["Wl,z,noexecstack"], 19 21 + []), 20 depends = [SAGE_ ROOT + "/local/include/ecm.h"]),22 depends = [SAGE_INC + "ecm.h"]), 21 23 22 24 Extension('sage.libs.mwrank.mwrank',
comment:122 followup: ↓ 123 Changed 10 years ago by
 Cc jpflori added
comment:123 in reply to: ↑ 122 Changed 10 years ago by
 Milestone changed from sagepending to sage4.7.2
#5847 has a positive review again
comment:124 Changed 10 years ago by
 Keywords sd32 added
Changed 10 years ago by
Sage library patch. Fixes extension modules not getting rebuilt though depending on MPIR. Rebased on Sage 4.7.2.alpha2 / #11376.
comment:125 Changed 10 years ago by
 Description modified (diff)
comment:126 Changed 9 years ago by
 Keywords Lion added
 Merged in set to sage4.7.2.alpha3
 Resolution set to fixed
 Status changed from positive_review to closed
comment:127 Changed 9 years ago by
 Description modified (diff)
Had to fix the changelog and some file permissions.
Corrected spkg at new location.
comment:128 followup: ↓ 129 Changed 9 years ago by
I'm not sure if this is the best place to report this since the ticket has been merged, but in building vanilla sage4.7.2.alpha3 on x86, mpir2.1.3.p4 fails with
../strip_fPIC.sh ../yasm/yasm I .. f elf64 submul_1.as o submul_1.o >/dev/null 2>&1 /bin/bash ../libtool mode=c ../mpn/m4ccas m4=m4 gcc std=gnu99 c DHAVE_CONFIG_H m32 O2 fomitframepointer mtune=core2 march=core2 D__GMP_WITHIN_GMP I.. DOPERATION_lshift I. I.. lshift.asm fPIC DPIC o .libs/lshift.o m4 DHAVE_CONFIG_H D__GMP_WITHIN_GMP DOPERATION_lshift DPIC lshift.asm >tmplshift.s gcc std=gnu99 c DHAVE_CONFIG_H m32 O2 fomitframepointer mtune=core2 march=core2 D__GMP_WITHIN_GMP I.. DOPERATION_lshift I. I.. tmplshift.s fPIC DPIC o .libs/lshift.o tmplshift.s: Assembler messages: tmplshift.s:53: Error: bad register name `%rbx' tmplshift.s:54: Error: bad register name `%rdx' tmplshift.s:55: Error: bad register name `%rsi)' tmplshift.s:56: Error: bad register name `%rdi)' tmplshift.s:57: Error: bad register name `%rsi,%rbx,8)' tmplshift.s:58: Error: bad register name `%rax' tmplshift.s:59: Error: bad register name `%rdx' tmplshift.s:60: Error: bad register name `%rbx' tmplshift.s:64: Error: bad register name `%rsi,%rbx,8)' tmplshift.s:65: Error: bad register name `%rsi,%rbx,8)' tmplshift.s:66: Error: bad register name `%rsi,%rbx,8)' tmplshift.s:67: Error: bad register name `%r8' tmplshift.s:68: Error: bad register name `%rdx' tmplshift.s:69: Error: bad register name `%r11' tmplshift.s:70: Error: bad register name `%rsi,%rbx,8)' ... tmplshift.s:118: Error: bad register name `%rsi,%rbx,8)' tmplshift.s:119: Error: bad register name `%r8' tmplshift.s:120: Error: bad register name `%rdx' tmplshift.s:121: Error: bad register name `%r8' tmplshift.s:122: Error: bad register name `%r8' tmplshift.s:123: Error: bad register name `%rbx' make[4]: *** [lshift.lo] Error 1 make[4]: Leaving directory `/storage/sage/sage4.7.2.alpha3/spkg/build/mpir2.1.3.p4/src/mpn' make[3]: *** [allrecursive] Error 1 make[3]: Leaving directory `/storage/sage/sage4.7.2.alpha3/spkg/build/mpir2.1.3.p4/src' make[2]: *** [all] Error 2 make[2]: Leaving directory `/storage/sage/sage4.7.2.alpha3/spkg/build/mpir2.1.3.p4/src' Error building MPIR.
I've never seen this before. The machine is running debian, but the sage build was done from within a gentoo prefix. So the build is basically one using gentoo. There doesn't seem to be a problem on amd64. I still have the build log.
comment:129 in reply to: ↑ 128 ; followup: ↓ 130 Changed 9 years ago by
Replying to strogdon:
I'm not sure if this is the best place to report this since the ticket has been merged, but in building vanilla sage4.7.2.alpha3 on x86, mpir2.1.3.p4 fails with
tmplshift.s: Assembler messages: tmplshift.s:53: Error: bad register name `%rbx' ... make[4]: *** [lshift.lo] Error 1 ...
I've never seen this before. The machine is running debian, but the sage build was done from within a gentoo prefix. So the build is basically one using gentoo. There doesn't seem to be a problem on amd64. I still have the build log.
See sagerelease and this mpirdevel thread.
I'm sorry I didn't catch this earlier, but it's a waste of resources to run 32bit operating systems (or software in general) on 64bit processors... ;)
I'll provide followup spkgs (also at #11616) that will fix this without the need to set ABI
, but perhaps not that very soon.
By the way, MPIR 2.5.0 should get released in the next days as well, so I'll presumably also make an spkg based on that.
comment:130 in reply to: ↑ 129 Changed 9 years ago by
Replying to leif:
Replying to strogdon:
I'm not sure if this is the best place to report this since the ticket has been merged, but in building vanilla sage4.7.2.alpha3 on x86, mpir2.1.3.p4 fails with
tmplshift.s: Assembler messages: tmplshift.s:53: Error: bad register name `%rbx' ... make[4]: *** [lshift.lo] Error 1 ...
I'll provide followup spkgs (also at #11616) that will fix this without the need to set
ABI
, but perhaps not that very soon.
An MPIR 2.1.3.p5 spkg fixing this is now available at #11896, currently needing review.
comment:131 Changed 9 years ago by
 Dependencies changed from #5847 to #5847, #9858, #11896
 Merged in sage4.7.2.alpha3 deleted
 Milestone changed from sage4.7.2 to sage4.7.3
 Resolution fixed deleted
 Status changed from closed to new
comment:132 Changed 9 years ago by
 Status changed from new to needs_review
comment:133 Changed 9 years ago by
 Status changed from needs_review to positive_review
comment:134 followup: ↓ 135 Changed 9 years ago by
Another cyclic dependency... ;) (#11698 depends on this ticket)
A new FLINT spkg (still 1.5.0, a p10) fixing the FLINT test suite build error (occurring in combination with any recent GMP / MPIR version like the one here) by just applying an upstream patch from FLINT 1.5.2 is ready for review at #9858.
(FLINT 1.5.2 and 1.6 spkgs will now most probably be on followup tickets to #9858.)
comment:135 in reply to: ↑ 134 Changed 9 years ago by
comment:136 Changed 9 years ago by
 Merged in set to sage4.7.3.alpha0
 Resolution set to fixed
 Status changed from positive_review to closed
comment:138 Changed 9 years ago by
 Merged in changed from sage4.7.3.alpha0 to sage4.8.alpha0
 Milestone set to sage4.8
comment:139 in reply to: ↑ 46 Changed 9 years ago by
Replying to leif:
Any reason to keep
SAGE_CONF_OPTS="enableshared disablestatic"(i.e., why not build the static library, too)?
As it turns out, this change seems to break MPIR on Cygwin. See this sagewindows thread.
The XGCD issue needs some work w.r.t. doctests (but not only, see below), maybe David Harvey has something done already in this direction when preparing the optional "true" GMP spkg he maintains. (I don't find the thread right now, but I seem to remember he said something in this direction).
Snippet from a private communication by Bill Hart (MPIR upstream):
Also note that as soon as this ticket here is closed, we should mark #8455 as invalid.