I just develop MOIP with ready-made components, but received the error after running.
Showed an error message:
"ld: file not found: /Users/teste/Library/Developer/Xcode/DerivedData/Moip_Store-fakuiehavrpkaeggjvvtbovybkyh/Build/Products/Debug-iphoneos/Moip Store.app/Moip Store
clang: error: linker command failed with exit code 1 (use -v to see invocation)"
site: https://github.com/moip/ios-sdk-sample
Someone solve this problem?
how?
Select your Project and choose your "Moip Store Test" - Target, go to "General" and set your Application as Host Application.
Related
Building a React Native Expo app (prebuild on iOS, not using Expo Go) and running into this esoteric error that I can't seem to find elsewhere on the internet.
I'll post it here for the next unlucky React Native dev, and perhaps I'll find a solution and post that too.
expo run:ios output:
⚠️ (../../Library/Developer/Xcode/DerivedData/MyProject-epxolwjjgmimbdefugnlecrdysuv/Build/Intermediates.noindex/PrecompiledHeaders/MyProject-Bridging-Header-2vyenlvwppgam.dia:1:1)
Command PrecompileSwiftBridgingHeader failed with a nonzero exit code
^ Could not read serialized diagnostics file: error(in target 'MyProject' from project 'MyProject')
❌ error: generate-pch command failed with exit code 1 (use -v to see invocation)
› 1 error(s), and 1 warning(s)
Failed to build iOS project. "xcodebuild" exited with error code 65.
Xcode build output:
<unknown>:0: error: error opening input file '/Users/jh/Code/MyProject/ios/MyProject/MyProject-Bridging-Header.h' (No such file or directory)
<unknown>:0: error: cannot open file '/Users/jh/Library/Developer/Xcode/DerivedData/MyProject-epxolwjjgmimbdefugnlecrdysuv/Build/Intermediates.noindex/PrecompiledHeaders/MyProject-Bridging-Header-e8n926ydzbc0.dia' for diagnostics emission (No such file or directory)
/Users/jh/Library/Developer/Xcode/DerivedData/MyProject-epxolwjjgmimbdefugnlecrdysuv/Build/Intermediates.noindex/PrecompiledHeaders/MyProject-Bridging-Header-e8n926ydzbc0.dia:1:1: warning: Could not read serialized diagnostics file: error("Failed to open diagnostics file") (in target 'MyProject' from project 'MyProject')
Command PrecompileSwiftBridgingHeader failed with a nonzero exit code
Expo SDK version 44. I'm on a 2022 Mac Studio M1.
Okay, found the solution!
I had used npx react-native-rename to rename my project, but it didn't rename the Swift bridging header.
It's located in ios/MyProject/<oldname>-Bridging-Header.h.
renamed: ios/MyProject/OldName-Bridging-Header.h -> ios/MyProject/MyProject-Bridging-Header.h
While I was doing this, I also discovered that several of my bundle identifiers hadn't been moved over either. Do a codebase search for com.yourorganization.youroldbundlename to find & replace those too.
The locations I had to update:
./ios/MyProject.xcodeproj/project.pbxproj
./ios/MyProject/Info.plist
./app.json
I've created a simple project to get myself accustomed to meson, but the build keeps failing.
This is what I did (to set up the environment, and to build):
set CC=clang
set CC_LD=lld
set CFLAGS="--target x86_64-pc-windows-msvc"
meson build
cd build
ninja
My meson.build is as follows:
project('EtaClient', 'c')
src = ['src/main.c', 'src/linkedlist.c']
executable('EtaClient', src)
target = 'x86_64-pc-windows-msvc'
While building, I get the following errors (the obj files are built successfully, but they're not linked and thus the exe isn't built):
LINK : warning LNK4044: unrecognized option '/-subsystem'; ignored
LINK : fatal error LNK1181: cannot open input file 'console.obj'
clang: error: linker command failed with exit code 1181 (use -v to see invocation)
When I look in my build.ninja to see what's going on, I find:
build EtaClient.exe | EtaClient.pdb: c_LINKER EtaClient.exe.p/src_main.c.obj EtaClient.exe.p/src_linkedlist.c.obj
LINK_ARGS = "-Wl,/nologo" "-Wl,/release" "-Wl,/nologo" "-Wl,/DEBUG" "-Wl,/PDB:EtaClient.pdb" "-Wl,--subsystem,console" "-lkernel32" "-luser32" "-lgdi32" "-lwinspool" "-lshell32" "-lole32" "-loleaut32" "-luuid" "-lcomdlg32" "-ladvapi32"
I replace "-Wl,--subsystem,console" with "-Wl,/subsystem:console", and the build compiles successfully, but I have to manually make this edit each time I modify my meson.build.
Could someone tell me why this happens, and how to set up meson to generate the correct flag?
Thanks in advance.
use clang-cl instead of clang and leave out the defintion of the linker when you are on windows
set CC=clang-cl
set CFLAGS="--target x86_64-pc-windows-msvc"
meson build
cd build
ninja
see
https://github.com/mesonbuild/meson/issues/4232
This question already has answers here:
ld: file not found: linker command failed with exit code 1
(11 answers)
Closed 5 years ago.
I KNOW what this error message
"Linker command failed with exit code 1 (use -v to see invocation"
means. I have duplicate symbols.
What I DON'T know is what "use - v to see invocation" means.
How do I actually use -v? In Terminal or where? Please someone, give me an example of its actual use.
Thanks for your help.
I found a way to get the error info: Control-click on the red error indicator (at left), then select Show Error Log, which gives the complete information.
(Meanwhile the "Use -v" message remains useless.)
What I have done after 2 days of reading stack overflow:
Keywords to problem:
"Apple-Mach-O Linker Error",
"libGGLCore.a(Clientanalytics.pb.o,Icore.pb.o,Jspb.pb.o,LogsAnnotations.pb.o
...)", "_OBJC_CLASS_$_GSDK_PBExtensionRegistry"
,"_OBJC_CLASS_$_GSDK_PBGeneratedEnumDescriptor" ....
I Don't use pod. Manually Download files from Github
So I am stuck. How do I solve the problem(s) displayed in the image below:
clang: error: linker command failed with exit code 1 (use -v to see invocation)
Did you download all the dependent pods? To make GCM work, you need Google, GoogleCloudMessaging, GGLInstanceID, GoogleInterchangeUtilities, GoogleIPhoneUtilities, GoogleNetworkingUtilities, GoogleSymbolUtilities, and GoogleUtilities.
There could be various errors in your code as per your description. Some of the possibilities are:
1. Please read this
2. Importing QuartzCore in the project might fix the issue too.
3. Cleaning the project and restarting might help you too.
4. Changing the architecture of the project from armv6 to armv7 or arm64 could help too.
5. Moving the linked library of GCM to another folder also causes this issue. Please check it out too.
I have problems with Swift Compiler:
I created new project for iOs on latest Xcode 6 and tried to build - recieved 2 errors with ViewController.swift and AppDelegate.swift.
<unknown>:0: error: unable to execute command: Segmentation fault: 11
<unknown>:0: error: swift frontend command failed due to signal (use -v to see invocation)
<unknown>:0: error: unable to execute command: Bus error: 10
<unknown>:0: error: swift frontend command failed due to signal (use -v to see invocation)
I can post a full logs if if it is necessary.
What should i do? Thanks.
I have faced a similar issue while working with a swift project. I found this on Apple Support Website. It says that this type of error occurs when you tried to access an non-existent/inaccessible memory address. To solve the issue you can quit unused applications or even restart the mac which will probably help you.