You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I run verifyProblem on a problem package, I get an error when trying to compile any c++ program.
It appears that there is an attempt to link a static library. Per the information I'm finding online, it appears that OSX is known to know have these libraries built in a static format to link against.
error
ERROR in submissions: Compile error for AC submission jeffi.cpp (C++):
ld: library not found for -lcrt0.o
clang: error: linker command failed with exit code 1 (use -v to see invocation)
The text was updated successfully, but these errors were encountered:
More specifically it looks like the effort is to compile the code statically, and that this is what leads to this object file trying to be linked in statically.
More specifically it looks like the effort is to compile the code statically, and that this is what leads to this object file trying to be linked in statically.
If you remove the -static flag from the compilation step of C++ in your configuration, does it work then?
You can modify it in the languages.yaml file under config.
When I run verifyProblem on a problem package, I get an error when trying to compile any c++ program.
It appears that there is an attempt to link a static library. Per the information I'm finding online, it appears that OSX is known to know have these libraries built in a static format to link against.
error
ERROR in submissions: Compile error for AC submission jeffi.cpp (C++):
ld: library not found for -lcrt0.o
clang: error: linker command failed with exit code 1 (use -v to see invocation)
The text was updated successfully, but these errors were encountered: