Apple Mach-O Linker Error when compiling for device

Question

I've just upgraded to xcode 4.0 and I can no longer deploy to iPhone, I get a Apple Mach-O Linker Error, it still works for the simulator though.

    Ld /Users/yveswheeler/Library/Developer/Xcode/DerivedData/iParcel-fkeqjcjcbbhjwhdssjptkdxzzzxh/Build/Intermediates/iParcel.build/Debug-iphoneos/iParcel.build/Objects-normal/armv7/iParcel normal armv7
    cd /Users/yveswheeler/iParcel
    setenv IPHONEOS_DEPLOYMENT_TARGET 3.2
    setenv PATH "/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin:/Developer/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin"
    /Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/g++-4.2 -arch armv7 -isysroot /Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS4.3.sdk -L/Users/yveswheeler/Library/Developer/Xcode/DerivedData/iParcel-fkeqjcjcbbhjwhdssjptkdxzzzxh/Build/Products/Debug-iphoneos -F/Users/yveswheeler/Library/Developer/Xcode/DerivedData/iParcel-fkeqjcjcbbhjwhdssjptkdxzzzxh/Build/Products/Debug-iphoneos -filelist /Users/yveswheeler/Library/Developer/Xcode/DerivedData/iParcel-fkeqjcjcbbhjwhdssjptkdxzzzxh/Build/Intermediates/iParcel.build/Debug-iphoneos/iParcel.build/Objects-normal/armv7/iParcel.LinkFileList -dead_strip -all_load -ObjC -lxml2 -miphoneos-version-min=3.2 -framework UIKit -framework CoreGraphics -framework QuartzCore /Users/yveswheeler/Library/Developer/Xcode/DerivedData/iParcel-fkeqjcjcbbhjwhdssjptkdxzzzxh/Build/Products/Debug-iphoneos/libThree20.a /Users/yveswheeler/Library/Developer/Xcode/DerivedData/iParcel-fkeqjcjcbbhjwhdssjptkdxzzzxh/Build/Products/Debug-iphoneos/libThree20Core.a /Users/yveswheeler/Library/Developer/Xcode/DerivedData/iParcel-fkeqjcjcbbhjwhdssjptkdxzzzxh/Build/Products/Debug-iphoneos/libThree20Network.a /Users/yveswheeler/Library/Developer/Xcode/DerivedData/iParcel-fkeqjcjcbbhjwhdssjptkdxzzzxh/Build/Products/Debug-iphoneos/libThree20Style.a /Users/yveswheeler/Library/Developer/Xcode/DerivedData/iParcel-fkeqjcjcbbhjwhdssjptkdxzzzxh/Build/Products/Debug-iphoneos/libThree20UI.a /Users/yveswheeler/Library/Developer/Xcode/DerivedData/iParcel-fkeqjcjcbbhjwhdssjptkdxzzzxh/Build/Products/Debug-iphoneos/libThree20UICommon.a /Users/yveswheeler/Library/Developer/Xcode/DerivedData/iParcel-fkeqjcjcbbhjwhdssjptkdxzzzxh/Build/Products/Debug-iphoneos/libThree20UINavigator.a -framework AddressBook -lz.1.2.3 -framework Foundation -framework CFNetwork -framework MobileCoreServices -framework SystemConfiguration -framework MessageUI -framework AudioToolbox -o /Users/yveswheeler/Library/Developer/Xcode/DerivedData/iParcel-fkeqjcjcbbhjwhdssjptkdxzzzxh/Build/Intermediates/iParcel.build/Debug-iphoneos/iParcel.build/Objects-normal/armv7/iParcel

arm-apple-darwin10-g++-4.2.1: /Users/yveswheeler/Library/Developer/Xcode/DerivedData/iParcel-fkeqjcjcbbhjwhdssjptkdxzzzxh/Build/Products/Debug-iphoneos/libThree20.a: No such file or directory
arm-apple-darwin10-g++-4.2.1: /Users/yveswheeler/Library/Developer/Xcode/DerivedData/iParcel-fkeqjcjcbbhjwhdssjptkdxzzzxh/Build/Products/Debug-iphoneos/libThree20Core.a: No such file or directory
arm-apple-darwin10-g++-4.2.1: /Users/yveswheeler/Library/Developer/Xcode/DerivedData/iParcel-fkeqjcjcbbhjwhdssjptkdxzzzxh/Build/Products/Debug-iphoneos/libThree20Network.a: No such file or directory
arm-apple-darwin10-g++-4.2.1: /Users/yveswheeler/Library/Developer/Xcode/DerivedData/iParcel-fkeqjcjcbbhjwhdssjptkdxzzzxh/Build/Products/Debug-iphoneos/libThree20Style.a: No such file or directory
arm-apple-darwin10-g++-4.2.1: /Users/yveswheeler/Library/Developer/Xcode/DerivedData/iParcel-fkeqjcjcbbhjwhdssjptkdxzzzxh/Build/Products/Debug-iphoneos/libThree20UI.a: No such file or directory
arm-apple-darwin10-g++-4.2.1: /Users/yveswheeler/Library/Developer/Xcode/DerivedData/iParcel-fkeqjcjcbbhjwhdssjptkdxzzzxh/Build/Products/Debug-iphoneos/libThree20UICommon.a: No such file or directory
arm-apple-darwin10-g++-4.2.1: /Users/yveswheeler/Library/Developer/Xcode/DerivedData/iParcel-fkeqjcjcbbhjwhdssjptkdxzzzxh/Build/Products/Debug-iphoneos/libThree20UINavigator.a: No such file or directory
Command /Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/g++-4.2 failed with exit code 1

