The problem is that virtual machines incompletely implement some of the instructions available on the native processors MPIR is optimised for.
We can't really do much about it. The workaround is to use a different VM, specify a --build= flag to MPIR's configure, or set up the VM to emulate a different processor. I don't think that updating the script is a good idea. It just introduces the potential for further bugs in real machines. Bill. On 12 December 2012 21:25, Nicholas Kinar <n.ki...@usask.ca> wrote: > For completeness: > > 1. Here is the config.log file: > > https://docs.google.com/open?id=0B-xY4xORAoEDbUtmdnV3RE1oMFU > > 2. The result of ./config.guess is: > > sandybridge-unknown-linux-gnu > > 3. Here is the result of running cpuinfo: > > https://docs.google.com/open?id=0B-xY4xORAoEDQTdrZ2NfT21PZmM > > If this is a known issue, then perhaps the documentation or even the script > could be updated? Perhaps this could be included as a "known issue" in the > INSTALL file? > > To test some more, I will try another virtual machine (perhaps Vmware > player). > > Nicholas > > > > -- 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.
