Re: clang-llvm: Tracking core OS crashes (Found! It's the 10.4 SDK)
Re: clang-llvm: Tracking core OS crashes (Found! It's the 10.4 SDK)
- Subject: Re: clang-llvm: Tracking core OS crashes (Found! It's the 10.4 SDK)
- From: Jean-Daniel Dupas <email@hidden>
- Date: Thu, 10 Sep 2009 15:02:06 +0200
Le 10 sept. 2009 à 14:48, Brian Barnes a écrit :
Rich Siegel wrote:
On 9/9/09 at 11:10 PM, email@hidden (Brian Barnes) wrote:
Apple guys/gals -- here's where the problem lays. It's the 10.4
SDK.
clang-llvm on 10.5, compiles without a problem, runs fine
clang-llvm on 10.4, crashes in OS routines (usually interface
routines)
I'm pretty certain that 10.4 is not a supported deployment target
for binaries built with clang, although I can't find mention as
such in the 3.2 release notes.
Anybody at Apple want to verify this? It *mostly* works -- there's
only a small subset of things that crash that I've detected -- and
I'm not exactly sure what the differences would be between the
10.4/10.5 SDK that wouldn't allow this work (i.e., bevel buttons are
still supported, carbon hasn't changed much in years, etc). My
attempted targets are:
ppc = sdk 10.4, gcc 4.0
i386 = dsk 10.4, clang-llvm
I *suspect* the problem isn't in clang, but instead in llvm/10.4.
If I can't use it with 10.4, that will be disappointing, but not the
end of the world. Everything I've read I'd love to be able to move
to clang/llvm, it's much faster (clang) and eliminates the old days
of figuring out the best scheduling, compiler settings, etc (llvm).
Since clang/llvm is relatively new (compared to gcc) -- what's going
to be the upgrade cycle on this? A nightly build like webkit might
be nice (as I've encountered a number of bugs.) Again, if I have to
wait for major releases, not a big deal, just wondering.
I'm working with a daily build for some times, and it works well.
There is no binary distribution, but a "make update && make clang-
only" is enough to build it.
http://clang.llvm.org/get_started.html
If you want to replace the Xcode clang binary, you have to replace:
/Developer/usr/bin/clang
/Developer/usr/libexec/clang-cc
/Developer/usr/lib/clang/
I replaced them by symlinks that point on the output of my llvm/clang
build dir so I don't have to replace them each time I rebuild clang.
I'm not sure this is officially supported, but as the 'clang'
interface is stable (no major changes in the arguments), I didn't
encounter any issue yet.
_______________________________________________
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