Was the option -O1 passed to gcc in all instances where the problem occurred?
I have heard of instances where -O1 will cause macro errors which cause the compiler to shut down. When a higher optimisation level is used the macro which causes the crash in gcc is optimised away. If that turns out to be the issue, the solution will be to simply compile that one file with -O2 optimisation. For most things -O1 is far too slow anyway. Bill. 2009/11/14 William Stein <wst...@gmail.com>: > > On Sat, Nov 14, 2009 at 12:05 AM, Jason Moxham > <ja...@njkfrudils.plus.com> wrote: >> >> Hi >> >> I thought I would give it a try , but I cant login to debian32 , doesn't like >> my password , although boxen and fedora32 are OK ?? >> I thought the passwords were all the same for the virtual machines. > > No. I've added your login info so you should be able to login now. > >> >> I havent managed to reproduce any error on some other 32bit machines but >> nothing was exactly the same. > > You might want to try starting by doing > > export SAGE_FAT_BINARY="yes" > > then build sage-4.2.1.tar by typing "make", which is at > > http://sage.math.washington.edu/home/wstein/farm/src/ > > It'll take a few hours, but you should get the error. > > William > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
