Override weak symbols in static library

by

This is a byproduct of the way that .a libraries work – they’re simply a collection of .o files.

What happens at compile link time is that the first reference to the name gets resolved to the weak reference and the strong name never gets a look in.

You can test this yourself by actually making both the identical name and strong and you’ll see exactly the same behaviour.

If you want the strong references resolved first, then put them earlier in the archive, or create a separate strong archive and link that first in the link-line.

While not directly applicable to your case, as you’re using an embedded environment, weak vs. strong references come into force properly when creating/consuming .so dynamic libraries rather than .a archives. When you create a .so, all the weak references that make up the library will not generate an error, and only one of them will be used for the final product; and if there is a strong definition anywhere then it gets used rather than any of the weak ones (this only works properly if, when you’re creating a .so, you link all the .o files that make it up separately, or use the --whole-archive when creating the .so if linking to a .a).

More Related Contents:

  1. Why does the order of ‘-l’ option in gcc matter? [duplicate]
  2. Why am I getting a gcc “undefined reference” error trying to create shared objects?
  3. Linking against older symbol version in a .so file
  4. Why do I have to define LD_LIBRARY_PATH with an export every time I run my application?
  5. How to make gcc link strong symbol in static library to overwrite weak symbol?
  6. Get the start and end address of text section in an executable
  7. Linking a C program directly with ld fails with undefined reference to `__libc_csu_fini`
  8. How to link to a different libc file?
  9. Removing trailing newline character from fgets() input
  10. C undefined behavior. Strict aliasing rule, or incorrect alignment? [duplicate]
  11. Order of local variable allocation on the stack
  12. Undefined reference to `pow’ and `floor’
  13. Adding leading underscores to assembly symbols with GCC on Win32?
  14. What is the difference between C, C99, ANSI C and GNU C?
  15. aligned malloc() in GCC?
  16. Why didn’t gcc (or glibc) implement _s functions?
  17. How to access C variable for inline assembly manipulation?
  18. How to check if a given file descriptor stored in a variable is still valid?
  19. Detecting 64bit compile in C
  20. C preprocessor: expand macro in a #warning
  21. multi-word addition using the carry flag
  22. Inline assembly that clobbers the red zone
  23. GCC 4.7 Source Character Encoding and Execution Character Encoding For String Literals?
  24. Tool to analyze size of ELF sections and symbol
  25. Process Linkage Table and Global Offset Table
  26. Why both clang and gcc only give a warning when there is a space after backslash if C standard says that whitespace is forbidden?
  27. How does GCC behave if passed conflicting compiler flags?
  28. why am I not getting an “used uninitialized” warning from gcc in this trivial example? [duplicate]
  29. & operator optional in function pointer assignment
  30. How do I compile the asm generated by GCC?

Leave a Comment