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: Jim Ursetto
Subject: Re: [Chicken-hackers] [PATCH] fix Mac OS X build
Date: Tue, 28 Jan 2014 14:33:30 -0600

Do you know if there is ever a case where the tools are not installed in 
/usr/bin at all, but are available under /Applications/XCode.app?    As far as 
I can remember, whenever I have installed the command-line tools (using the 
dialogue box, or the installer inside XCode) binaries are immediately available 
under /usr/bin.  However, it sounds like Felix is having an issue where 
/usr/bin is not populated, but the tools are available in their expected place 
in /Applications/XCode.app.  I do not recall experiencing this.

Jim

On Jan 28, 2014, at 2:21 PM, richo <address@hidden> wrote:

> On 28/01/14 13:58 -0600, Jim Ursetto wrote:
>> On Jan 28, 2014, at 1:53 PM, Felix Winkelmann <address@hidden> wrote:
>> 
>>> From: Jim Ursetto <address@hidden>
>>> Subject: Re: [Chicken-hackers] [PATCH] fix Mac OS X build
>>> Date: Tue, 28 Jan 2014 13:10:53 -0600
>>> 
>>>> Do you mean, why isn't it in the README for Chicken?
>>> 
>>> Yes, that's what I meant.
>>> 
>>> I think it is a recent change, prior to XCode 5 AFAIK the shims were always 
>>> installed in /usr/bin automatically.
>>> 
>>> Not in Xcode4, as I'm quite sure, since I had quite some trouble figuring 
>>> out the
>>> correct locations.
>> 
>> That is possible.  I never had to do anything special with XCode 4 as far as 
>> I remember; the binaries were always in /usr/bin.
>> 
> 
> As of Mavericks, /usr/bin/{clang,gcc,git,...} is a shim that invokes xcrun 
> (which
> is responsible for looking up the tools you've selected with xcode-select),
> but also for bringing up a "Would you like to install dev tools" if you don't
> already have them.
> 
> The upshot is that getting the dev tools installed is pretty painless, the
> downside is that any check along the lines of "which ${tool}" will give you
> false positives, and better, trying to invoke the tools in an automated
> fashion will burst into flames because it'll bring up a dialogue if there's a
> windowserver attached and then block forever.
> 
> richo
> 
> -- 
> richo || Today's excuse:
> 
> Terrorists crashed an airplane into the server room, have to remove
> /bin/laden. (rm -rf /bin/laden)
> http://blog.psych0tik.net
> _______________________________________________
> Chicken-hackers mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/chicken-hackers




reply via email to

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