Hi Elias, I can't see any serious problems there. So I guess it is a virtual box issue.
The only problem I can see is that you have CC=gcc-4.6 instead of CC="gcc-4.6 -std=gnu99", though if it compiles, then this is probably not a problem. You should also see what other options are passed to GCC when configuring automatically, i.e. configure without overriding CFLAGS and see what CFLAGS it uses. Simply replace the -march option but leave the other options as they are. For example, on my machine it uses: CFLAGS="-m64 -O2 -march=k8 -mtune=k8" So I would overwrite that with CFLAGS="-m64 -O2 -march=native -mtune=native" presumably. Anyhow, the options you are using are probably ok. Note that you can't use -O3 with gcc-4.6 due to bugs in the compiler. Bill. On 15 November 2012 16:21, Elias <elias.tsigari...@gmail.com> wrote: > Hi Bill, > the ./config.guess gives > sandybridge-unknown-linux-gnu > > the cpuinfo is > processor : 0 > vendor_id : GenuineIntel > cpu family : 6 > model : 42 > model name : Intel(R) Core(TM) i5-2557M CPU @ 1.70GHz > stepping : 7 > cpu MHz : 1688.048 > cache size : 6144 KB > fpu : yes > fpu_exception : yes > cpuid level : 5 > wp : yes > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca > cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx rdtscp lm constant_tsc > up rep_good nopl pni monitor ssse3 lahf_lm > bogomips : 3376.09 > clflush size : 64 > cache_alignment : 64 > address sizes : 36 bits physical, 48 bits virtual > power management: > > > and the first lines of config.log are (I am sorry, I can not attach a file) > > $ ./configure --prefix=/home/elias/ --enable-cxx=yes > --enable-gmpcompat=yes CC=gcc-4.6 CXX=g++-4.6 > > ## --------- ## > ## Platform. ## > ## --------- ## > > hostname = aeolus-lu64 > uname -m = x86_64 > uname -r = 3.5.0-18-generic > uname -s = Linux > uname -v = #29-Ubuntu SMP Fri Oct 19 10:26:51 UTC 2012 > > /usr/bin/uname -p = unknown > /bin/uname -X = unknown > > /bin/arch = unknown > /usr/bin/arch -k = unknown > /usr/convex/getsysinfo = unknown > /usr/bin/hostinfo = unknown > /bin/machine = unknown > /usr/bin/oslevel = unknown > /bin/universe = unknown > > PATH: /usr/lib/lightdm/lightdm > PATH: /usr/local/sbin > PATH: /usr/local/bin > > > -- Elias > > > > On Thursday, November 15, 2012 4:13:40 PM UTC+1, 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. -- 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.