#7932: _Complex_I undeclared - a new bug totally stops a Solaris 10 build.
------------------------+---------------------------------------------------
Reporter: drkirkby | Owner: drkirkby
Type: defect | Status: new
Priority: blocker | Milestone: sage-4.3.1
Component: solaris | Keywords:
Work_issues: | Author:
Upstream: N/A | Reviewer:
Merged: |
------------------------+---------------------------------------------------
Comment(by drkirkby):
I've no idea why, but it does build and run as expected with the Sun
Studio compiler on t2.math.washington.edu (a Sun T5240 SPARC)
{{{
kir...@t2:[~] $ /opt/SUNWspro/bin/cc simple_complex.c
kir...@t2:[~] $ ./a.out
CYTHON_CCOMPLEX 1
}}}
and also on my Sun Sun Ultra 27 (Intel Xeon) with Sun Studio 12.1
{{{
drkir...@hawk:~$ /opt/sunstudio12.1/bin/cc simple_complex.c
drkir...@hawk:~$ ./a.out
CYTHON_CCOMPLEX 1
}}}
but as you say, not on t2 if one uses 'gcc'. Nor does it build with gcc on
my Sun Ultra 27 which has gcc 4.3.4 (the least buggy gcc according to
some).
{{{
drkir...@hawk:~$ gcc simple_complex.c
simple_complex.c: In function ‘__pyx_t_double_complex_from_parts’:
simple_complex.c:20: error: ‘_Complex_I’ undeclared (first use in this
function)
simple_complex.c:20: error: (Each undeclared identifier is reported only
once
simple_complex.c:20: error: for each function it appears in.)
}}}
This rather makes me think it is gcc bug, rather than a system header
file.
Dave
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/7932#comment:4>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" 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/sage-trac?hl=en.
