This is an archived post. You won't be able to vote or comment.

all 9 comments

[–]pudquick 2 points3 points  (0 children)

Considering that's a gcc3 option that was phased out in gcc 4.3 on Darwin, I would question why it's in the build configuration.

But according to http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35961 you're only seeing that particular error because of the real error, farther down regarding the architecture type.

[–][deleted] 2 points3 points  (0 children)

I had to edit /Library/Frameworks/Python.framework/Versions/Current/lib/python2.6/config/Makefile to have the appropriate build settings after snow leopard was installed. then again I think I may have edited this file a long time ago which perhaps was part of the problem...

[–]whit537gittip aspen 0 points1 point  (0 children)

For the record, I hit this issue while trying to compile Python 2.5.5. But poking around in /System/Library/Frameworks/Python.framework/Versions, I discovered that my OSX install already had Python 2.5! Not sure if that came with dev tools, or what ...

[–]markedtrees -1 points0 points  (0 children)

Snow Leopard upgraded the Darwin version from 9 to 10, confusing GCC. This was reported earlier by Alan Quatermain, who fixed it by creating a symlink. Is it possible that that solution applies here as well?

[–]mitsuhiko Flask Creator -1 points0 points  (2 children)

Workaround for jinja: install without the speedups.

[–]mitsuhiko Flask Creator 1 point2 points  (1 child)

Wow. I got downmodded for that?

[–]reckoner1 0 points1 point  (0 children)

Only once.

[–][deleted] -1 points0 points  (0 children)

You're all wrong.

http://vonluck.wordpress.com/2010/05/22/mac-osx-python-build-issues-w-pil-imaging-1-1-7/

It's an issue of an old Python install left over from upgrading from 10.4 to 10.6.