What the heck?! So many __different__ problems for the __same__ error message. Good job Apple! — Iulian Onofrei, Oct 25 '14 at 07:47
**"ERROR: An Error has occurred"** would be more helpful :)) — Aviram Netanel, Jun 24 '15 at 11:02
Look at the warnings the Linker spits out before the error; it may lead to a better/more specific solution. — Pro Q, Sep 11 '17 at 06:45
https://stackoverflow.com/questions/44601404/apple-mach-o-linker-error-clang-error-linker-command-failed-with-exit-code-1 — Naresh, Mar 02 '19 at 09:25

Gajendra K Chauhan · Answer 1 · 2015-02-18T11:07:14.380

214

Here is permanent solution.Generally overwriting project may cause this prolems.Try this method.

-UPDATE - Clang error - Mach-O Linker error

In some case error log window displaying .xctest error, to fix it

-> Select your project

-> Beside this(just before General tab) select your projectTest file from dropdown

-> There is one option (like ProjNameTests)

-> In Host Application, select your project from dropdown only if it show custom

DONE!

enter image description here

Old method deleted

edited Feb 18 '15 at 11:07

answered Jan 17 '12 at 11:31

Gajendra K Chauhan

3,387
7
40
55

4

If I remove the Framework search path than I'm getting can't find header file – Danpe Oct 05 '13 at 21:55
fail destroys my project – CommaToast Mar 05 '14 at 11:18
There's no way to undo – zbz.lvlv Nov 13 '14 at 01:55
@GajendraKChauhan -> Beside this select your projectTest file from dropdown where is it in project ? – Chirag Pipaliya Nov 18 '14 at 12:32
just before General tab – Gajendra K Chauhan Nov 18 '14 at 12:41
Thanks, second one helped me also. – Goran Jakovljevic Nov 23 '14 at 12:59
66

I think i don't get it. What should I do…? – fabian Mar 29 '15 at 20:08
1

@fabian Just skip out and try alternate solution :-) – Gajendra K Chauhan Jul 09 '15 at 08:52
4

Saved my day man. Sitting in front of my boss, have to show him the app I'm working on, and I got this linker error. I was gone if haven't landed here :D – Saraz Jan 30 '16 at 07:26
1

Wish I could up-vote this a second time! Cheers again – Jim Tierney Feb 18 '16 at 10:01
1

in my dropdown i cannot see my `ProjNameTests` how can i find it? – natsumiyu Jun 01 '16 at 08:52
Any answer solve my error. I do not understand why appears. I do not understand.clang: error: linker command failed with exit code 1 (use -v to see invocation) – Markus Oct 25 '16 at 13:50
2

where is host application in final step ? – Kartiikeya Feb 07 '18 at 09:53
1

I don't get it, my host application is my current application, it's not "custom" is there something I need to change in this screenshot - https://i.imgur.com/Xq3delf.png - ? thank you – Noitidart Jun 01 '18 at 05:29

score 194 · Answer 2 · edited Dec 26 '22 at 03:36

194

I had the same problem and the issue was that I have accidently imported a .m file instead of .h in an implementation file.

edited Dec 26 '22 at 03:36

starball

20,030
7
43
238

answered Apr 28 '11 at 07:50

Daniel

935
2
6
11

1

Impossible to find error! Just try each and every solution – AsifHabib Dec 17 '14 at 14:23
This is not true, I've tried the same thing in a new project and still getting same error. – Hemang Jun 11 '15 at 12:26
Go to the Project settings and Build phases section, make sure you do not have a .m file in the section "Copy Bundle Resources" instead of the "Compile Sources". that worked for me – LuAndre Sep 27 '16 at 20:03
Impossible to find the solution. I do not know what I am going to do... – Markus Oct 25 '16 at 13:50

