Linking a C program directly with ld fails with undefined reference to `__libc_csu_fini`

by

/usr/lib/libc.so is a linker script which tells the linker to pull in the shared library /lib/libc.so.6, and a non-shared portion, /usr/lib/libc_nonshared.a.

__libc_csu_init and __libc_csu_fini come from /usr/lib/libc_nonshared.a. They’re not being found because references to symbols in non-shared libraries need to appear before the archive that defines them on the linker line. In your case, /usr/lib/crt1.o (which references them) appears after /usr/lib/libc.so (which pulls them in), so it doesn’t work.

Fixing the order on the link line will get you a bit further, but then you’ll probably get a new problem, where __libc_csu_init and __libc_csu_fini (which are now found) can’t find _init and _fini. In order to call C library functions, you should also link /usr/lib/crti.o (after crt1.o but before the C library) and /usr/lib/crtn.o (after the C library), which contain initialisation and finalisation code.

Adding those should give you a successfully linked executable. It still won’t work, because it uses the dynamically linked C library without specifying what the dynamic linker is. You’ll need to tell the linker that as well, with something like -dynamic-linker /lib/ld-linux.so.2 (for 32-bit x86 at least; the name of the standard dynamic linker varies across platforms).

If you do all that (essentially as per Rob’s answer), you’ll get something that works in simple cases. But you may come across further problems with more complex code, as GCC provides some of its own library routines which may be needed if your code uses certain features. These will be buried somewhere deep inside the GCC installation directories…

You can see what gcc is doing by running it with either the -v option (which will show you the commands it invokes as it runs), or the -### option (which just prints the commands it would run, with all of the arguments quotes, but doesn’t actually run anything). The output will be confusing unless you know that it usually invokes ld indirectly via one of its own components, collect2 (which is used to glue in C++ constructor calls at the right point).

More Related Contents:

  1. Why does the order of ‘-l’ option in gcc matter? [duplicate]
  2. Linking against older symbol version in a .so file
  3. How to link to a different libc file?
  4. Why is this code using strlen heavily 6.5x slower with GCC optimizations enabled?
  5. Compiling without libc
  6. How to make weak linking work with GCC?
  7. Why am I getting a gcc “undefined reference” error trying to create shared objects?
  8. difference between %ms and %s scanf
  9. gcc will not properly include math.h
  10. Can I mix static and shared-object libraries when linking?
  11. `bash: ./a.out: No such file or directory` on running executable produced by `ld`
  12. How to compile my own glibc C standard library from source and use it?
  13. Why do I have to define LD_LIBRARY_PATH with an export every time I run my application?
  14. How to make gcc link strong symbol in static library to overwrite weak symbol?
  15. Get the start and end address of text section in an executable
  16. Check glibc version for a particular gcc compiler
  17. An alternative for the deprecated __malloc_hook functionality of glibc
  18. c math linker problems on Ubuntu 11.10 [duplicate]
  19. Override weak symbols in static library
  20. Is accessing the “value” of a linker script variable undefined behavior in C?
  21. Query on -ffunction-section & -fdata-sections options of gcc
  22. What do R_X86_64_32S and R_X86_64_64 relocation mean?
  23. Why aren’t my compile guards preventing multiple definition inclusions?
  24. Where is PATH_MAX defined in Linux?
  25. How to verify if a void pointer (void *) is one of two data types?
  26. typeof operator in C
  27. How to place a variable at a given absolute address in memory (with GCC)
  28. c99 goto past initialization
  29. Bitshift and integer promotion?
  30. Compiling a C program that uses OpenGl in Mac OS X

Leave a Comment