[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #32279] Definition of 'Complex' causes build f

From: Kai Habel
Subject: [Octave-bug-tracker] [bug #32279] Definition of 'Complex' causes build failure with fltk1.3
Date: Fri, 28 Jan 2011 16:28:52 +0000
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20101026 SUSE/3.6.12-0.7.1 Firefox/3.6.12


                 Summary: Definition of 'Complex' causes build failure with
                 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



This has been reported some time ago:


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


>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:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]