Hi James, It looks to me like your compiler is failing a test which is designed to pick up buggy compilers.
The compiler itself says that there is an internal bug and you should report it. I don't think there is anything we can do about this. Certainly gcc 4.3 is pretty buggy. I'd be inclined to update your compiler, as this bug is probably fixed in a later version. Bill. Hi Bill > This is actually a bug in MPIR. It should work fine on your hardware. > > Can you please post the error messages you get when you type configure. >From what I've found on Google, there are two ways to rebuild the packages that are suspected of generating "illegal instruction" errors: $ rm spkg/installed/mpir* spkg/installed/atlas* $ make and $ ./sage -f mpir-xxx $ ./sage -f atlas-xxx So, rebuilding mpir, using $ gcc --version gcc (Ubuntu 4.3.2-1ubuntu12) 4.3.2 where, I don't think it's a hardware problem, since I just built open-axiom from source, and no crashes or problems over two hours of comiling, then: ...<lots of mpir files...> checking compiler gcc -O2 -fomit-frame-pointer ... no, long long reliability test 1 configure: error: could not find a working compiler, see config.log for details Failed to configure. real 0m7.513s user 0m2.812s sys 0m1.996s sage: An error occurred while installing mpir-1.2.p4 Please email sage-devel http://groups.google.com/group/sage-devel explaining the problem and send the relevant part of of /opt/sage-4.1.1-linux-Debian_GNU_Linux_5.0_lenny-i686-Linux/install.log. Describe your computer, operating system, etc. If you want to try to fix the problem, yourself *don't* just cd to /opt/sage-4.1.1-linux-Debian_GNU_Linux_5.0_lenny-i686-Linux/spkg/build/mpir-1.2.p4 and type 'make'. Instead type "/opt/sage-4.1.1-linux-Debian_GNU_Linux_5.0_lenny-i686-Linux/sage -sh" in order to set all environment variables correctly, then cd to /opt/sage-4.1.1-linux-Debian_GNU_Linux_5.0_lenny-i686-Linux/spkg/build/mpir-1.2.p4 (When you are done debugging, you can type "exit" to leave the subshell.) make[1]: *** [installed/mpir-1.2.p4] Error 1 make[1]: Leaving directory `/opt/sage-4.1.1-linux-Debian_GNU_Linux_5.0_lenny-i686-Linux/spkg' real 0m56.995s user 0m16.733s sys 0m5.560s Error building Sage. And from the config.log configure:5112: gcc -O2 -fomit-frame-pointer conftest.c >&5 conftest.c: In function 'e': conftest.c:16: internal compiler error: Illegal instruction Please submit a full bug report, with preprocessed source if appropriate. See <file:///usr/share/doc/gcc-4.3/README.Bugs> for instructions. configure:5115: $? = 1 failed program was: /* The following provokes a segfault in the compiler on powerpc-apple-darwin. Extracted from tests/mpn/t-iord_u.c. Causes Apple's gcc 3.3 build 1640 and 1666 to segfault with e.g., -O2 -mpowerpc64. */ #ifdef __GNUC__ typedef unsigned long long t1;typedef t1*t2; __inline__ t1 e(t2 rp,t2 up,int n,t1 v0) {t1 c,x,r;int i;if(v0){c=1;for(i=1;i<n;i++){x=up[i];r=x+1;rp[i]=r;}}return c;} f(){static const struct{t1 n;t1 src[9];t1 want[9];}d[]={{1,{0},{1}},};t1 got[9];int i; for(i=0;i<1;i++){if(e(got,got,9,d[i].n)==0)h();g(i,d[i].src,d[i].n,got,d[i].want,9);if(d[i].n)h();}} h(){}g(){} #else int dummy; #endif int main () { return 0; } configure:5520: result: no, long long reliability test 1 configure:5758: error: could not find a working compiler, see config.log for details which also shows #define PACKAGE "mpir" #define VERSION "1.2" #define WANT_FFT 1 #define HAVE_HOST_CPU_k7 1 Let me know if you need the whole thing. BTW, atlas also fails to build, but gets as far as /opt/sage-4.1.1-linux-Debian_GNU_Linux_5.0_lenny-i686-Linux/spkg/build/atlas-3.8.3.p7/ATLAS-build/../src//bin/atlas_install.c: In function ‘GetString’: /opt/sage-4.1.1-linux-Debian_GNU_Linux_5.0_lenny-i686-Linux/spkg/build/atlas-3.8.3.p7/ATLAS-build/../src//bin/atlas_install.c:876: internal compiler error: Illegal instruction Thanks for your help. James 2009/10/5 Bill Hart <[email protected]>: > Hi James, > > This is actually a bug in MPIR. It should work fine on your hardware. > > Can you please post the error messages you get when you type configure. > > Bill. > > --- On Mon, 10/5/09, James <[email protected]> wrote: > >> From: James <[email protected]> >> Subject: illegal instructions and sage >> To: "William Hart" <[email protected]> >> Date: Monday, October 5, 2009, 6:56 AM >> Hi >> >> I'd like to plead for support of older hardware. >> >> I still run an older athlon, >> >> $ cat /proc/cpuinfo >> vendor_id : AuthenticAMD >> cpu family : 6 >> model : 4 >> model name : AMD Athlon(tm) processor >> stepping : 2 >> cpu MHz : 1333.169 >> cache size : 256 KB >> ... >> cpuid level : 1 >> wp : yes >> flags : fpu >> vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov >> pat pse36 mmx fxsr syscall mmxext 3dnowext 3dnow up >> bogomips : 2666.33 >> clflush size : 32 >> power management: >> >> and I wanted to run a recent version of sage, >> sage-4.1.1-linux-Debian_GNU_Linux_5.0_lenny-i686-Linux.tar.gz. >> >> Well, as you probably already know, this will not work >> because of some of the >> instruction extensions used in mpir, particularly the sse >> instructions, which >> my processor does not have. I tried to simply >> recompile mpir for my older >> processor, with >> >> ./sage -f mpir-1.2.p4 >> >> but, again, this will not work. mpir does not even >> get past the "configure" >> tests. >> >> Apparently, mpir insists on using the extended instruction >> set, and simply >> fails to compile without them. >> >> This is quite the "show stopper" for any of us with older >> hardware - no mpir, >> and no sage either. >> >> So then, I now plead for your support of older hardware in >> mpir, by making >> whatever changes in "configure" and in the effected code, >> which will allow for >> some kind of "fallback" code to be produced. >> >> Please. Please? >> >> >> James >> >> > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "mpir-devel" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/mpir-devel?hl=en -~----------~----~----~----~------~----~------~--~---
