Hello Michael, > Ok, if that does the trick I will merge the fix into 2.8.14 provided > it compiles locally on the test boxen (which it should). I looked at > the configure log in detail and it seems very weired that it fails > that late because it does find a gmp and gmp headers. Hm, I'm not sure, whether my patch is more a workaround than the actual solution. In the original spsk_install it reads '--with-gmp-dir="$SAGE_LOCAL" '. So gmo is also searched for in SAGE_LOCAL. But there is no libgmp.a in SAGE_LOCAL (only .so, .la ...). I suspect, it should be there independent of the case whether there is a system-wide gmp, doesn't it?
> Oh well, Sage never builds out of the box for everybody. It is like > playing a whack a mole :) Indeed, indeed. First I had to change to a different servers, because it didn't build on "my" machine, because of the usual gcc 4.1.0 compiler-bug. (I'm still waiting for our edp-department to update gcc on my usual machine.) Best regards, Alexander --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~----------~----~----~----~------~----~------~--~---
