Actually, if you are preparing binaries of Macaulay the normal thing would be to use --enable-fat. But for core2, this will specifically pick the broken core2 code in your case. So, in actual fact, the --build=x86_64 would be the only safe option if you are using custom allocation, at the moment anyhow.
Bill. 2009/12/10 Dan Grayson <d...@math.uiuc.edu>: > Yup, that's how I was going to work around it. Actually, I should > have been doing it anyway, because I'm trying to prepare distributions > of Macaulay2 that will work on all architectures. Somehow I forgot to > do it. (A consequence of that is that if someone wants a fast > Macaulay2 in which the mpir uses code optimized to their architecture, > they should compile Macaulay2 from sources. At least until we find > mpir distributed with the OS so Macaulay2 can list it as a > prerequisite.) > > By the way, isn't there a more generic way to build mpir to be safe > and generic, without learning the entire poset of architecture names? > > On Dec 10, 8:09 am, Bill Hart <goodwillh...@googlemail.com> wrote: >> By the way, in the mean time, the following may be a workaround for you. > ... >> >> To use a "safe" default x86_64 build, use the following: >> >> ./configure --build=x86_64 > > -- > > You received this message because you are subscribed to the Google Groups > "mpir-devel" group. > To post to this group, send email to mpir-de...@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. > > > -- You received this message because you are subscribed to the Google Groups "mpir-devel" group. To post to this group, send email to mpir-de...@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.
