Yes, you should only get invalid instruction errors when it is compiling for the wrong machine. So either MPIR detected it incorrectly, or the virtual machine is configured incorrectly, or there is a compiler bug. The latter is a distinct possibility. gcc 4.6.0 is pretty buggy.
Bill. On 15 November 2012 15:22, Jean-Pierre Flori <jpfl...@gmail.com> wrote: > > > On Thursday, November 15, 2012 9:13:40 AM UTC-6, Bill Hart wrote: >> >> Hi Elias, >> >> this might be to do with the virtual box, as we've tested on a large >> number of real machines and not encountered this yet. >> >> You may have to tell mpir's configure what the machine actually is by >> passing a --build=whatever >> >> Can you tell us what ./config.guess says on your system. Also, could >> you attach a copy of the config.log. >> >> Can you also attach the output of cat /proc/cpuinfo >> >> Thanks, >> >> Bill. >> >> On 15 November 2012 14:13, Elias <elias.ts...@gmail.com> wrote: >> > Dear developers, >> > when I do a make check with mpir 2.6.0, I get the following error >> > /bin/bash: line 1: 17730 Illegal instruction (core dumped) "$tst" > >> > t-get_d.log-t 2>&1 >> > I am running lubuntu 12.10 using a virtual box in mac os lion. >> > The compiler is gcc 4.6 >> > Probably this causes problem in the installation of flint, but I will >> > send >> > another email for this. >> > >> > Can you please help me with this? >> > >> > best, >> > >> > -- Elias >> > >> > -- >> > You received this message because you are subscribed to the Google >> > Groups >> > "mpir-devel" group. >> > To view this discussion on the web visit >> > https://groups.google.com/d/msg/mpir-devel/-/YAi4NCxUpWAJ. >> > To post to this group, send email to mpir-...@googlegroups.com. >> > To unsubscribe from this group, send email to >> > mpir-devel+...@googlegroups.com. >> > For more options, visit this group at >> > http://groups.google.com/group/mpir-devel?hl=en. > > I remember that we had problem with Sage built within Virtualbox, because > although Virtualbox exposes the right type of processor and so gcc uses the > right set of instructions, it does not really give you access to the > complete set of instructions, whence potential SIGILL arising. > Not sure how this was dealt with in Sage, but you might find some hints on > sage-devel or the Sage's trac. > Or this could be unrelated. -- 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.
