Opened 18 months ago

Last modified 18 months ago

#53173 new defect

py-pyobjc: fails to build on 10.6, uses 10.7 SDK; stdarg.h: No such file or directory

Reported by: mojca (Mojca Miklavec) Owned by:
Priority: Normal Milestone:
Component: ports Version:
Keywords: snowleopard Cc: ryandesign (Ryan Schmidt)
Port: py-pyobjc


It looks suspicious that the build is trying to use the 10.7 SDK:

/usr/bin/gcc-4.2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -arch i386 -I/opt/local/Library/Frameworks/Python.framework/Versions/3.6/include/python3.6m -c Modules/objc/OC_NSBundleHack.m -o build/temp.macosx-10.6-i386-3.6/Modules/objc/OC_NSBundleHack.o -DPyObjC_STRICT_DEBUGGING -DMACOSX -DPyObjC_BUILD_RELEASE=1006 -DMACOSX -g -fexceptions -Wall -Wstrict-prototypes -Wmissing-prototypes -Wformat=2 -W -Wpointer-arith -Wmissing-declarations -Wnested-externs -W -Wno-import -Wno-unknown-pragmas -Wshorten-64-to-32 -Ilibffi-src/include -Ilibffi-src/powerpc -isysroot /Developer/SDKs/MacOSX10.7.sdk
In file included from /opt/local/Library/Frameworks/Python.framework/Versions/3.6/include/python3.6m/Python.h:75,
                 from Modules/objc/pyobjc.h:11,
                 from Modules/objc/OC_NSBundleHack.m:1:
/opt/local/Library/Frameworks/Python.framework/Versions/3.6/include/python3.6m/bytearrayobject.h:9:20: error: stdarg.h: No such file or directory

Here's the full log.

Change History (2)

comment:1 Changed 18 months ago by ryandesign (Ryan Schmidt)

You are right that it is unexpected that the pyobjc build is trying to use the 10.7 SDK. I don't know if that's the cause of the problem, however.

The 10.6 buildbot machines do have the 10.7 SDK installed, because that was the only way to build libsdl2.

The pyobjc file runs /usr/bin/xcodebuild -version -sdk macosx Path to determine what SDK to use. On the 10.6 buildbot machines, this returns /Developer/SDKs/MacOSX10.7.sdk, presumably because it is the newest installed SDK.

comment:2 Changed 18 months ago by mojca (Mojca Miklavec)

Ah, that explains why I constantly get 10.(n+1) on my computer as well.

/usr/bin/xcodebuild -version -sdk macosx Path

returns the newer SDK for me as well.

I was looking at some links like which tend to suggest a broken installation of the toolchain.

Note: See TracTickets for help on using tickets.