Re: [matplotlib-devel] compiling on Solaris (and going against the python API)

2010-09-17 Thread Jason Grout
On 9/17/10 1:57 AM, Eric Firing wrote: > On 09/16/2010 08:21 PM, Christoph Gohlke wrote: >> >> >> On 9/16/2010 8:15 PM, Jason Grout wrote: >>> On 9/16/10 10:00 PM, Eric Firing wrote: On 09/16/2010 04:12 PM, Jason Grout wrote: > On 9/16/10 9:03 PM, Jason Grout wrote: >> On 9/16/10 8:00

Re: [matplotlib-devel] compiling on Solaris (and going against the python API)

2010-09-17 Thread Eric Firing
On 09/16/2010 09:27 PM, Jason Grout wrote: > On 9/17/10 1:57 AM, Eric Firing wrote: >> On 09/16/2010 08:21 PM, Christoph Gohlke wrote: >>> >>> >>> On 9/16/2010 8:15 PM, Jason Grout wrote: On 9/16/10 10:00 PM, Eric Firing wrote: > On 09/16/2010 04:12 PM, Jason Grout wrote: >> On 9/16/10

Re: [matplotlib-devel] compiling on Solaris (and going against the python API)

2010-09-17 Thread John Hunter
On Fri, Sep 17, 2010 at 3:04 AM, Eric Firing wrote: > Before making that change, I verified that at least on my linux system, > Python.h defines those two variables the same way that features.h does, > so the redefinition would be harmless if we did not undefine the > variables. I don't think we

Re: [matplotlib-devel] compiling on Solaris (and going against the python API)

2010-09-17 Thread Jason Grout
On 09/17/2010 03:04 AM, Eric Firing wrote: > On 09/16/2010 09:27 PM, Jason Grout wrote: >> >> >> I see the change that you made (keep the old order for linux, do the new >> thing for everything else). This seems like a bad thing to do. Looking >> at setjmp.h, it includes features.h. features.h