Where to report this clang issue?
Where to report this clang issue?
- Subject: Where to report this clang issue?
- From: Matt Neuburg <email@hidden>
- Date: Thu, 13 Feb 2014 11:52:57 -0800
Xcode 5.1 beta has introduced some clang problems and I'm wondering where/how you think I ought to report them. What's happened is that clang "unknown argument" errors are now appearing. My impression is that these used to be ignored silently. See, for example, here:
http://clang-developers.42468.n3.nabble.com/error-unknown-argument-ffoo-gt-reason-td4037260.html
The way this manifested for me was when I did
$ sudo gem install rmagick
and it failed to build:
https://github.com/rmagick/rmagick/issues/96
As you can see, I eventually solved it by reverting to the clang contained in Xcode 5.0.2.
That actually happened as part of a different issue where I couldn't build TextMate from source:
http://lists.macromates.com/textmate/2014-February/037093.html
Again, reverting to the clang in Xcode 5.0.2 solved it (and thus I was able to build TextMate, which is just awesome).
So what I'm left with is a desire to beg the clang developers to stop and go back, as the new version is breaking all kinds of stuff. How should I do that? I assume this is not directly an Xcode problem so the proper authority would not be Apple, but I'm unclear on the details. Thanks for any ideas - m.
--
matt neuburg, phd = email@hidden, http://www.apeth.net/matt/
pantes anthropoi tou eidenai oregontai phusei
Programming iOS 7! http://shop.oreilly.com/product/0636920031017.do
iOS 7 Fundamentals! http://shop.oreilly.com/product/0636920032465.do
RubyFrontier! http://www.apeth.com/RubyFrontierDocs/default.html
TidBITS, Mac news and reviews since 1990, http://www.tidbits.com
_______________________________________________
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