score 72 · Answer 3 · answered Mar 24 '11 at 21:17

72

Just ran into the same issue.

The solution (for me) = check your frameworks.

In my case I had added classes related to CoreData without "CoreData.framework". Adding it solved the MACH_O complaining.

answered Mar 24 '11 at 21:17

Dante Cesa

330
2
4

6

It happens also when you linked again a library that isn't present in the latest SDK release. Let's say you linked against libz.1.2.3 and the sdk includes 1.2.5. Check your frameworks is a really good suggestion! Thank you Dante! – SlowTree Jan 05 '12 at 10:39
Thanks SlowTree, save suggestion solved my experience with this linker crash. libz.1.2.3 to libz.1.2.5; – Tom Pace Jan 13 '12 at 04:20
3

Cocoapods linked two `libPods.a` files for me (hence the duplicate symbols). Thanks, Dante! – Nick Merrill Dec 20 '14 at 19:21
Yes. Removed .a files and added again from linker. Its worked! – Balasubramanian Jun 13 '17 at 14:03

score 62 · Answer 4 · answered Oct 19 '16 at 19:18

62

open .xcworkspace file not .xcodeproj. I repeat open .xcworkspace file. All of your errors will go away.

answered Oct 19 '16 at 19:18

mahi

532
10
16

1

Wow, that has to be one of the most insane debug messages. I would have literally never guessed that this was the reason based off the message provided. – Joseph Casey Nov 02 '16 at 01:05
1

Did the trick for me because there was an external library that wasn't included in .xcodeproj. had to do with cocoapods – Sjoerd de Wit Aug 07 '17 at 09:56
This worked for me. Like @SjoerddeWit said -- cocoapods inclusion necessitates opening .xcworkspace rather than .xcodeproj. – Cody Richmond Aug 23 '18 at 15:28
I have exported a unity project to xcode and there's no .xcworkspace file – Ayush Malviya Mar 11 '19 at 13:22

score 36 · Answer 5 · answered Jul 03 '12 at 14:11

36

Re: Problem as outlined in title:

Just in case anyone else missed the obvious...

I came across this error after installing a new version of Xcode4 and dragging existing files into a new project. I had failed to spot that the 'add to targets' checkbox was left unchecked in the 'Choose options for adding files:' dialog. Correcting my omission in Targets>Build Phases>Compile Sources solved the problem.

answered Jul 03 '12 at 14:11

cate

600
7
15

This trick worked for me. thanks. I deleted all the compile directories and rebuild the project. – Vivek Gyaneshwar Jun 15 '17 at 11:02

score 34 · Answer 6 · answered Jun 06 '15 at 00:08

34

Menu > Product > Clean, this is what made it work. I'm not sure about everyone else. I added pic to show.

enter image description here

answered Jun 06 '15 at 00:08

dnaatwork.com

362
5
9

1

Awesome. By far the easiest solution I could find. – Vincent van Leeuwen Jun 12 '15 at 17:59

score 29 · Answer 7 · answered Aug 07 '11 at 05:54

29

Bizarre error. For me, I just cleaned and restarted Xcode and the problem went away.

answered Aug 07 '11 at 05:54

p.pad

529
7
11

score 26 · Answer 8 · answered Jul 19 '16 at 22:05

26

Fix: Build Settings > Enable Bitcode > No

answered Jul 19 '16 at 22:05

Sebastián Lara

5,355
2
28
21

Holy Shot.. ! This Worked for me :) – Droid Genie Nov 01 '18 at 07:08

score 23 · Answer 9 · answered Jul 05 '17 at 18:08

23

None of these answers helped me. Then I tried to reinstall Cocoapods:

pod deintegrate

pod install

Problem solved!

answered Jul 05 '17 at 18:08

Johannes

1,370
16
15

I'm not sure where the disconnect with pods & xcode is but often times it's a struggle to make sure pods files make it to the derivedData folder. This seems to fix that issue. I wish I could start just this answer.. – Jacksonkr Sep 19 '17 at 13:54

score 20 · Accepted Answer · answered May 30 '11 at 18:48

20

The problem was that in XCode 4, the dependencies do not assume the architecture settings of the main project, as they previously did in XCode 3. I had to go through all of my dependencies setting them for the correct architecture.

answered May 30 '11 at 18:48

CodeVomit

749
2
7
10

2

thank you! I was completed misled by the fact that the error message from the linker complains about "File not Found", not "File found, but I can't use it ...", and was wandering through the xcode settings looking for library search paths. But this worked for me. And if you hare having this problem, this other post is also related: http://stackoverflow.com/questions/2999844/three20-and-ios-4. Also, this nice summary blog: http://www.amirnaor.com/?p=112 – Rob Aug 28 '11 at 13:48

