Re: clang failed with exit code 250
Re: clang failed with exit code 250
- Subject: Re: clang failed with exit code 250
- From: "Sean McBride" <email@hidden>
- Date: Mon, 5 Jul 2010 13:57:15 -0400
- Organization: Rogue Research Inc.
On Thu, 1 Jul 2010 13:57:43 -0400, Paul Summermatter said:
>Jean-Daniel et al,
>
> Thank you very much for the information. So, I guess I wasn't thinking
>about this correctly. I was assuming I should submit a bug to Apple,
>but do they actually own/maintain their own clang or should I be
>submitting a bug to the University of Illinois clang mailing list
>(assuming that this bug isn't already fixed in a new version)?
I'd suggest filing it here:
<http://llvm.org/bugs>
It's a much more pleasant and transparent experience than Apple's Radar.
> Also, you talk about LLVM 2.7. I don't see a straight llvm executable
>in Developer/usr/bin (lots of llvm executables related to gcc4.2 and
>such), and, as clang is a separate project from LLVM, I'm not sure what
>happens if I mix and match versions, meaning I wonder if I can upgrade
>just clang and leave llvm as is.
You can use this technique to use the newest clang with Xcode:
<http://shapeof.com/archives/2010/01/using_the_latest_llvm_with_xcode.html>
> For now, I think I'm going to punt and just continue using GCC, but I
>may get daring at some point and play with this a bit more.
That's probably best. clang is somewhat bleeding edge, but promises to
be great!
--
____________________________________________________________
Sean McBride, B. Eng email@hidden
Rogue Research www.rogue-research.com
Mac Software Developer Montréal, Québec, Canada
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden