Warning on OS X 10.7.5, XCode Version 4.5.2 (4G2008a)

[ssteinerx]

XCode Version 4.5.2 (4G2008a) includes the following gcc, so I'm not sure exactly why it thinks it can't use this one and has to fallback to "clang":

gcc --version

i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.1.00)
Copyright (C) 2007 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

pip install greenlet

Downloading/unpacking greenlet
Downloading greenlet-0.4.0.zip (72kB): 72kB downloaded
Running setup.py egg_info for package greenlet

Installing collected packages: greenlet
Running setup.py install for greenlet
gcc-4.2 not found, using clang instead
building 'greenlet' extension
clang -fno-strict-aliasing -fno-common -dynamic -g -O2 -DNDEBUG -g -O3 -arch x86_64 -I/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7 -c greenlet.c -o build/temp.macosx-10.6-x86_64-2.7/greenlet.o
greenlet.c:650:3: warning: array index of '1' indexes past the end of an array (that contains 1 elements) [-Warray-bounds]
PyTuple_SET_ITEM(tuple, 1, kwargs);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/tupleobject.h:54:37: note: instantiated from:
#define PyTuple_SET_ITEM(op, i, v) (((PyTupleObject *)(op))->ob_item[i] = v)
^
/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/tupleobject.h:26:5: note: array 'ob_item' declared here
PyObject *ob_item[1];
^
1 warning generated.
clang -bundle -undefined dynamic_lookup -g -arch x86_64 build/temp.macosx-10.6-x86_64-2.7/greenlet.o -o build/lib.macosx-10.6-x86_64-2.7/greenlet.so
Linking /Users/ssteiner/.virtualenvs/1/build/greenlet/build/lib.macosx-10.6-x86_64-2.7/greenlet.so to /Users/ssteiner/.virtualenvs/1/build/greenlet/greenlet.so

Successfully installed greenlet
Cleaning up...

[snaury]

I don't think this warning has anything to do with greenlet. You should report it to Python and/or Apple.

[ssteinerx]

Is it possible that the GCC version specification in the build files is too specific i.e. only 4.2 and doesn't automatically use 4.2.1 even though it's in the same series?

On Nov 18, 2012, at 9:56 AM, Alexey Borzenkov wrote:

I don't think this warning has anything to do with greenlet. You should report it to Python and/or Apple.

—
Reply to this email directly or view it on GitHub.

[snaury]

@ssteinerx I just checked on my MacBook Air (OS X 10.7.5) which has Xcode 4.3.3 (haven't updated in a while), and python setup.py build_ext uses llvm-gcc-4.2, so your guess is as good as mine what's wrong with Xcode 4.5. Greenlet uses setuptools/distutils to build the extension, and it's Python's job to build extensions properly, and it usually uses whatever it itself was built with.

Besides, where does this message "gcc-4.2 not found, using clang instead" is even coming from? I can't seem to find it in Python 2.7's distutils/stdlib on OS X, neither it is in latest versions of distribute or pip. In any case this is not an issue with greenlet, this is an issue with Python's tuple APIs with clang, so please contact Apple and ask them what they broke this time. :)

[snaury]

@ssteinerx I updated to Xcode 4.5.2, no warnings, pip install greenlet uses llvm-gcc-4.2. Are you sure you have Command Line Tools (Preferences -> Downloads -> Components) installed?

[ssteinerx]

Just upgraded to 4.5.2 from 4.5.1 and this is what I get, not sure why, command line tools are definitely installed and GCC is the right version...

(~)# pip install --upgrade greenlet
Downloading/unpacking greenlet
Downloading greenlet-0.4.0.zip (72kB): 72kB downloaded
Running setup.py egg_info for package greenlet

Installing collected packages: greenlet
Running setup.py install for greenlet
gcc-4.2 not found, using clang instead
building 'greenlet' extension
clang -fno-strict-aliasing -fno-common -dynamic -isysroot /Developer/SDKs/MacOSX10.6.sdk -g -O2 -DNDEBUG -g -O3 -arch x86_64 -I/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7 -c greenlet.c -o build/temp.macosx-10.6-x86_64-2.7/greenlet.o
clang -bundle -undefined dynamic_lookup -isysroot /Developer/SDKs/MacOSX10.6.sdk -isysroot /Developer/SDKs/MacOSX10.6.sdk -g -arch x86_64 build/temp.macosx-10.6-x86_64-2.7/greenlet.o -o build/lib.macosx-10.6-x86_64-2.7/greenlet.so
Linking /private/var/folders/22/mfscv0n153v5yny3hgrx5h340000gn/T/pip-build/greenlet/build/lib.macosx-10.6-x86_64-2.7/greenlet.so to /private/var/folders/22/mfscv0n153v5yny3hgrx5h340000gn/T/pip-build/greenlet/greenlet.so

Successfully installed greenlet
Cleaning up...

()# gcc -v
Using built-in specs.
Target: i686-apple-darwin11
Configured with: /private/var/tmp/llvmgcc42/llvmgcc42-2336.1167/src/configure --disable-checking --enable-werror --prefix=/Applications/Xcode.app/Contents/Developer/usr/llvm-gcc-4.2 --mandir=/share/man --enable-languages=c,objc,c++,obj-c++ --program-prefix=llvm- --program-transform-name=/^[cg][^.-]*$/s/$/-4.2/ --with-slibdir=/usr/lib --build=i686-apple-darwin11 --enable-llvm=/private/var/tmp/llvmgcc42/llvmgcc42-2336.11~67/dst-llvmCore/Developer/usr/local --program-prefix=i686-apple-darwin11- --host=x86_64-apple-darwin11 --target=i686-apple-darwin11 --with-gxx-include-dir=/usr/include/c++/4.2.1
Thread model: posix
gcc version 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.11.00)

Thanks,

S

On Dec 7, 2012, at 4:05 PM, Alexey Borzenkov wrote:

@ssteinerx I updated to Xcode 4.5.2, no warnings, pip install greenlet uses llvm-gcc-4.2. Are you sure you have Command Line Tools (Preferences -> Downloads -> Components) installed?

—
Reply to this email directly or view it on GitHub.

[snaury]

@ssteinerx Are you using some custom built Python (from macports or built yourself) by any chance? I found http://bugs.python.org/issue13590 bug report, and it has a link to http://hg.python.org/cpython/rev/688d48e434e4 change, which interestingly removes the very message you experience. And I can confirm that I have no such message anywhere in my /usr/lib/python2.7/distutils (Apple's Python, OS X 10.7.5). What does which python say?

[ssteinerx]

On Dec 7, 2012, at 5:09 PM, Alexey Borzenkov wrote:

@ssteinerx Are you using some custom built Python (from macports or built yourself) by any chance?

No. I'm on OS X 10.7.5 as well but I'm running the OS X 2.7.3 build installed from the Python.org site .dmg file.

(~)# which python
/Library/Frameworks/Python.framework/Versions/2.7/bin/python

I found http://bugs.python.org/issue13590 bug report, and it has a link to http://hg.python.org/cpython/rev/688d48e434e4 change, which interestingly removes the very message you experience. And I can confirm that I have no such message anywhere in my /usr/lib/python2.7/distutils (Apple's Python, OS X 10.7.5). What does which python say?

Those notes say:

As of Xcode 4.2, now standard for OS X 10.7 and optional for OS X 10.6, Apple no longer ships gcc-4.2 in Xcode, in favor of clang and the transitional llvm-gcc.

()# which gcc
/usr/bin/gcc
()# l /usr/bin/gcc*
lrwxr-xr-x 1 root wheel 12 Dec 7 16:21 /usr/bin/gcc -> llvm-gcc-4.2

[snaury]

@ssteinerx found it, macports python27 (versions 2.7.3_0 and 2.7.3_1) indeed have this very message. I just never experienced it since I only add macports to $PATH when I actually need it (too much breakage like this is possible otherwise), and stuff I need just symlinked to a directory in my $HOME. Apple's Python is 2.7.1, so it was probably introduced in upstream Python somewhere along the way.

[snaury]

@ssteinerx Huh? OS X 10.7.5 has no /Library/Frameworks/Python.framework! :) The actual OS X Python is in /System/Library/Frameworks/Python.framework. So you probably have some other Python installed somehow.

[ssteinerx]

Yes, I installed Python 2.7.3 from the Python.org official build.

S

On Dec 7, 2012, at 5:25 PM, Alexey Borzenkov wrote:

@ssteinerx Huh? OS X 10.7.5 has no /Library/Frameworks/Python.framework! :) The actual OS X Python is in /System/Library/Frameworks/Python.framework. So you probably have some other Python installed somehow.

—
Reply to this email directly or view it on GitHub.

[snaury]

@ssteinerx ah, sorry, missed that you have python.org build installed. Then that's the culprit, closing since it's upstream and greenlet cannot do anything about it.

[snaury]

Also, I just noticed that there's no warning about ob_item from clang anymore (not sure what has changed?), so there's basically no warnings of consequence anymore. For example, on macports Python is built with clang so it doesn't even warn about gcc-4.2 missing.

[ssteinerx]

On Dec 7, 2012, at 5:51 PM, Alexey Borzenkov wrote:

Also, I just noticed that there's no warning about ob_item from clang anymore (not sure what has changed?),

Maybe somebody #pragma'd it out of existence ;-).

so there's basically no warnings of consequence anymore. For example, on macports Python is built with clang so it doesn't even warn about gcc-4.2 missing.

No warnings? Ship it!

S