mit-scheme does not build on OS X 10.8

[AlonzoQuixote@…]

Attempt to install mit-scheme on OS X 10.8 mountain lion (x86_64, Xcode 4.4) fails on configure.

...
:info:build checking for native-code support... yes, using portable C code
:info:build configure: error: No MacOSX SDK for version: 10.8
...

Log file attached. A recent, earlier SDK issue was fixed for this port here: r90606

[ryandesign (Ryan Carsten Schmidt)]

It's building fine for me. Have you remembered to use xcode-select?

[AlonzoQuixote@…]

The problem does not seem to be xcode-select.

~> xcode-select -print-path
/Applications/Xcode.app/Contents/Developer

The mit-scheme port worked fine on this machine last week, before upgrade to 10.8, and many other ports have re-installed after the upgrade with no problem.

[drkp (Dan Ports)]

I don't have access to 10.8 at the moment, so may not be much help. Is the 10.8 SDK available in /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.8.sdk?

[AlonzoQuixote@…]

After adding the following link, a "port clean mit-scheme" and "port install mit-scheme" succeeded:

ln -s /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs /Developer/Platforms/MacOSX.platform/Developer

However, on another newer machine (macbook pro retina, but with same OS 10.8 and Xcode 4.4) the install works without the link. The newer machine has no /Developer directory. So maybe a fix would be to patch the configure script so that it looks in /Applications, more specifically in

/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs

if

/Developer/Platforms/MacOSX.platform/Developer/SDKs/${SDK}.sdk

fails?

[drkp (Dan Ports)]

Hmm, that's exactly what the post-patch script is supposed to be doing.

Do you have developer_dir set in /opt/local/etc/macports/macports.conf? It should be commented out to let MacPorts pick the proper path automatically, but older installations may still have it hardcoded to /Developer

[ralph@…]

Replying to dports@…:

Do you have developer_dir set in /opt/local/etc/macports/macports.conf? It should be commented out to let MacPorts pick the proper path automatically, but older installations may still have it hardcoded to /Developer

This fixed the problem for me.