CMake warning wrt frameworks during configure phase on Snow Leopard

Jeremy Lavergne jeremy at lavergne.gotdns.org
Wed Sep 25 14:39:54 PDT 2013


I'd look for the existing symlinks and see what's going on (perhaps use `find` and set type to link and exec ls -l {} \;). You can see where they point and why they're wrong, if not highlighted already in the bug report.

To recreate a symlink,  you remove the existing source (source points to destination) then symlink it again. For example:
`ls -l /something/path` would show -> /other/path
`rm /something/path`
`ln -s /something/path /other/path`

I also found it strange the printed path had a double slash going on.

On Sep 25, 2013, at 5:28 PM, MK-MacPorts at techno.ms wrote:

> Just by accident I've found on my Snow Leopard this warning in the log file of one of my ports:
> ---
> .
> .
> .
> :info:configure -- The C compiler identification is GNU 4.2.1
> :info:configure -- The CXX compiler identification is GNU 4.2.1
> :info:configure CMake Warning at /opt/macports-test/share/cmake-2.8/Modules/Platform/Darwin.cmake:290 (message):
> :info:configure   The SDK Library/Frameworks path
> :info:configure
> :info:configure    //Library/Frameworks
> :info:configure
> :info:configure   is not set up correctly on this system.  This is known to occur when
> :info:configure   installing Xcode 3.2.6:
> :info:configure
> :info:configure    http://bugs.python.org/issue14018
> :info:configure
> :info:configure   The problem may cause build errors that report missing system frameworks.
> :info:configure   Fix your SDK symlinks to resolve this issue and avoid this warning.
> :info:configure Call Stack (most recent call first):
> :info:configure   /opt/macports-test/share/cmake-2.8/Modules/CMakeSystemSpecificInformation.cmake:36 (include)
> :info:configure   CMakeLists.txt:2 (PROJECT)
> :info:configure
> :info:configure
> :info:configure -- Checking whether C compiler has -isysroot
> :info:configure -- Checking whether C compiler has -isysroot - yes
> .
> .
> .
> ---
> Apart from this the port builds fine.
> 
> The suggested fix in http://bugs.python.org/issue14018 is "to manually fix the symlinks in /Developer/SDKs/MacOSX10.6.sdk …" !
> 
> Hmmm… I don't know what and how to fix this.
> 
> Any ideas?



More information about the macports-dev mailing list