[Octave-bug-tracker] [bug #32279] Definition of 'Complex' causes build failure with fltk1.3

[Kai Habel]

URL:
  <http://savannah.gnu.org/bugs/?32279>

                 Summary: Definition of 'Complex' causes build failure with
fltk1.3
                 Project: GNU Octave
            Submitted by: kahacjde
            Submitted on: Fri 28 Jan 2011 05:28:51 PM CET
                Category: Libraries
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Build Failure
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: GNU/Linux

    _______________________________________________________

Details:

This has been reported some time ago:

http://octave.1599824.n4.nabble.com/octave-build-issue-error-in-fltk-backend-td2309879.html

I don't know how one handles such cases. Should we undefine 'Complex' before
we define it in oct-cmplx.h?

Kai 

>The problems seems to be that fltk1.3 includes X11/X.h. There >is the
>following definition
>
>/* Polygon shapes */
>
>#define Complex                        0       /* paths may >intersect */
>#define Nonconvex               1       /* no paths intersect, >but not
>convex */
>#define Convex                  2       /* wholly convex */
>
>this collides with liboctave/oct-cmplx.h:
>
>#include <complex>
>
>typedef std::complex<double> Complex;
>typedef std::complex<float> FloatComplex; 





    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?32279>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/