Hoyt Koepke wrote: > Yes I did do that, and recompiled everything, but still good to check. > > gcc is smelling fishier and fishier (or maybe python 2.6?).
Please post a simple example on the Python developer list that can reproduce the error with GCC 4.4. We have had issue with new GCC releases in the past. Sometimes new optimizations are the culprit of strange faults. You may want to play around with different -O levels, too. Sometimes the error doesn't occur with less optimizations. Please make sure you are using the correct compiler flags, especially -fno-strict-aliasing and -fwrapv. python2.6-config should give you the correct compilers flags. Christian _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
