On Jan 15, 2010, at 1:46 PM, Dr. David Kirkby wrote:
Robert Bradshaw wrote:
Em, I'm puzzled by this too. It builds fine with the Sun compiler
kir...@t2:[~] $ /opt/SUNWspro/bin/cc simple_complex.c
kir...@t2:[~] $ ./a.out
CYTHON_CCOMPLEX 1
but not with gcc.
I'll report this as a gcc bug, as that would seem the most likely
reason.
Of course, it works fine with gcc on a wide variety of other
platforms, so I don't know what's up with the Solaris gcc.
Any ideas for a workaround?
- Robert
Well the gcc developers admit it is a bug in 'fixincludes'
Apparently it would be easy to fix if someone with knowledge of
'fixincludes' attempted it.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42753#c10
but nobody has stepped up to do that yet.
Is there any chance you could disable your particular bit of code on
Solaris, if the compiler is gcc? The following will both be defined
under such circumstances.
__sun__
__GNUC__
We will just have to accept that bit wont work. Sage does not pass
all tests on Solaris now, so the loss of some more functionality,
whilst not ideal, is better than not being able to build Sage at all.
It's not easy to disable "this bit" of code on Solaris--not only is it
in an auto-generated, but many other files will be have exactly the
same problem.
- Robert
--
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
