On 23/04/2008, Joshua Lippai <[EMAIL PROTECTED]> wrote:
> Alternatively, if you're only building this for your own use and not
> for packaging a Universal Binary you want PowerPC users to be able to
> use, you could simply eliminate the ppc arch flags in the Makefile
> inside
> /Library/Framewo
Alternatively, if you're only building this for your own use and not
for packaging a Universal Binary you want PowerPC users to be able to
use, you could simply eliminate the ppc arch flags in the Makefile
inside /Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/config/
On Mon, Apr 2
On Tue, Apr 22, 2008 at 5:28 PM, Charlie Moad <[EMAIL PROTECTED]> wrote:
> The internal compiler error is something we are all running into right now.
> The only known fix is to run the build with the gcc flag "-Os" instead of
> "-O3". You should be able to do this by setting the environment duri
The internal compiler error is something we are all running into right now.
The only known fix is to run the build with the gcc flag "-Os" instead of
"-O3". You should be able to do this by setting the environment during your
build:
CFLAGS="-Os" python setup.py build
On Mon, Apr 21, 2008 at 8:24
Hello OSX SVN MPL users
I am following the instructions on
http://ipython.scipy.org/moin/Py4Science/InstallationOSX
and ran into some trouble.
The computer is a 13" intel macbook,
OSX 10.5.2 installed fresh in December 2007
Everything went reasonably well until I got to matplotlib.
I ran into