score 13 · Answer 11 · answered Mar 22 '11 at 13:20

13

I had the same and managed to solve it.

In xcode preferences, location tab change value under build location to "Place build products in locations specified by targets".

answered Mar 22 '11 at 13:20

Wolfert

974
6
12

Thanks Wolfert, tried that but still have 1250 Apple Mach-O Linker Warnings and no progress. Did you do anything else to fix this? Cheers – Mar 22 '11 at 22:14
6

Option isn't available in XCode 5.1 – Hemang Nov 04 '14 at 10:02

score 13 · Answer 12 · answered Jun 29 '11 at 13:15

I struggled with this for a little while, and in my case it ended up being the Build Setting under Search Paths called FRAMEWORK_SEARCH_PATHS. It helped that I selected the "Levels" button, which seemed to compare my project, target and "Resolved" settings. I saw that my target setting somehow overrode the default of "$(inherited)", and the overridden value was what XCode "resolved" the setting to be. When I removed the override, which in this case specified the 3.2 sdk, the linker errors went away -- as did some recently appeared warnings about any classes where I called post-4.0 methods.

About those warnings -- I never saw them before I added the MessageUI framework for a recent change. I suspect, but don't know for sure, that when I added that framework, XCode tried to do something clever by adding that override to my target. I didn't do it explicitly at any point. The warnings were,for example, about the URLByAppendingPathComponent method of NSURL, which did not appear until sdk 4.0. Prior to adding the MessageUI framework, I never got that warning. And since I removed the override, I no longer get them.

score 11 · Answer 13 · answered Jun 27 '11 at 19:37

11

I had this issue and importing QuartzCore fixed it.

answered Jun 27 '11 at 19:37

jmosesman

716
1
11
24

score 8 · Answer 14 · answered Oct 04 '12 at 22:37

8

Changing "Build Active Architectures Only" to Yes in CordovaLib.xcodeproj -> Build Settings did the trick for me. earlier the app was running on simulator, but not on the device.

answered Oct 04 '12 at 22:37

Nishanth Nair

2,975
2
19
22

score 7 · Answer 15 · answered Mar 16 '11 at 18:17

7

You may need to update your build settings.

Verify the iOS target version and the processor architectures, as you may not have the old SDKs with XCode 4.

You may see «Missing SDK» on the build settings. Change that to whatever applies.

answered Mar 16 '11 at 18:17

Macmade

52,708
13
106
123

That's pretty much the first thing I do whenever I upgrade xcode. This time it's not the problem. – CodeVomit Mar 16 '11 at 19:40

score 7 · Answer 16 · answered May 12 '11 at 13:02

7

I had the same issue: just accidentally deleted a .m file, while .h was in the project. The problem disappeared when I've restored the .m file.

answered May 12 '11 at 13:02

Misha Karpenko

2,168
17
18

score 6 · Answer 17 · answered Apr 22 '11 at 19:35

6

Check to make sure that you don't have a specific framework search path specified. if you go to the info on the target and just remove the framework search path entries it should use the defaults for your specified deployment version.

answered Apr 22 '11 at 19:35

Grady Player

14,399
2
48
76

score 5 · Answer 18 · answered Jul 02 '15 at 13:21

5

I had exactly the same problem just because I had two same constants in different classes. You also can have this problem if you import .m file not .h file

answered Jul 02 '15 at 13:21

Adela Toderici

1,118
13
30

You save my day!! – teck wei Apr 18 '17 at 01:19
@teckwei you can press the upVote arrow :D – Adela Toderici Apr 18 '17 at 10:15

score 5 · Answer 19 · edited Jun 20 '20 at 09:12

I just try to create a category class file and got this weird issue..and finally....

Wrong way to create category class that causes the issue:

New File -> Cocoa Touch -> Objective-C class, then I modified the name of files to Category Class like name.. (i.e. OriginalClass_CategoryName.h/m to OriginalClass+CategoryName.h/m, and also modified the contents in the file).

Right way here:

New File -> Cocoa Touch -> Objective-C category, and it'll auto generate files (OriginalClass+CategoryName.h/m).

Oh, how stupid I am!!

score 5 · Answer 20 · answered Feb 22 '12 at 11:33

If you are using CoreData, and you use XCode to generate NSManagedObject subclasses for your entities, make sure you only generate one for each entity.

My problem was that it generated multiple NSManagedObject subclasses for the same entity (and put them in different folders).

I just deleted all of them and regenerated the NSManagedObject subclasses.

score 5 · Answer 21 · answered Mar 15 '12 at 09:25

5

To add onto the list of weird stuff that fixed this issue...

