[Openmcl-devel] Incompatibility with Xcode 4?

[Gary Byers]

Thanks for looking at this.

I had just checked in changes to the Makefiles that approach the problem
a different way (by setting SDKROOT to /) and leaving OSVERSION at 10.5.

The header files and libraries that're installed in / (in /usr/include,
/usr/lib, etc.) generally correspond to those installed in the most
recent SDK directory in the XCode tree (usually rooted at /Developer)
and also generally describe the host OS version.  As long as that's
10.5 or later, the setting of OSVERSION should set options that keep
the lisp kernel from using post-10.5 features (sort of ...) and the
resulting binary will run on 10.5, even if the kernel is built on a
system that doesn't have 10.5-specific headers installed (like XCode4).
Being able to run on 10.5 is still desirable.

At some point, we'll likely have to drop 10.5 support: it'll get too
hard to maintain and be too irrelevant.  I don't think that the fact
that XCode4 doesn't distribute a 10.5-specific SDK is a good reason
to drop that support now.

On Wed, 16 Mar 2011, Raymond Wiker wrote:

>
> On Mar 16, 2011, at 20:08 , Raymond Wiker wrote:
>
>> Raymond Wiker <rwiker <at> gmail.com> writes:
>>
>>> I just tried (rebuild-ccl :full t) (i.e, no SVN update), and that
>>> failed. I then tried (rebuild-ccl :full t :update t); that, too,
>>> failed.
>>>
>>> I think I've seen this discussed on this mailing list earlier, so I'll
>>> take another look at the archives.
>>
>> I've now taken a look at the archives, found the hint to change
>> the Makefile(s), made the changes and rebuilt both the 32-
>> and 64-bit versions. Worked like a charm.
>>
>> I have a feeling that it should be possible to make the Makefile
>> choose the correct version, depending on what's actually
>> available... I'll see if I can come up with a patch.
>
> The attached patch appears to work...