[Python-Dev] python build failed on mac (original) (raw)

Vijay Majagaonkar vijaymajagaonkar at gmail.com
Sat Jan 21 21:24:00 CET 2012

On 2012-01-21, at 1:57 PM, Hynek Schlawack wrote:

Am Freitag, 20. Januar 2012 um 23:40 schrieb Vijay Majagaonkar:

I am trying to build python 3 on mac and build failing with following error can somebody help me with this

It is a known bug that Apple's latest gcc-llvm (that comes with Xcode 4.1 by default as gcc) miscompiles Python: http://bugs.python.org/issue13241 make clean CC=clang ./configure && make -s Thanks for the help, but above command need to run in different way ./configure CC=clang make I'm not sure why you think it "needs" to be that way, but it's fine by me as both ways work fine.

I am not sure, that was just try and worked for me, with first option suggested by you was throwing same compile error then I tried with this that worked :)

this allowed me to build the code but when ran test I got following error message

[363/364/3] testio python.exe(11411) malloc: *** mmap(size=9223372036854775808) failed (error code=12) *** error: can't allocate region *** set a breakpoint in mallocerrorbreak to debug python.exe(11411,0x7fff7a8ba960) malloc: *** mmap(size=9223372036854775808) failed (error code=12) *** error: can't allocate region *** set a breakpoint in mallocerrorbreak to debug python.exe(11411,0x7fff7a8ba960) malloc: *** mmap(size=9223372036854775808) failed (error code=12) *** error: can't allocate region *** set a breakpoint in mallocerrorbreak to debug I am using Mac OS-X 10.7.2 and insatlled Xcode 4.2.1 Please ensure there aren't any gcc-created objects left by running "make distclean" first.

I have tried this option too but still result is same, I have attached test result if that will helps
-------------- next part -------------- A non-text attachment was scrubbed... Name: mac_test.log Type: application/octet-stream Size: 3051915 bytes Desc: not available URL: <http://mail.python.org/pipermail/python-dev/attachments/20120121/9fdf4af0/attachment-0001.obj> -------------- next part -------------- and I will like to work on this if you give me some guideline to look into this issue

Thanks for the help ;)

More information about the Python-Dev mailing list