I had some const CGFloat variables in a global header file like so

const NSInteger  globalInteger1 = 2;
const NSInteger  globalInteger2 = 3;

The moment I removed these, all was fine :)

answered Mar 15 '12 at 09:25

sherlock

1,521
2
13
17

1

My WEIRD issue was at the .pch or constants.h file I have declared a constant as NSString * const kInitiaNotification = @"kInitialNotification"; without mentioning the "static" at first – Mazen Kasser Feb 12 '14 at 06:23
I had the issue just after I changed from `NSString static *key = @"someKey"` to `const NSString *key = @"someKey"` – TonyTony Sep 09 '14 at 15:42

score 4 · Answer 22 · answered Oct 31 '14 at 09:28

4

I solved this problem too weird !

Go to Target > Build Phases > Link Binary with libraries :

Remove all your frameworks and add them again !

Hope it works for you !

answered Oct 31 '14 at 09:28

Rudi

4,304
4
34
44

pretty awful solution – SleepsOnNewspapers Apr 26 '15 at 01:47
It cannot be answer... not logical very much – LKM Jun 01 '15 at 03:34
I checked the error message and found that it was one of the frameworks, so I removed that framework and added it again, not all the frameworks but just that one. – Oluwatobi Omotayo Aug 24 '17 at 19:07

score 4 · Answer 23 · answered May 16 '15 at 12:42

4

For Swift language ...

I am getting this error " ld: file too small (length=0) .... "

In my case I just clean the project and then rebuild it ..

Steps:-

1) goto Project -> Clean

2) goto Project -> Build

Hope this helps..

answered May 16 '15 at 12:42

Niks

87
2
8

score 4 · Answer 24 · answered May 09 '16 at 10:16

4

This did a trick for me:

Go to

1) Products > clean

2) Windows > Projects

3) Select your project and click on "Delete" derived Data

4) Products > Build

answered May 09 '16 at 10:16

score 4 · Answer 25 · answered Mar 24 '11 at 21:25

4

Not sure if it's related, but seeing that you're running some three20 libraries, you may want to check this post on their website: http://three20.info/article/2011-03-10-Xcode4-Support

answered Mar 24 '11 at 21:25

Rog

18,602
6
76
97

score 4 · Answer 26 · answered Jan 12 '12 at 14:07

4

I had the same problem, and I solved it. In my case, "architectures" setting caused the problem. In my project file, Build Settings tab, Architectures were set to armv6. I changed it to Standard(armv7), do clean and build. Then it worked!

answered Jan 12 '12 at 14:07

Kim Jin

31
3

score 4 · Answer 27 · answered Feb 21 '12 at 03:25

In my case the problem was having different architectures specified under different targets. I was building my application target with armv6, armv7 and cocos2d with Standard (amrv7). Go into build settings and make sure your architectures agree for all targets.

score 3 · Answer 28 · answered Apr 04 '12 at 17:55

I was able to fix this error by editing "Library Search Paths"

It cropped up in the first place because I had moved a couple folders around, and that ended up giving my build settings two different search paths because they are are automatically added to your build settings when you link a library/framework, but they are not always removed.

So if you move a linked library/framework to a different directory and re-link it, you'll have to manually edit the search path.

You might be able to dodge this by removing the library/framework before moving it, but I haven't tested that.

score 3 · Answer 29 · answered Dec 17 '13 at 02:04

3

For me it was accidentally importing an implementation ".m" file instead of the corresponding header ".h" file. As soon as I caught that the project build was back to normal.

answered Dec 17 '13 at 02:04

owenfi

2,471
1
24
37

score 3 · Answer 30 · answered Jun 24 '15 at 11:00

3

Code Signinig!!!

I had this issue too - "linker command failed with exit code 1 (use -v to see invocation)"

my problem was I tried to run the app on a real device, and I forgot to configure the Code Signing section in the Build Settings tab.

answered Jun 24 '15 at 11:00

Aviram Netanel

12,633
9
45
69

How did you configure that setting? Please help! – Pixele9 Jun 02 '17 at 02:13
select the target, go to build settings tab, in the Code Signing section – Aviram Netanel Jun 07 '17 at 07:24

score 3 · Answer 31 · answered Oct 21 '16 at 21:17

3

for me the problem was I had loaded same functions twice. Remove -ObjC from Build Settings > Linking > Other Linker Flags.

answered Oct 21 '16 at 21:17

Agu Dondo

12,638
7
57
68

score 3 · Answer 32 · answered Apr 13 '17 at 10:48

3

If you have defined NSObject with the same name like:

NSObject *notUniqueObj;

even in 2 different files ( if you are importing one in another ), it will give you an error. Give different names for those.

answered Apr 13 '17 at 10:48

