Well there's no doubt that it's happening. The compiler had no problem at all building and installing mpc, mpfr, gmp, ppl, and cloog, so it's not a problem with how it handles complex numbers as such. It's something in the interaction of Sage, gcc, and Sun Studio.
-drl On Feb 29, 6:00 am, David Kirkby <david.kir...@onetel.net> wrote: > On 29 February 2012 09:18, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote: > > > On 2012-02-29 02:37, deSitter wrote: > > > Simply including complex.h in base.c would probably work > > No. > > > > My guess is a problem with gcc. > > Are you absolutely certain that you are using gcc-4.6.2? I have seen > > this problem with older versions of gcc but never with gcc-4.6.2. > > There is one file (I've no idea what one), where this problem occured > before and was "solved". The result was to conditionally define a couple of > things if the GCC version was between X and Y. The compiler defines things > like MAJOR_VERSION (just guessing). > > To my knowledge there is no such problem with modern GCC versions. If it's > an older gcc, we can work around it, though I forget how we did, as it was > so long ago. > > Dave -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
