How to fix faulty symlink in XCode 3.2.6, issue 14018?

[Ryan Schmidt]

On Jun 19, 2015, at 10:24 PM, semaphore45 at yahoo.com wrote:

> I am trying to solve the issue described there http://bugs.python.org/issue14018, which prevents me from installing gqrx. The problem is I don't understand how the solution should be implemented. It states:
>> The Xcode installer creates faulty symlinks to /Library within  /Developer/SDKs.
> I assume /Library is the wrong target.
> 
> But the example shows:
>> $ cd /Developer/SDKs/MacOSX10.6.sdk/Library
>> $ ls -l
>> total 8
>> lrwxr-xr-x  1 root  wheel  19 Mar 17 18:24 Frameworks@ -> 
>> /Library/Frameworks
>> 
> Where /Library/Frameworks is not /Library, obviously. The symlink I see on my config shows exactly that, no link to /Library but only to /Library/Framework.
> 
> Then I read 
>> The solution is to manually go in and fix the symlinks in 
>> /Developer/SDKs/MacOSX10.6.sdk
>> 
> But how should I correct that? Removing the second recursive alias "Frameworks" redirecting to /Library/Frameworks?
> 
> I assume my logic is failing me. 
> What is the correct target for /Developer/SDKs/MacOSX10.6.sdk/Library/Frameworks?

I just installed a fresh copy of Xcode 3.2.6 on Snow Leopard, and can confirm there is a problem with the Mac OS X 10.6 SDK's Frameworks, which is that /Developer/SDKs/MacOSX10.6.sdk/Library/Frameworks is a directory, and it contains a symlink Frameworks pointing to /Library/Frameworks. In other words, /Developer/SDKs/MacOSX10.6.sdk/Library/Frameworks/Frameworks points to /Library/Frameworks, when instead it is /Developer/SDKs/MacOSX10.6.sdk/Library/Frameworks that should point to /Library/Frameworks. If you look at the MacOSX10.5.sdk, it is already set up that way.

The solution would be to delete the directory /Developer/SDKs/MacOSX10.6.sdk/Library/Frameworks and then create /Developer/SDKs/MacOSX10.6.sdk/Library/Frameworks as a symlink pointing to /Library/Frameworks.

Inside /Developer/SDKs/MacOSX10.6.sdk/Library/Frameworks there is also a directory PluginManager.framework, but it only contains two header files, and they are identical to the headers already in /Library/Frameworks/PluginManager.framework on my system, so there should be no problem deleting this from the SDK.

So these commands would set things right:

sudo rm -f /Developer/SDKs/MacOSX10.6.sdk/Library/Frameworks/Frameworks
sudo rm -rf /Developer/SDKs/MacOSX10.6.sdk/Library/Frameworks/PluginManager.framework
sudo rmdir /Developer/SDKs/MacOSX10.6.sdk/Library/Frameworks
sudo ln -s /Library/Frameworks /Developer/SDKs/MacOSX10.6.sdk/Library/Frameworks

The faulty Frameworks setup in Xcode 3.2.6's Mac OS X 10.6 SDK should not be of any significance for MacPorts, because MacPorts ports don't typically use anything in /Library/Frameworks, but I have not tested the gqrx port specifically; perhaps it is an exception. I'll try to install it now.