Omkar Jadhav

1,046
3
16
41

Enchilada · Answer 33 · 2011-04-01T12:14:30.187

3

One possibility: Turn on "Dead code stripping" in the Xcode 4 build settings.

Another possibility: It could be that you switched to using LLVM for some framework that was previously using GCC. Moving back to GCC (or LLVM GCC) may get rid of those warnings.

edited Apr 01 '11 at 12:14

answered Apr 01 '11 at 11:24

Enchilada

3,859
1
36
69

score 3 · Answer 34 · answered Mar 23 '12 at 15:52

3

I mistakenly defined a new constant with the same name as an existing constant in a different file and it caused this error for me using xCode 4.3.1. xCode didn't complain but the compiler doesn't like it.

answered Mar 23 '12 at 15:52

moliveira

798
8
17

score 2 · Answer 35 · answered Nov 27 '12 at 08:46

For me was architectures fault when running on device in XCode 4.5.x.

XCode 4.5 doesn't support armv6 any more, so my fix was:

I just edited all targets in all libraries (three20Core, three20Common, etc.) and libThree20: in build settings have chosen only armv7 and armv7s in "Architectures" and "Valid Architectures"

score 2 · Answer 36 · answered Jan 29 '13 at 21:10

2

In my case I had duplicated a class file! Found it by using the bottom search field at the right side bar of Xcode, so to solve it remove reference of one of them

answered Jan 29 '13 at 21:10

Mazen Kasser

3,559
2
25
35

score 2 · Answer 37 · answered Aug 11 '13 at 10:00

2

My fix for my same problem: Adding the "other linker flags" in "Project" and not in "Targets". So, I moved it to "Targets", it shouldn't be in "Project".

answered Aug 11 '13 at 10:00

Idan Moshe

1,675
4
28
65

score 2 · Answer 38 · answered Jan 24 '14 at 21:08

2

I was accidentally trying to compile for 64-bit simulator which was not agreeing with my CocoaPods

answered Jan 24 '14 at 21:08

Alan

4,325
3
21
25

score 2 · Answer 39 · answered Oct 01 '14 at 07:47

I'm running xcode 5. In my case I've to change my "Deployment Target". It was previously set as 3.0 and I change it to 7.0. Now the error message gone. To change your "Deployment Target", follow the steps:

Go to your "Project name" (top left)
Go to your "Targets" (middle of the screen)
Go to "General"
"Deployment Info"
"Deployment Target"

Change it to current iOS version. -Thanks.

score 1 · Answer 40 · answered Aug 03 '12 at 15:25

1

If you're getting a Mach-O Linker warning or error that says "Directory not found for option", lookup the path of that directory. If it's missing try downloading the latest version of RestKit and putting the folder in manually.

answered Aug 03 '12 at 15:25

Kyle Clegg

38,547
26
130
141

score 1 · Answer 41 · answered Oct 12 '13 at 14:33

1

I accidentally added two copies of the same subclass of a UITableViewController. Removing one of the sets of files cleared up the error.

answered Oct 12 '13 at 14:33

SmileBot

19,393
7
65
62

score 1 · Answer 42 · answered May 13 '17 at 01:59

1

My issue was because I didn't defined variables as extern in one of my header files and it was redeclared in the .c file.

answered May 13 '17 at 01:59

Dan

1,812
3
13
27

score 1 · Answer 43 · answered Jul 29 '18 at 19:36

1

The solution of this problem is very simple Just go to the directory where the project installed and open the file with extension ".xcworkspace"

That will solve the problem .

answered Jul 29 '18 at 19:36

Ahmed Samir

291
3
6

score 0 · Answer 44 · edited Oct 20 '12 at 12:25

0

I fixed it by changing Mach-O Type under linking section on the Build settings from Nothing to Executable.

edited Oct 20 '12 at 12:25

j0k

22,600
28
79
90

answered May 30 '12 at 00:27

Menan Vadivel

106
1
5

score 0 · Answer 45 · answered Aug 30 '12 at 12:26

0

I got this problem after importing a framework. Under 'Build Phases', the framework's name was highlighted in red. I added the framework again and the problem was solved.

answered Aug 30 '12 at 12:26

yoeriboven

3,541
3
25
40

score 0 · Answer 46 · edited Dec 23 '13 at 02:20

0

Follow these steps to fix this problem:

Go to project settings and Build Tab. Search for "Other Linker Flags"

Double click on the linker flags for Release and Change:

 ${TARGET_BUILD_DIR}/libCordova.a to ${BUILT_PRODUCTS_DIR}/libCordova.a

Do the same for Debug Clean and build archive again.

edited Dec 23 '13 at 02:20

Unheilig

