Re: [matplotlib-devel] weird error with gcc 4.4, gomp, cython, and matplotlib

[Hoyt K. <ho...@gm...>]

On Thu, Jan 28, 2010 at 2:00 AM, Robert Bradshaw
<rob...@ma...> wrote:
[snip]
> I'm guessing that's the issue, but just to be sure, try using the bare

I still get the error with the super-bare extension module, so
cython's off the hook :-).

> Have you verified that the same C++ compiler and version of libstdc++ is
> being used for everything?

I've tried it two ways; first with everything -- numpy, scipy,
matplotlib -- installed and compiled from svn, and one with them
installed from the latest ubuntu repositories.  I also tried it on
both machines I have access to; a 64bit server with gcc 4.3.3 and
python 2.6.2, and a 32bit one with gcc 4.4.1 and python 2.6.4. The
error is the same on both of those.  The python version and the gcc
compiler are the two things in common.

> If you did upgrade NumPy, rebuild *everything* of compiled code
> which depends on it.

Yes I did do that, and recompiled everything, but still good to check.

gcc is smelling fishier and fishier (or maybe python 2.6?).

-- Hoyt

++++++++++++++++++++++++++++++++++++++++++++++++
+ Hoyt Koepke
+ University of Washington Department of Statistics
+ http://www.stat.washington.edu/~hoytak/
+ ho...@gm...
++++++++++++++++++++++++++++++++++++++++++