Apple LLVM 6.0 Error

Question

I recently downloaded and installed the XCode6-Beta and I am getting this build error. Steps already taken:

Double checked my prefix header file.
Cleaned project.
Restarted XCode.
Deleted DerivedData like 100 times!

Any thing I may be missing?

Command /Applications/Xcode6-Beta.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang failed with exit code 1

EDIT: Temporary Solution.

I removed the 6.0 support which was one of the areas causing problem however, if you need support for earlier versions this will still be an issue.

And what's the *actual* error? LLVM is not in itself an error. — The Paramagnetic Croissant, Jun 05 '14 at 05:45
Thanks for the impulsive downvote. For your kind consideration the error thrown by the xcode is "Apple LLVM 6.0 Error". I guess you haven't seen that before? — Atif Imran, Jun 05 '14 at 05:50
I've seen plenty of errors that begin with this string, but this part of the error message is irrelevant. Is it s compiler error or a linker error or some other kind of error? — The Paramagnetic Croissant, Jun 05 '14 at 06:13
Did you add any swift code? If so, you'll need to change target version to 7.0. — mservidio, Jun 10 '14 at 16:49
Hi..i am facing the same problem...my project runs in Xcode 5 but throw this error in Xcode 6 beta..Any suggestion is highly appreciated.Thanks — Tunvir Rahman Tusher, Jul 11 '14 at 15:07
http://stackoverflow.com/questions/25840720/xcode-6-pch-file-not-found have a look here — Nagendra Tripathi, Nov 04 '14 at 14:37

score 26 · Accepted Answer · answered Sep 19 '14 at 19:34

26

Ther is one way!

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

-> ENABLE FOUNDATION ASSERTIONS set it to NO

answered Sep 19 '14 at 19:34

user4059661

276
3
2

score 3 · Answer 2 · edited Jun 20 '20 at 09:12

The problem is, Xcode is not telling you the actual error that clang (LLVM) is throwing; it's just saying that clang process exited with code 1, meaning an error.

To find out exactly what the error is requires a bit of digging...

I don't have Xcode6, but this how it can be done in Xcode 5, and it's probably pretty similar:

If you open the "Logs Navigator" (View-->Navigators-->Logs Navigator or cmd-8) and click on "Build", you should be able to see the build that you just ran. Clicking on the three lines on the side will bring up the full command that was run and the output it gave.

You might be able to see your error here, but if not, you can do one better:

Copy and paste the command (it will be HUGE) from the window into a terminal and run it! You should look something like this:

CompileC /Users/Daly/Library/Developer/Xcode/DerivedData/Misc-hbomxnscgtjodqafsvgpndlyhkes/Build/Intermediates/Misc.build/Debug/Misc.build/Objects-normal/x86_64/template_tests.o Misc/template_tests.cpp normal x86_64 c++ com.apple.compilers.llvm.clang.1_0.compiler

cd /Users/Daly/Documents/School/EECS/Labs/Misc/Misc

export LANG=en_US.US-ASCII

/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -x c++ -arch x86_64 -fmessage-length=0 -fdiagnostics-show-note-include-stack -fmacro-backtrace-limit=0 -std=c++11 -stdlib=libc++ -Wno-trigraphs -fpascal-strings -O0 -Wno-missing-field-initializers -Wmissing-prototypes -Wno-non-virtual-dtor -Wno-overloaded-virtual -Wno-exit-time-destructors -Wno-missing-braces -Wparentheses -Wswitch -Wno-unused-function -Wno-unused-label -Wno-unused-parameter -Wunused-variable -Wunused-value -Wno-empty-body -Wno-uninitialized -Wno-unknown-pragmas -Wno-shadow -Wno-four-char-constants -Wno-conversion -Wno-constant-conversion -Wno-int-conversion -Wno-bool-conversion -Wno-enum-conversion -Wno-shorten-64-to-32 -Wno-newline-eof -Wno-c++11-extensions -DDEBUG=1 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk -fasm-blocks -fstrict-aliasing -Wdeprecated-declarations -Winvalid-offsetof -mmacosx-version-min=10.8 -g -fvisibility-inlines-hidden -Wno-sign-conversion -iquote /Users/Daly/Library/Developer/Xcode/DerivedData/Misc-hbomxnscgtjodqafsvgpndlyhkes/Build/Intermediates/Misc.build/Debug/Misc.build/Misc-generated-files.hmap -I/Users/Daly/Library/Developer/Xcode/DerivedData/Misc-hbomxnscgtjodqafsvgpndlyhkes/Build/Intermediates/Misc.build/Debug/Misc.build/Misc-own-target-headers.hmap -I/Users/Daly/Library/Developer/Xcode/DerivedData/Misc-hbomxnscgtjodqafsvgpndlyhkes/Build/Intermediates/Misc.build/Debug/Misc.build/Misc-all-target-headers.hmap -iquote /Users/Daly/Library/Developer/Xcode/DerivedData/Misc-hbomxnscgtjodqafsvgpndlyhkes/Build/Intermediates/Misc.build/Debug/Misc.build/Misc-project-headers.hmap -I/Users/Daly/Library/Developer/Xcode/DerivedData/Misc-hbomxnscgtjodqafsvgpndlyhkes/Build/Products/Debug/include -I/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include -I/Users/Daly/Library/Developer/Xcode/DerivedData/Misc-hbomxnscgtjodqafsvgpndlyhkes/Build/Intermediates/Misc.build/Debug/Misc.build/DerivedSources/x86_64 -I/Users/Daly/Library/Developer/Xcode/DerivedData/Misc-hbomxnscgtjodqafsvgpndlyhkes/Build/Intermediates/Misc.build/Debug/Misc.build/DerivedSources -F/Users/Daly/Library/Developer/Xcode/DerivedData/Misc-hbomxnscgtjodqafsvgpndlyhkes/Build/Products/Debug -MMD -MT dependencies -MF /Users/Daly/Library/Developer/Xcode/DerivedData/Misc-hbomxnscgtjodqafsvgpndlyhkes/Build/Intermediates/Misc.build/Debug/Misc.build/Objects-normal/x86_64/template_tests.d --serialize-diagnostics /Users/Daly/Library/Developer/Xcode/DerivedData/Misc-hbomxnscgtjodqafsvgpndlyhkes/Build/Intermediates/Misc.build/Debug/Misc.build/Objects-normal/x86_64/template_tests.dia -c /Users/Daly/Documents/School/EECS/Labs/Misc/Misc/Misc/template_tests.cpp -o /Users/Daly/Library/Developer/Xcode/DerivedData/Misc-hbomxnscgtjodqafsvgpndlyhkes/Build/Intermediates/Misc.build/Debug/Misc.build/Objects-normal/x86_64/template_tests.o

