On Jan 29, 2014, at 2:33 AM, Felix Winkelmann <[email protected]> wrote:
> From: ".alyn.post." <[email protected]> >> I agree with Jim here. I don't use Xcode, but need gcc/clang for brew, >> chicken, &c. I benefit from this project: >> http://kennethreitz.org/xcode-gcc-and-homebrew/, which provides gcc >> and associated darwin libraries on the command-line. My gcc is in >> /usr/bin, which got that way installing brew, for which I assume I >> did something similar to/identical to the instructions upthread. >> >> So I have a proper compiler in /usr/bin, and I'd like chicken to >> continue to use it. > > You are free to do so, by overriding the appropriate build-variables. Yet, why > shouldn't the default build play it safe? Well, no one else appears to be having any issues right now, so I would argue using /usr/bin/gcc is playing it safe. I would also argue that hardcoding paths into the XCode directories is a fringe use case. So, please explain exactly what problem you are having, along with your OS version and XCode version. Jim _______________________________________________ Chicken-hackers mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/chicken-hackers
