See this answer.
Is this even the correct approach here
No: you can’t use mismatched versions of glibc as your link command does. You used crt0.o
and ld-linux.so
from new (system-installed) libc, but libc.so.6
from an old (copied from cluster) libc. That is just not going to work.
More Related Contents:
- How to specify non-default shared-library path in GCC Linux? Getting “error while loading shared libraries” when running
- Why does the order in which libraries are linked sometimes cause errors in GCC?
- What is the -fPIE option for position-independent executables in gcc and ld?
- Telling gcc directly to link a library statically
- libpthread.so.0: error adding symbols: DSO missing from command line
- What are the –start-group and –end-group command line options?
- ld cannot find an existing library
- Use both static and dynamically linked libraries in gcc
- combine two GCC compiled .o object files into a third .o file
- GNU gcc/ld – wrapping a call to symbol with caller and callee defined in the same object file
- How can I tell, with something like objdump, if an object file has been built with -fPIC?
- static linking only some libraries
- Compilation fails with “relocation R_X86_64_32 against `.rodata.str1.8′ can not be used when making a shared object”
- How to set the runtime path (-rpath) of an executable with gcc under Mac OSX?
- How to link using GCC without -l nor hardcoding path for a library that does not follow the libNAME.so naming convention?
- What does exactly the warning mean about hidden symbol being referenced by DSO?
- CMake and Static Linking
- undefined reference to symbol even when nm indicates that this symbol is present in the shared library
- correct usage of rpath (relative vs absolute)
- Hiding symbol names in library
- Why doesn’t GCC optimize a*a*a*a*a*a to (a*a*a)*(a*a*a)?
- What does the -all_load linker flag do?
- Preprocessor output
- #pragma comment(lib, “xxx.lib”) equivalent under Linux?
- Compiling problems: cannot find crt1.o
- Build .so file from .c file using gcc command line
- Why does the x86-64 System V calling convention pass args in registers instead of just the stack?
- Understanding GCC’s floating point constants in assembly listing output
- c math linker problems on Ubuntu 11.10 [duplicate]
- Query on -ffunction-section & -fdata-sections options of gcc