|
From: Hanspeter N. <fi...@sn...> - 2020-06-07 10:26:32
|
On 6/7/20 5:13 AM, Luigi Ernesto Zanotti wrote: > On 06/06/2020 21:38, Zhu, Jianxin wrote: >> Dear Hanspeter, >> >> Indeed you are right. On my system, I have >> a MacOSX10.14.sdk not linked to MacOSX.sdk (itself linked to >> MacOSX10.15.sdk) >> inside /Library/Developer/CommandLineTools/SDKs. >> >> I have now moved the standalone MacOSX10.14.sdk to >> MacOSX10.14.sdk_orig and made a symbolic link >> sudo ln -sf MacOSX.sdk MacOSX10.14.sdk >> >> With this correction, I can build python27 like a charm. Maybe Luigi >> can do the same. >> By getting over this, I am now also able to complete the fink update-all. >> >> Thank you so much for the help. >> >> Best, >> >> Jianxin >> >> >> On 6/6/20, 12:37 PM, "Hanspeter Niederstrasser" >> <fi...@sn...> wrote: >> >> We all have the same exact compiler command on 10.14/xcode11.3.1 >> > gcc -fno-strict-aliasing -Wno-nullability-completeness -DNDEBUG >> -g -fwrapv -fwrapv -O3 -Wall -Wstrict-prototypes -I. -IInclude >> -I./Include -I/sw/include -I/sw/include/ncursesw >> -I/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk/usr/include >> -I/sw/src/fink.build/python27-2.7.18-2/Python-2.7.18/Include >> -I/sw/src/fink.build/python27-2.7.18-2/Python-2.7.18 -c >> ./Mac/Modules/_scproxy.c -o >> build/temp.macosx-10.14-x86_64-2.7/./Mac/Modules/_scproxy.o >> >> that references the SDK-10.15 from Xcode.app. My working python >> build >> has a warning for _scproxy.c about a header in the unversioned >> SDK from >> Xcode.app: >> >> >> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/SystemConfiguration.framework/Headers/SCSchemaDefinitions.h >> >> >> But error for Jianxin and Luigi refer to the similar header file >> from >> the SDK-10.14 from the command line tools: >> >> >> /Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/System/Library/Frameworks/SystemConfiguration.framework/Headers/SCSchemaDefinitions.h >> >> >> And the actual error when compiling _scproxy.o immediatel above the >> warning says the __OSX_AVAILABLE_BUT_DEPRECATED_MSG error is in >> >> >> /Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/System/Library/Frameworks/Security.framework/Headers/CMSDecoder.h >> >> >> What's the output of the following (one line) command: >> >> /bin/ls -Fl /Library/Developer/CommandLineTools/SDKs >> >> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs >> >> >> I get the following: >> ``` >> >> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs: >> >> total 0 >> drwxr-xr-x 4 nieder staff 128 Nov 7 2019 DriverKit19.0.sdk/ >> drwxr-xr-x 8 nieder staff 256 Nov 7 2019 MacOSX.sdk/ >> lrwxr-xr-x 1 nieder staff 10 Apr 6 05:59 MacOSX10.15.sdk@ -> >> MacOSX.sdk >> >> /Library/Developer/CommandLineTools/SDKs: >> total 0 >> lrwxr-xr-x 1 root wheel 15 Apr 6 06:23 MacOSX.sdk@ -> >> MacOSX10.15.sdk >> lrwxr-xr-x 1 root wheel 10 Jul 23 2019 MacOSX10.14.sdk@ -> >> MacOSX.sdk >> drwxr-xr-x 8 root wheel 256 Apr 6 06:24 MacOSX10.15.sdk/ >> ``` >> >> I'm thinking there's a different symlink in one of your two SDK >> locations. >> >> Hanspeter >> >> > I followed the solution proposed by Jianxin, and it worked fine! > After that I guessed which was the difference wit the MacbookAir > installation, where /python27_2.7.18-1 (one) smoothly built on May, 6. > Here are the outputs for iMac AFTER the symlink and MacbookAir: > iMac: > /Library/Developer/CommandLineTools/SDKs: > total 0 > lrwxr-xr-x 1 root wheel 15 23 Feb 12:55 MacOSX.sdk@ -> MacOSX10.15.sdk > drwxr-xr-x 7 root wheel 224 5 Jan 15:19 MacOSX.sdk 1/ > lrwxr-xr-x 1 root wheel 10 7 Jun 11:30 MacOSX10.14.sdk@ -> MacOSX.sdk > drwxr-xr-x 7 root wheel 224 23 Feb 12:57 MacOSX10.14_orig.sdk/ > drwxr-xr-x 8 root wheel 256 23 Feb 12:58 MacOSX10.15.sdk/ > > MacbookAir: > /Library/Developer/CommandLineTools/SDKs: > total 0 > lrwxr-xr-x 1 root wheel 15 23 Feb 18:44 MacOSX.sdk@ -> MacOSX10.15.sdk > drwxr-xr-x 7 root wheel 224 9 Dec 14:42 MacOSX.sdk 1/ > lrwxr-xr-x 1 root wheel 10 12 Oct 2019 MacOSX10.14.sdk@ -> MacOSX.sdk > drwxr-xr-x 8 root wheel 256 23 Feb 18:46 MacOSX10.15.sdk/ > > For some reason (mysterious for me) the two sdk installations didn't > proceed along the same path, even if I always tried to keep Fink > installations to proceed in parallel each other! > Last question: should I keep MacOSX10.14_orig.sdk or remove it? > Thanks so much for Hanspeter and Jianxin help. Cheers, I would guess it's OK to get rid of the real directory MacOSX10.14_orig.sdk and keep only the 10.14 symlink. With Xcode11.3.1, it seems that the SDK that's supposed to be getting used is the 10.15 SDK and 10.14 is just a convenience symlink. Hanspeter |