> > The restriction is not due to the physical CPU at all. The physical > CPU's architecture is equal to the architecture that MPIR detects. > That is not the problem. The problem is that Virtualbox does not > support certain instructions inside the VM. And that means that all > VMs made by people using Virtualbox will probably have this problem. > The conditions for this problem to occur are: 1) the physical CPU > supports some instruction x; and 2) Virtualbox does not support > running instruction x inside VMs; and 3) MPIR gets built with > instruction x somewhere in its binary (or fails during the build due > to instruction x being run somewhere in the build process), because it > knew that the *physical* CPU supported that instruction, while it did > not know that the *virtual* CPU does *not* support that instruction. > > At least, that's how I understand the situation. > > -Keshav > > ---- > Join us in #sagemath on irc.freenode.net !- Hide quoted text - > > - Show quoted text -
Just to add my 2 cents. I am using vmplayer which I believe is simliar overall if not in implementation detail. However it supports a somewhat different set of CPU instructions. Fortunately, the solution posted here for virtual box, using march=native, works equally well for vmplayer. Adam -- To post to this group, send an email to sage-devel@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
