chicken-hackers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Chicken-hackers] [PATCH] fix Mac OS X build


From: Felix Winkelmann
Subject: Re: [Chicken-hackers] [PATCH] fix Mac OS X build
Date: Wed, 29 Jan 2014 09:32:08 +0100 (CET)

From: Jim Ursetto <address@hidden>
Subject: Re: [Chicken-hackers] [PATCH] fix Mac OS X build
Date: Tue, 28 Jan 2014 16:14:16 -0600

> On Jan 28, 2014, at 3:56 PM, Felix Winkelmann <address@hidden> wrote:
> 
>>> 
>>> I don't see why not.  chicken should be using /usr/bin as its binary 
>>> directory, and so when xcode-select changes the install location, it will 
>>> still work.   (I think the shims just look up the actual XCode location and 
>>> then exec() it -- they're not symlinks nor are they physically updated in 
>>> place, AFAIK.)  Am I missing something?
>> 
>> If I compile the base chicken system using toolchain/xcode-version A
>> with the c-compiler in some default location, xcode-select to another
>> toolchain/xcode-version and then install an egg using the base chicken
>> system, that calls whatever c-compiler is currently in /usr/bin, then
>> we surely might get into trouble regarding binary-compatibility or
>> c-compiler version differences, ABIs, or whatnot, right?
> 
> I guess so, but I don't see how it's any different than upgrading XCode in 
> place, or even upgrading the gcc binary on any old system.

That is a deliberate decision by the user, with all that implies.

>  I don't think you should habitually be running xcode-select to switch 
> toolchains, anyway. 

Neither do I, but how to prevent it?

> I still don't see the problem with just using /usr/bin/gcc like every other 
> UNIX program on the Mac, unless you've actually had a problem with this, 
> which is possible as you've done a lot of work on iOS lately.

No, because I don't use xcode-select.


felix



reply via email to

[Prev in Thread] Current Thread [Next in Thread]