On Fri, May 18, 2012 at 6:19 AM, Keshav Kini <keshav.k...@gmail.com> wrote: > Jeroen Demeyer <jdeme...@cage.ugent.be> writes: >> Something else to try: build with SAGE_FAT_BINARY=yes. Perhaps the >> run-time CPU detection works better. > > Yup, that works. But it's still a workaround and not really a solution. > It would be nice if I could type "make" and have everything just work.
Building with SAGE_FAT_BINARY will result in other parts of Sage (e.g., ATLAS) being built much less efficiently. It's far better to use CFLAGS="-O2 -march=native" ./sage -i mpir which does seem to work. Many thanks for working on somehow fixing this. I think a lot of people use virtualbox, so having MPIR building broken there is not good... What do the MPIR dev's think is an acceptable solution here? -- William > > -Keshav > > ---- > Join us in #sagemath on irc.freenode.net ! > > -- > To post to this group, send an email to sage-de...@googlegroups.com > To unsubscribe from this group, send an email to > sage-devel+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/sage-devel > URL: http://www.sagemath.org -- William Stein Professor of Mathematics University of Washington http://wstein.org -- You received this message because you are subscribed to the Google Groups "mpir-devel" group. To post to this group, send email to mpir-devel@googlegroups.com. To unsubscribe from this group, send email to mpir-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/mpir-devel?hl=en.