16,196
193
68
98

answered Nov 22 '13 at 19:40

Tuttoilmondo

1

score 0 · Answer 47 · answered Dec 23 '13 at 02:16

0

I got the same issue when i export FMDB module in xcode 4.6. Later i found a fmdb.m in my my file list which was causing this issue. After i removed from the project it works fine

answered Dec 23 '13 at 02:16

winari

46
4

score 0 · Answer 48 · answered Apr 29 '14 at 07:57

in my case i just moved the .h .m file from one folder to other folder and that folder was not exsisting behind. so i created folder first on finder and then moved the file on finder and then add that folder and remove the reference of moved filed to other folder from project it stopped giving me error

score 0 · Answer 49 · answered May 25 '14 at 22:41

I had this same problem just a minute ago. which lead me here, which wasn't of any help. But I figured out what was the problem and fixed it. the problem was that in my header file i had declare one instance of the struct class named trig_node[SIZE]

my header...

struct TrigNode
{
    float msin;
    float mcos;
    float mtan;
}trig_node[SIZE];

and in my .cpp file i have a function that access this instance and return the answer.

float cos_table_(float deg)
{
    uint n = ((SIZE/DEGRE)*deg);
    return trig_node[n % DEGRE].mcos;
}

which is what as causing my linking error. So, to fix that i place the instance of the trig table class "trig_node[SIZE]" in the .cpp file which cleared the error. so now the new fix looked something like this

my header...

struct TrigNode
{
    float msin;
    float mcos;
    float mtan;
};

my .cpp file trig_node[SIZE]

float cos_table_(float deg)
{
    uint n = ((SIZE/DEGRE)*deg);
    return trig_node[n % DEGRE].mcos;
}

score 0 · Answer 50 · answered Jun 12 '14 at 12:02

0

This error can also be occurred if you have imported two different versions of same library ,in this case just remove the older version and keep only one version and Magic will work for you.

answered Jun 12 '14 at 12:02

AHSAN NAZIR RAJA

166
1
13

score 0 · Answer 51 · answered Jul 06 '14 at 23:44

If you used XCode to create a custom NSManagedObject class and then add to it and generate a new file for the custom class, sometimes XCode will not overwrite your old class and you will be stuck with two of the same files but in different directories. Find the old file and delete it.

The problem could be something else though.

score 0 · Answer 52 · answered Sep 09 '14 at 12:58

0

Could you try Unity-Build Settings-Player Settings-SDK Version: Device SDK instead of simulator sdk

Ive had such error and that fixed it

answered Sep 09 '14 at 12:58

Stormy

541
4
9

score 0 · Answer 53 · answered Oct 10 '14 at 08:11

0

I encountered with this problem to figure out that I have two references in my XCODE project. Just delete the other reference. Hope this helps

answered Oct 10 '14 at 08:11

Rick Royd Aban

904
6
33

score 0 · Answer 54 · answered Jan 27 '15 at 07:00

I had the same Problem, As I was dragging some files .h and .m into my Project and Xcode started showing me this error clang: error: linker command failed with exit code 1 (use -v to see invocation) while running.

Later I discovered that I already have that .h & .m in my Xcode Project under some other SubFolder. So I deleted that Extra .h and .m , Cleaned my Project and Its working now.

clang: error: linker command failed with exit code 1 (use -v to see invocation) This error comes for a number of reason, Thats why this Question has so many Answers. You just need to see & check; what case you fall in.

score 0 · Answer 55 · answered Feb 07 '15 at 19:07

0

i think the best response is to look into files imports , some imports has a problem .

example : include #import "file.m" or include external file.h

...

answered Feb 07 '15 at 19:07

user2165491

101
1
4

score 0 · Answer 56 · answered Feb 10 '15 at 04:06

0

My specific error was:

ld: entry point (_main) undefined. for architecture armv7

Which should have been obvious, but it's because main.m was not include into Compile Sources under Build Phases

answered Feb 10 '15 at 04:06

Jacksonkr

31,583
39
180
284

score 0 · Answer 57 · answered Apr 01 '15 at 00:46

I would like to share one more reason when I got this error:

I had changed the project name in Project Navigator(in Xcode 6.1.1) by single click on it and my project would not compile. I changed the project name back to old name, project was building. Very very strange but yes I have faced this. I hope this information helps.

score 0 · Answer 58 · answered Jul 09 '15 at 23:35

0

I simply had to files with a main() method and Xcode wasn't happy about that.

answered Jul 09 '15 at 23:35

Curlip

395
1
3
15

score 0 · Answer 59 · answered Jan 20 '16 at 19:39

0

If you use Xcode 7 or later just do a product -> clean. This worked for me.

answered Jan 20 '16 at 19:39