(This is from one of my projects.) You can skip the first line (CompileC .... 1_0.compiler), but copy the rest and paste it into a terminal!

Hopefully this lets you see the error and we can work from there (probably in a new question)!

There are a number of types of linker error that Xcode seems not to correctly handle, so this advice is good. Duplicate symbols at link-time seems to be one of them. — marko, Sep 14 '14 at 08:31

score 3 · Answer 3 · answered Oct 16 '14 at 20:14

3

This happened to me when I renamed my project. To solve this, Select Targets/Build Settings and search for the old project name and replace with the new name.

answered Oct 16 '14 at 20:14

Beto Caldas

2,198
2
23
23

score 2 · Answer 4 · answered Nov 06 '14 at 05:01

I got the same error, but what causing it was some missing classes library. then i added them again to the project but still causing the error.
after i searched it in the build phase, those class that had been missing is still linked to the project, so all i did is to remove those class that been highlighted red.
clean the project, and then build it.
for me, it worked

score 2 · Answer 5 · edited May 23 '17 at 12:17

2

Final solution:

Try to delete the appTests like here here:

https://www.dropbox.com/s/j9s6nycb58x3nzs/target_tests.png?dl=0

Credits for this answer: Apple LLVM 6.0 Error: clang failed with exit code -1

edited May 23 '17 at 12:17

Community

1
1

answered Nov 08 '14 at 01:34

LinusGeffarth

27,197
29
120
174

score 2 · Answer 6 · 2014-12-05T10:30:12.813

This example worked for me. Follow this link if you want to do it with the screen shots. Otherwise here are the steps:
STEP 1: From the menu bar of xcode select > window > organizer
STEP 2: The new window will open, copy the derived data address till /derivedData e.g. ~/Library/Developer/Xcode/DerivedData/
STEP 3: Quit xCode
STEP 4: Double click/tap on finder and select "Go to Folder"
STEP 5: Paste the copied address in the text field
STEP 6: The folder that will open delete every single file and folder you see in it.
STEP 7: Empty your trash and open xCode again and run the project.
It worked for me.

Atif Imran · Answer 7 · 2014-09-14T06:55:29.220

Temporary Solution.

I removed the 6.0 support which was one of the areas causing problem and that seemed to have fixed it. However, if you need support for earlier versions this will still be an issue.

There might be trouble at the prefix.pch file, make sure you also double check your prefix.pch for any code that might be from the previous os version. If you dont't need the pre-compilation set it to NO by going to TARGETS > PreCompile Prefix Headers and selecting NO. You may then need to manually import the frameworks/file to every class file you make.

EDIT

If you do a hard cleaning cmd + product > clean. You will see an option 'Clean Build Folder..'. Using that sometimes removes the issue. If that still doesn't work reinstall the xcode6 and it will work(since you already have the downloaded dmg setup, it will take 2min only)

score 1 · Answer 8 · answered Dec 03 '16 at 18:27

1

I was able to resolve this error by changing the 'Build Settings -> iOS Deployment Target' value to a more recent iOS version.

answered Dec 03 '16 at 18:27

ViperMav

71
3

score 1 · Answer 9 · answered May 10 '18 at 16:11

I was trying to use openMP on XCode-9 on Mac-OS Sierra 10.13.4 and I followed these steps : [http://antonmenshov.com/2017/09/09/clang-openmp-setup-in-xcode/][1]

I have the error like this :

clang-6.0: error: cannot specify -o when generating multiple output files

I fix that problem by changing some settings in XCode:

In build settings > build options > Enable Index-While-Building Functionality to No

score 0 · Answer 10 · answered Dec 03 '14 at 13:36

This problem might occur when the project library looses its reference due to some condition.Go to --> Library -->Developer --> Xcode -->DerivedData .Now delete the "DerivedData" folder.Clean and run your project. This solves the issue. Hope this helps

score 0 · Answer 11 · answered Nov 25 '15 at 19:59

Such a problem may occur if you change some Cocoa header by an accident. The compiler will ask you to rebuild precompiled headers (in my case it did so), but the actual error will be different. To make the compiler show you a real error set ENABLE FOUNDATION ASSERTIONS to NO (it's described above), so, you'll find out which header caused failure.

score 0 · Answer 12 · answered Feb 15 '18 at 05:14

0

You need to change the Development target .... it works for me

answered Feb 15 '18 at 05:14

Abhishek Mishra

1,625
16
32

Apple LLVM 6.0 Error

12 Answers12