VS code error : exited with code 1 in mac os - visual-studio-code

Running] cd "/Users/abhiaryan/Desktop/c+++/" && g++ demo.cpp -o demo && "/Users/abhiaryan/Desktop/c+++/"demo
Undefined symbols for architecture arm64:
"_main", referenced from:
implicit entry/start for main executable
ld: symbol(s) not found for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
[Done] exited with code=1 in 0.052 seconds
the screen shots are here

go to settings > search for run > select save file before run
It resolved my same issue.

Related

clang: error: linker command failed with exit code 1 (use -v to see invocation) in Visual Studio Code

I want to run a c++ code in Visual Studio Code but every time I get this error
Undefined symbols for architecture x86_64:
"_main", referenced from:
implicit entry/start for main executable
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
I tried several methods with editing the main function but non worked

How to fix "undefined symbols" for compiling mplayer

When I try to compile mplayer on MacOS (12.4) I get an error
Undefined symbols for architecture x86_64:
"_x264_encoder_open_163", referenced from:
_X264_init in libavcodec.a(libx264.o)
Undefined symbols for architecture x86_64:
"_x264_encoder_open_163", referenced from:
_X264_init in libavcodec.a(libx264.o)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [mencoder] Error 1
make: *** Waiting for unfinished jobs....
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [mplayer] Error 1
Any ideas how to fix this?
The issue seem to have been with the x264 library.
And for some reasons a first reinstall of x264 did not work. But when (after some other attempts to install what is missing) I did again
brew reinstall x264
something was compiled. But then I did run the following three commands in exactly this order:
./configure
make clean
make
And to my total surprise it did compile finally mplayer. And it works (and fixes a bug only I seem to have).

getting exit code error when install any new pod

i getting exit code error when i try to install any new pod and that's never happend
ld: warning: directory not found for option '-F/Users/hamadaraouf/Library/Developer/Xcode/DerivedData/بورسعيد-eypkqarpocnxxwbqicnkmsfprobc/Build/Products/Debug-iphoneos/DTGradientButton'
ld: framework not found DTGradientButton
clang: error: linker command failed with exit code 1 (use -v to see invocation)
[https://i.stack.imgur.com/Arwos.png][1]
thank you

ld: framework not found -Accelerate clang: error: linker command failed with exit code 1

i am trying to implement Apptentive SDK in my iPhone application as per the guide document.
everything was gone good. but at last point of implementing SDK found error.that is Accelerate framework directory path not fount like that a error occurs
ld: framework not found -Accelerate
clang: error: linker command failed with exit code 1 (use -v to see invocation)
clang: error: linker command failed with exit code 1 (use -v to see invocation)
it may be Xcode version in-compatability issues, if we change directory path it may works

error: linker command failed with exit code 1 (use -v to see invocation)

When I use GooglePluse Library file it works on iphone simulator.
But when I run it on device it gives the following Error:
ld: duplicate symbol _OBJC_CLASS_$_GooglePlusSignIn in /Pratik workspace/Fitness
app/Fitness Ap/Fitness/lib/libGooglePlusUniversal.a(GooglePlusSignIn.o) and /Pratik
workspace/Fitness app/Fitness Ap/Fitness/lib/libGooglePlus.a(GooglePlusSignIn.o) for
architecture armv7 clang: error: linker command failed with exit code 1 (use -v to
see invocation)
you will have 2 files with same name that's why it is giving error like this.
go in targets ->Build Phases ->Compile sources and try to remove GooglePlusSignIn file.it will be there i think.
then run again and let me know whether it is working or not..!!!
Happy coding...!!!!