Apple Llvm 6.0 Error: Clang Failed with Exit Code -1

Apple LLVM 6.0 Error: clang failed with exit code -1

Hey I just ran into the same problem. Basically I deleted my tests target. I found this:

Errors When Compiling iOS 8, Xcode 6.0.1

Which basically says that:

Click on the name of your project on the list of files/folders on the
left in Xcode (at the very top of the list). Look at the "Targets"
section on the left-hand side of the window to the right. Likely,
there's two listed with the second being a "test" item. Right-click on
that item and select "delete". Then try to run the project again. See
screenshot below for a visual cue.

And a picture to help you out:

Hope this helps!

EDIT: Also in the tests target, I actually found that I didn't necessarily need to delete it, there was a broken path, just fixing it makes it all work again.

Apple LLVM 6.0 Error

Ther is one way!

Select Targets/Build Settings/ Scroll to Apple LLVM 6.0 - Preprocessing

-> ENABLE FOUNDATION ASSERTIONS set it to NO

Apple LLVM 6.0 Error After Changing Architectures

I was trying to compile ARM code as if it were ARM64. Since it's just an app and not an extension, I don't need to do that. So, under Project>Target>Build Settings> Architectures I changed the Architectures key I standard architectures, and the Valid Architectures key to armv7.

Apple LLVM 6.0 Error Clang 254

You can follow this example to solve this issue. It worked for me. You have to delete the derived data and the restart xCode. It always work with Apple LLVM 6.0 Error.

Xcode build error clang failed

It looks like you have a stray - in an Header Search Paths setting in your xCode project.

Unfortunately, there isn't a particularly easy way to find this except for looking through the document using the project viewer (you could edit it with a text editor, but that could worsen the problem).

Basically, select the project document in the Project Navigator (left pane) and then look through the project's Build Settings, and then the Build Settings for each target in turn, looking for the Header Search Paths setting and anywhere it shows up as bold, you will want to double-click and make sure there isn't a single - (or a - followed by a space or comma, which could be parsed as a single argument).

If you don't locate it this way, you may have a build setting that is resolving to -, so look at the bottom of the Build Settings and make sure there isn't a User-Defined variable that is set to - (or - or -,).

---

Related Topics