Chris <listservs@...83...> writes:
>
> Based on recent emails, this looks like a problem attributed to the gcc
> version, not the python version. Suggested solutions are compile with
> the -Os flag or use gcc 4.2.
>
I think universal builds may have to
wait for another day, when gcc 4.2 is ready for prime time.
Actually, the -0s flag with gcc 4.0 seemed to work just fine. Thanks.