Daniel

3,758
3
22
43

score 0 · Answer 60 · answered Apr 01 '16 at 19:27

My problem was that in multiple class.m files I had created an NSString named TAG, and I had set the value of TAG to the String name of each class (Ex: NSString * TAG = HWGuiControl). I had done so that then it was easy to prepend my NSLog statements with the name of the class. (I have used this system in Android with great success, great for analyzing program flow 2 years later). Deploying to a device, this all works great. But when its time to create an Archive for distribution, apparently the linker cannot contend with the NSString named TAG appearing in multiple files. Modifying the name(s) of TAG to HWGTAG, etc, did the trick.

score 0 · Answer 61 · answered Sep 01 '16 at 19:57

In my own case, I had duplicate declarations of some keys. I declared some NSString Constants using the extern keyword and did exactly the same thing in two different class files. When I removed one of them, the error disappeared.

extern NSString *const CFDataStatusKey;
extern NSString *const CFDataErrorKey;
extern NSString *const CFDataReasonKey;
extern NSString *const CFDataChannelsKey;

These where declared and initialized respectively in .h and .m files of the two classes. Removing a duplicate solved the issue. Hopes this helps

score 0 · Answer 62 · answered Nov 03 '16 at 13:59

0

In my case, the cause of such Apple Mach-O Linker error was source code file (.m) inclusion to resource bundle target.

Verify that recently created .m file is not included in a bundle: select the file in project navigator, open file inspector and make sure that resource bundle checkbox is deselected in Target Membership section.

answered Nov 03 '16 at 13:59

pjuzeliunas

1,596
1
15
19

In my case it was a matter of selecting instead of deselecting – Wojtek Dmyszewicz Apr 18 '17 at 23:00

score 0 · Answer 63 · answered Jan 23 '17 at 12:21

I had to make sure my framework was built with a Simulator selected in order to build my project with a simulator (my project of course is using the framework). Same goes for building on my iPhone everything has to be in sync not sure why but it fixes the issue.

I hope this helps someone.

score 0 · Answer 64 · answered Jul 17 '18 at 09:40

0

In my case i has include .m file thats why compiler shows this type of error.

you should check the latest file import that is not .m file " Sometime i"

answered Jul 17 '18 at 09:40

Abhijit Kotangale

39
6

score 0 · Answer 65 · edited Aug 08 '19 at 09:13

0

Please go to your workspace setting and make the following changes:

Workspace Setting:
   Build System:
     Legacy BuilPer-User


 Per-User Workspace
  DerivedData:
    Workspace relative location



Build System 
    Use User Setting

edited Aug 08 '19 at 09:13

NickCoder

1,504
2
23
35

answered Aug 08 '19 at 08:52

Andy Rubin

25
7

Chintan Shah · Answer 66 · 2022-07-26T07:08:34.207

For our Flutter project, we recently changed the bundle identifier and it doesn't get updated properly in Info.plist. Thus, creating this issue.

We had to add/update following keys in Info.plist with given values:

BUNDLE_ID
CFBundleDisplayName
CFBundleName

<key>CFBundleInfoDictionaryVersion</key>
<string>6.0</string>

<key>CFBundlePackageType</key>
<string>APPL</string>

<key>CFBundleIdentifier</key>
<string>$(PRODUCT_BUNDLE_IDENTIFIER)</string>
<key>CFBundleExecutable</key>
<string>${EXECUTABLE_NAME}</string>

<key>CFBundleShortVersionString</key>
<string>$(MARKETING_VERSION)</string>
<key>CFBundleVersion</key>
<string>$(CURRENT_PROJECT_VERSION)</string>

Also, please make sure that your project.pbxproj file also contain the following with static values:

MARKETING_VERSION = 1.0;
CURRENT_PROJECT_VERSION = 1;

If any of these info is not correctly linked then it will keep showing this error.

score -1 · Answer 67 · answered Oct 05 '12 at 10:06

-1

Try to clean your project, and Compile.

answered Oct 05 '12 at 10:06

Tom John

99
1
7

score -1 · Answer 68 · answered Mar 30 '19 at 23:35

-1

With CocoaPod, first install and then open the workspace instead of project as specified on CocoaPod website.

$ pod install

$ open YOUR_PROJECT_NAME.xcworkspace

answered Mar 30 '19 at 23:35

Hassan Rahman

4,953
1
34
32

score -2 · Answer 69 · answered Apr 14 '16 at 06:39

-2

In my case

I just removed armv7s and armv64 and build its works.

answered Apr 14 '16 at 06:39

Hardik Mamtora

1,642
17
23

Apple Mach-O Linker Error when compiling for device

69 Answers69

Right way here:

Linked