168) * BFD_RELOC_SPARC_LOX10: howto manager. (line 181) * BFD_RELOC_SPARC_M44: howto manager. (line 183) * BFD_RELOC_SPARC_OLO10: howto manager. (line 165) * BFD_RELOC_SPARC_PC10: howto manager. (line 138) * BFD_RELOC_SPARC_PC22: howto manager. (line 139) * BFD_RELOC_SPARC_PC_HH22: howto manager. (line 169) * BFD_RELOC_SPARC_PC_HM10: howto manager. (line 170) * BFD_RELOC_SPARC_PC_LM22: howto manager. (line 171) * BFD_RELOC_SPARC_PLT32: howto manager. (line 178) * BFD_RELOC_SPARC_PLT64: howto manager. (line 179) * BFD_RELOC_SPARC_REGISTER: howto manager. (line 185) * BFD_RELOC_SPARC_RELATIVE: howto manager. (line 144) * BFD_RELOC_SPARC_REV32: howto manager. (line 188) * BFD_RELOC_SPARC_TLS_DTPMOD32: howto manager. (line 209) * BFD_RELOC_SPARC_TLS_DTPMOD64: howto manager. (line 210) * BFD_RELOC_SPARC_TLS_DTPOFF32: howto manager. (line 211) * BFD_RELOC_SPARC_TLS_DTPOFF64: howto manager. (line 212) * BFD_RELOC_SPARC_TLS_GD_ADD: howto manager. (line 193) * BFD_RELOC_SPARC_TLS_GD_CALL: howto manager. (line 194) * BFD_RELOC_SPARC_TLS_GD_HI22: howto manager. (line 191) * BFD_RELOC_SPARC_TLS_GD_LO10: howto manager. (line 192) * BFD_RELOC_SPARC_TLS_IE_ADD: howto manager. (line 206) * BFD_RELOC_SPARC_TLS_IE_HI22: howto manager. (line 202) * BFD_RELOC_SPARC_TLS_IE_LD: howto manager. (line 204) * BFD_RELOC_SPARC_TLS_IE_LDX: howto manager. (line 205) * BFD_RELOC_SPARC_TLS_IE_LO10: howto manager. (line 203) * BFD_RELOC_SPARC_TLS_LDM_ADD: howto manager. (line 197) * BFD_RELOC_SPARC_TLS_LDM_CALL: howto manager. (line 198) * BFD_RELOC_SPARC_TLS_LDM_HI22: howto manager. (line 195) * BFD_RELOC_SPARC_TLS_LDM_LO10: howto manager. (line 196) * BFD_RELOC_SPARC_TLS_LDO_ADD: howto manager. (line 201) * BFD_RELOC_SPARC_TLS_LDO_HIX22: howto manager. (line 199) * BFD_RELOC_SPARC_TLS_LDO_LOX10: howto manager. (line 200) * BFD_RELOC_SPARC_TLS_LE_HIX22: howto manager. (line 207) * BFD_RELOC_SPARC_TLS_LE_LOX10: howto manager. (line 208) * BFD_RELOC_SPARC_TLS_TPOFF32: howto manager. (line 213) * BFD_RELOC_SPARC_TLS_TPOFF64: howto manager. (line 214) * BFD_RELOC_SPARC_UA16: howto manager. (line 145) * BFD_RELOC_SPARC_UA32: howto manager. (line 146) * BFD_RELOC_SPARC_UA64: howto manager. (line 147) * BFD_RELOC_SPARC_WDISP16: howto manager. (line 172) * BFD_RELOC_SPARC_WDISP19: howto manager. (line 173) * BFD_RELOC_SPARC_WDISP22: howto manager. (line 132) * BFD_RELOC_SPARC_WPLT30: howto manager. (line 140) * BFD_RELOC_SPU_ADD_PIC: howto manager. (line 231) * BFD_RELOC_SPU_HI16: howto manager. (line 228) * BFD_RELOC_SPU_IMM10: howto manager. (line 219) * BFD_RELOC_SPU_IMM10W: howto manager. (line 220) * BFD_RELOC_SPU_IMM16: howto manager. (line 221) * BFD_RELOC_SPU_IMM16W: howto manager. (line 222) * BFD_RELOC_SPU_IMM18: howto manager. (line 223) * BFD_RELOC_SPU_IMM7: howto manager. (line 217) * BFD_RELOC_SPU_IMM8: howto manager. (line 218) * BFD_RELOC_SPU_LO16: howto manager. (line 227) * BFD_RELOC_SPU_PCREL16: howto manager. (line 226) * BFD_RELOC_SPU_PCREL9a: howto manager. (line 224) * BFD_RELOC_SPU_PCREL9b: howto manager. (line 225) * BFD_RELOC_SPU_PPU32: howto manager. (line 229) * BFD_RELOC_SPU_PPU64: howto manager. (line 230) * BFD_RELOC_THUMB_PCREL_BLX: howto manager. (line 703) * BFD_RELOC_THUMB_PCREL_BRANCH12: howto manager. (line 717) * BFD_RELOC_THUMB_PCREL_BRANCH20: howto manager. (line 718) * BFD_RELOC_THUMB_PCREL_BRANCH23: howto manager. (line 719) * BFD_RELOC_THUMB_PCREL_BRANCH25: howto manager. (line 720) * BFD_RELOC_THUMB_PCREL_BRANCH7: howto manager. (line 715) * BFD_RELOC_THUMB_PCREL_BRANCH9: howto manager. (line 716) * BFD_RELOC_TIC30_LDP: howto manager. (line 1334) * BFD_RELOC_TIC54X_16_OF_23: howto manager. (line 1352) * BFD_RELOC_TIC54X_23: howto manager. (line 1349) * BFD_RELOC_TIC54X_MS7_OF_23: howto manager. (line 1357) * BFD_RELOC_TIC54X_PARTLS7: howto manager. (line 1339) * BFD_RELOC_TIC54X_PARTMS9: howto manager. (line 1344) * bfd_reloc_type_lookup: howto manager. (line 2392) * BFD_RELOC_V850_16_GOT: howto manager. (line 1290) * BFD_RELOC_V850_16_GOTOFF: howto manager. (line 1314) * BFD_RELOC_V850_16_PCREL: howto manager. (line 1260) * BFD_RELOC_V850_16_S1: howto manager. (line 1278) * BFD_RELOC_V850_16_SPLIT_OFFSET: howto manager. (line 1275) * BFD_RELOC_V850_17_PCREL: howto manager. (line 1263) * BFD_RELOC_V850_22_PCREL: howto manager. (line 1195) * BFD_RELOC_V850_22_PLT_PCREL: howto manager. (line 1296) * BFD_RELOC_V850_23: howto manager. (line 1266) * BFD_RELOC_V850_32_ABS: howto manager. (line 1272) * BFD_RELOC_V850_32_GOT: howto manager. (line 1293) * BFD_RELOC_V850_32_GOTOFF: howto manager. (line 1317) * BFD_RELOC_V850_32_GOTPCREL: howto manager. (line 1287) * BFD_RELOC_V850_32_PCREL: howto manager. (line 1269) * BFD_RELOC_V850_32_PLT_PCREL: howto manager. (line 1299) * BFD_RELOC_V850_9_PCREL: howto manager. (line 1192) * BFD_RELOC_V850_ALIGN: howto manager. (line 1253) * BFD_RELOC_V850_CALLT_15_16_OFFSET: howto manager. (line 1284) * BFD_RELOC_V850_CALLT_16_16_OFFSET: howto manager. (line 1244) * BFD_RELOC_V850_CALLT_6_7_OFFSET: howto manager. (line 1241) * BFD_RELOC_V850_CODE: howto manager. (line 1320) * BFD_RELOC_V850_COPY: howto manager. (line 1302) * BFD_RELOC_V850_DATA: howto manager. (line 1323) * BFD_RELOC_V850_GLOB_DAT: howto manager. (line 1305) * BFD_RELOC_V850_JMP_SLOT: howto manager. (line 1308) * BFD_RELOC_V850_LO16_S1: howto manager. (line 1281) * BFD_RELOC_V850_LO16_SPLIT_OFFSET: howto manager. (line 1256) * BFD_RELOC_V850_LONGCALL: howto manager. (line 1247) * BFD_RELOC_V850_LONGJUMP: howto manager. (line 1250) * BFD_RELOC_V850_RELATIVE: howto manager. (line 1311) * BFD_RELOC_V850_SDA_15_16_OFFSET: howto manager. (line 1201) * BFD_RELOC_V850_SDA_16_16_OFFSET: howto manager. (line 1198) * BFD_RELOC_V850_SDA_16_16_SPLIT_OFFSET: howto manager. (line 1233) * BFD_RELOC_V850_TDA_16_16_OFFSET: howto manager. (line 1223) * BFD_RELOC_V850_TDA_4_4_OFFSET: howto manager. (line 1230) * BFD_RELOC_V850_TDA_4_5_OFFSET: howto manager. (line 1226) * BFD_RELOC_V850_TDA_6_8_OFFSET: howto manager. (line 1212) * BFD_RELOC_V850_TDA_7_7_OFFSET: howto manager. (line 1220) * BFD_RELOC_V850_TDA_7_8_OFFSET: howto manager. (line 1216) * BFD_RELOC_V850_ZDA_15_16_OFFSET: howto manager. (line 1208) * BFD_RELOC_V850_ZDA_16_16_OFFSET: howto manager. (line 1205) * BFD_RELOC_V850_ZDA_16_16_SPLIT_OFFSET: howto manager. (line 1237) * BFD_RELOC_VAX_GLOB_DAT: howto manager. (line 2157) * BFD_RELOC_VAX_JMP_SLOT: howto manager. (line 2158) * BFD_RELOC_VAX_RELATIVE: howto manager. (line 2159) * BFD_RELOC_VPE4KMATH_DATA: howto manager. (line 1796) * BFD_RELOC_VPE4KMATH_INSN: howto manager. (line 1797) * BFD_RELOC_VTABLE_ENTRY: howto manager. (line 1801) * BFD_RELOC_VTABLE_INHERIT: howto manager. (line 1800) * BFD_RELOC_X86_64_32S: howto manager. (line 538) * BFD_RELOC_X86_64_COPY: howto manager. (line 533) * BFD_RELOC_X86_64_DTPMOD64: howto manager. (line 539) * BFD_RELOC_X86_64_DTPOFF32: howto manager. (line 544) * BFD_RELOC_X86_64_DTPOFF64: howto manager. (line 540) * BFD_RELOC_X86_64_GLOB_DAT: howto manager. (line 534) * BFD_RELOC_X86_64_GOT32: howto manager. (line 531) * BFD_RELOC_X86_64_GOT64: howto manager. (line 549) * BFD_RELOC_X86_64_GOTOFF64: howto manager. (line 547) * BFD_RELOC_X86_64_GOTPC32: howto manager. (line 548) * BFD_RELOC_X86_64_GOTPC32_TLSDESC: howto manager. (line 554) * BFD_RELOC_X86_64_GOTPC64: howto manager. (line 551) * BFD_RELOC_X86_64_GOTPCREL: howto manager. (line 537) * BFD_RELOC_X86_64_GOTPCREL64: howto manager. (line 550) * BFD_RELOC_X86_64_GOTPLT64: howto manager. (line 552) * BFD_RELOC_X86_64_GOTTPOFF: howto manager. (line 545) * BFD_RELOC_X86_64_IRELATIVE: howto manager. (line 557) * BFD_RELOC_X86_64_JUMP_SLOT: howto manager. (line 535) * BFD_RELOC_X86_64_PLT32: howto manager. (line 532) * BFD_RELOC_X86_64_PLTOFF64: howto manager. (line 553) * BFD_RELOC_X86_64_RELATIVE: howto manager. (line 536) * BFD_RELOC_X86_64_TLSDESC: howto manager. (line 556) * BFD_RELOC_X86_64_TLSDESC_CALL: howto manager. (line 555) * BFD_RELOC_X86_64_TLSGD: howto manager. (line 542) * BFD_RELOC_X86_64_TLSLD: howto manager. (line 543) * BFD_RELOC_X86_64_TPOFF32: howto manager. (line 546) * BFD_RELOC_X86_64_TPOFF64: howto manager. (line 541) * BFD_RELOC_XC16X_PAG: howto manager. (line 2151) * BFD_RELOC_XC16X_POF: howto manager. (line 2152) * BFD_RELOC_XC16X_SEG: howto manager. (line 2153) * BFD_RELOC_XC16X_SOF: howto manager. (line 2154) * BFD_RELOC_XSTORMY16_12: howto manager. (line 2143) * BFD_RELOC_XSTORMY16_24: howto manager. (line 2144) * BFD_RELOC_XSTORMY16_FPTR16: howto manager. (line 2145) * BFD_RELOC_XSTORMY16_REL_12: howto manager. (line 2142) * BFD_RELOC_XTENSA_ASM_EXPAND: howto manager. (line 2263) * BFD_RELOC_XTENSA_ASM_SIMPLIFY: howto manager. (line 2268) * BFD_RELOC_XTENSA_DIFF16: howto manager. (line 2210) * BFD_RELOC_XTENSA_DIFF32: howto manager. (line 2211) * BFD_RELOC_XTENSA_DIFF8: howto manager. (line 2209) * BFD_RELOC_XTENSA_GLOB_DAT: howto manager. (line 2199) * BFD_RELOC_XTENSA_JMP_SLOT: howto manager. (line 2200) * BFD_RELOC_XTENSA_OP0: howto manager. (line 2257) * BFD_RELOC_XTENSA_OP1: howto manager. (line 2258) * BFD_RELOC_XTENSA_OP2: howto manager. (line 2259) * BFD_RELOC_XTENSA_PLT: howto manager. (line 2204) * BFD_RELOC_XTENSA_RELATIVE: howto manager. (line 2201) * BFD_RELOC_XTENSA_RTLD: howto manager. (line 2194) * BFD_RELOC_XTENSA_SLOT0_ALT: howto manager. (line 2239) * BFD_RELOC_XTENSA_SLOT0_OP: howto manager. (line 2219) * BFD_RELOC_XTENSA_SLOT10_ALT: howto manager. (line 2249) * BFD_RELOC_XTENSA_SLOT10_OP: howto manager. (line 2229) * BFD_RELOC_XTENSA_SLOT11_ALT: howto manager. (line 2250) * BFD_RELOC_XTENSA_SLOT11_OP: howto manager. (line 2230) * BFD_RELOC_XTENSA_SLOT12_ALT: howto manager. (line 2251) * BFD_RELOC_XTENSA_SLOT12_OP: howto manager. (line 2231) * BFD_RELOC_XTENSA_SLOT13_ALT: howto manager. (line 2252) * BFD_RELOC_XTENSA_SLOT13_OP: howto manager. (line 2232) * BFD_RELOC_XTENSA_SLOT14_ALT: howto manager. (line 2253) * BFD_RELOC_XTENSA_SLOT14_OP: howto manager. (line 2233) * BFD_RELOC_XTENSA_SLOT1_ALT: howto manager. (line 2240) * BFD_RELOC_XTENSA_SLOT1_OP: howto manager. (line 2220) * BFD_RELOC_XTENSA_SLOT2_ALT: howto manager. (line 2241) * BFD_RELOC_XTENSA_SLOT2_OP: howto manager. (line 2221) * BFD_RELOC_XTENSA_SLOT3_ALT: howto manager. (line 2242) * BFD_RELOC_XTENSA_SLOT3_OP: howto manager. (line 2222) * BFD_RELOC_XTENSA_SLOT4_ALT: howto manager. (line 2243) * BFD_RELOC_XTENSA_SLOT4_OP: howto manager. (line 2223) * BFD_RELOC_XTENSA_SLOT5_ALT: howto manager. (line 2244) * BFD_RELOC_XTENSA_SLOT5_OP: howto manager. (line 2224) * BFD_RELOC_XTENSA_SLOT6_ALT: howto manager. (line 2245) * BFD_RELOC_XTENSA_SLOT6_OP: howto manager. (line 2225) * BFD_RELOC_XTENSA_SLOT7_ALT: howto manager. (line 2246) * BFD_RELOC_XTENSA_SLOT7_OP: howto manager. (line 2226) * BFD_RELOC_XTENSA_SLOT8_ALT: howto manager. (line 2247) * BFD_RELOC_XTENSA_SLOT8_OP: howto manager. (line 2227) * BFD_RELOC_XTENSA_SLOT9_ALT: howto manager. (line 2248) * BFD_RELOC_XTENSA_SLOT9_OP: howto manager. (line 2228) * BFD_RELOC_XTENSA_TLS_ARG: howto manager. (line 2278) * BFD_RELOC_XTENSA_TLS_CALL: howto manager. (line 2279) * BFD_RELOC_XTENSA_TLS_DTPOFF: howto manager. (line 2275) * BFD_RELOC_XTENSA_TLS_FUNC: howto manager. (line 2277) * BFD_RELOC_XTENSA_TLS_TPOFF: howto manager. (line 2276) * BFD_RELOC_XTENSA_TLSDESC_ARG: howto manager. (line 2274) * BFD_RELOC_XTENSA_TLSDESC_FN: howto manager. (line 2273) * BFD_RELOC_Z80_DISP8: howto manager. (line 2282) * BFD_RELOC_Z8K_CALLR: howto manager. (line 2288) * BFD_RELOC_Z8K_DISP7: howto manager. (line 2285) * BFD_RELOC_Z8K_IMM4L: howto manager. (line 2291) * bfd_scan_arch: Architectures. (line 437) * bfd_scan_vma: BFD front end. (line 532) * bfd_seach_for_target: bfd_target. (line 507) * bfd_section_already_linked: Writing the symbol table. (line 55) * bfd_section_list_clear: section prototypes. (line 8) * bfd_sections_find_if: section prototypes. (line 176) * bfd_set_arch_info: Architectures. (line 478) * bfd_set_archive_head: Archives. (line 69) * bfd_set_default_target: bfd_target. (line 446) * bfd_set_error: BFD front end. (line 342) * bfd_set_error_handler: BFD front end. (line 384) * bfd_set_error_program_name: BFD front end. (line 393) * bfd_set_file_flags: BFD front end. (line 452) * bfd_set_format: Formats. (line 68) * bfd_set_gp_size: BFD front end. (line 522) * bfd_set_private_flags: BFD front end. (line 599) * bfd_set_reloc: BFD front end. (line 442) * bfd_set_section_contents: section prototypes. (line 207) * bfd_set_section_flags: section prototypes. (line 140) * bfd_set_section_size: section prototypes. (line 193) * bfd_set_start_address: BFD front end. (line 501) * bfd_set_symtab: symbol handling functions. (line 60) * bfd_symbol_info: symbol handling functions. (line 130) * bfd_target_list: bfd_target. (line 498) * bfd_write_bigendian_4byte_int: Internal. (line 13) * bfd_zalloc: Opening and Closing. (line 232) * bfd_zalloc2: Opening and Closing. (line 241) * coff_symbol_type: coff. (line 244) * core_file_matches_executable_p: Core Files. (line 39) * find_separate_debug_file: Opening and Closing. (line 283) * generic_core_file_matches_executable_p: Core Files. (line 49) * get_debug_link_info: Opening and Closing. (line 264) * Hash tables: Hash Tables. (line 6) * internal object-file format: Canonical format. (line 11) * Linker: Linker Functions. (line 6) * Other functions: BFD front end. (line 614) * separate_debug_file_exists: Opening and Closing. (line 274) * struct bfd_iovec: BFD front end. (line 817) * target vector (_bfd_final_link): Performing the Final Link. (line 6) * target vector (_bfd_link_add_symbols): Adding Symbols to the Hash Table. (line 6) * target vector (_bfd_link_hash_table_create): Creating a Linker Hash Table. (line 6) * The HOWTO Macro: typedef arelent. (line 288) * what is it?: Overview. (line 6)  Tag Table: Node: Top1089 Node: Overview1428 Node: History2479 Node: How It Works3425 Node: What BFD Version 2 Can Do4968 Node: BFD information loss6283 Node: Canonical format8815 Node: BFD front end13187 Node: Memory Usage45266 Node: Initialization46494 Node: Sections46953 Node: Section Input47436 Node: Section Output48801 Node: typedef asection51287 Node: section prototypes76599 Node: Symbols86279 Node: Reading Symbols87874 Node: Writing Symbols88981 Node: Mini Symbols90690 Node: typedef asymbol91664 Node: symbol handling functions97723 Node: Archives103065 Node: Formats106791 Node: Relocations109739 Node: typedef arelent110466 Node: howto manager126102 Node: Core Files202471 Node: Targets204509 Node: bfd_target206479 Node: Architectures228872 Node: Opening and Closing252252 Node: Internal263708 Node: File Caching270041 Node: Linker Functions271955 Node: Creating a Linker Hash Table273628 Node: Adding Symbols to the Hash Table275366 Node: Differing file formats276266 Node: Adding symbols from an object file277991 Node: Adding symbols from an archive280142 Node: Performing the Final Link283071 Node: Information provided by the linker284313 Node: Relocating the section contents285467 Node: Writing the symbol table287218 Node: Hash Tables291233 Node: Creating and Freeing a Hash Table292431 Node: Looking Up or Entering a String293681 Node: Traversing a Hash Table294934 Node: Deriving a New Hash Table Type295723 Node: Define the Derived Structures296789 Node: Write the Derived Creation Routine297870 Node: Write Other Derived Routines300494 Node: BFD back ends301809 Node: What to Put Where302079 Node: aout302259 Node: coff308577 Node: elf337010 Node: mmo337411 Node: File layout338339 Node: Symbol-table343986 Node: mmo section mapping347755 Node: GNU Free Documentation License351407 Node: BFD Index376490  End Tag Table This is the file .../info/dir, which contains the topmost node of the Info hierarchy, called (dir)Top. The first time you invoke Info you start off looking at this node.  File: dir, Node: Top This is the top of the INFO tree This (the Directory node) gives a menu of major topics. Typing "q" exits, "?" lists all Info commands, "d" returns here, "h" gives a primer for first-timers, "mEmacs" visits the Emacs manual, etc. In Emacs, you can click mouse button 2 on a menu item or cross reference to select it. * Menu: GNU libraries * gmp: (gmp). GNU Multiple Precision Arithmetic Library. Individual utilities * addr2line: (binutils)addr2line. Convert addresses to file and line. * ar: (binutils)ar. Create, modify, and extract from archives. * c++filt: (binutils)c++filt. Filter to demangle encoded C++ symbols. * cxxfilt: (binutils)c++filt. MS-DOS name for c++filt. * dlltool: (binutils)dlltool. Create files needed to build and use DLLs. * elfedit: (binutils)elfedit. Update the ELF header of ELF files. * nlmconv: (binutils)nlmconv. Converts object code into an NLM. * nm: (binutils)nm. List symbols from object files. * objcopy: (binutils)objcopy. Copy and translate object files. * objdump: (binutils)objdump. Display information from object files. * ranlib: (binutils)ranlib. Generate index to archive contents. * readelf: (binutils)readelf. Display the contents of ELF format files. * size: (binutils)size. List section sizes and total size. * strings: (binutils)strings. List printable strings from files. * strip: (binutils)strip. Discard symbols. * windmc: (binutils)windmc. Generator for Windows message resources. * windres: (binutils)windres. Manipulate Windows resources. Software development * As: (as). The GNU assembler. * Bfd: (bfd). The Binary File Descriptor library. * Binutils: (binutils). The GNU binary utilities. * Gas: (as). The GNU assembler. * Ld: (ld). The GNU linker. * gprof: (gprof). Profiling your program's execution Software libraries * mpfr: (mpfr). Multiple Precision Floating-Point Reliable Library. This is ld.info, produced by makeinfo version 4.8 from ld.texinfo. INFO-DIR-SECTION Software development START-INFO-DIR-ENTRY * Ld: (ld). The GNU linker. END-INFO-DIR-ENTRY This file documents the GNU linker LD (GNU Binutils) version 2.21. Copyright (C) 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009 Free Software Foundation, Inc. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License".  File: ld.info, Node: Top, Next: Overview, Up: (dir) LD ** This file documents the GNU linker ld (GNU Binutils) version 2.21. This document is distributed under the terms of the GNU Free Documentation License version 1.3. A copy of the license is included in the section entitled "GNU Free Documentation License". * Menu: * Overview:: Overview * Invocation:: Invocation * Scripts:: Linker Scripts * Machine Dependent:: Machine Dependent Features * BFD:: BFD * Reporting Bugs:: Reporting Bugs * MRI:: MRI Compatible Script Files * GNU Free Documentation License:: GNU Free Documentation License * LD Index:: LD Index  File: ld.info, Node: Overview, Next: Invocation, Prev: Top, Up: Top 1 Overview ********** `ld' combines a number of object and archive files, relocates their data and ties up symbol references. Usually the last step in compiling a program is to run `ld'. `ld' accepts Linker Command Language files written in a superset of AT&T's Link Editor Command Language syntax, to provide explicit and total control over the linking process. This version of `ld' uses the general purpose BFD libraries to operate on object files. This allows `ld' to read, combine, and write object files in many different formats--for example, COFF or `a.out'. Different formats may be linked together to produce any available kind of object file. *Note BFD::, for more information. Aside from its flexibility, the GNU linker is more helpful than other linkers in providing diagnostic information. Many linkers abandon execution immediately upon encountering an error; whenever possible, `ld' continues executing, allowing you to identify other errors (or, in some cases, to get an output file in spite of the error).  File: ld.info, Node: Invocation, Next: Scripts, Prev: Overview, Up: Top 2 Invocation ************ The GNU linker `ld' is meant to cover a broad range of situations, and to be as compatible as possible with other linkers. As a result, you have many choices to control its behavior. * Menu: * Options:: Command Line Options * Environment:: Environment Variables  File: ld.info, Node: Options, Next: Environment, Up: Invocation 2.1 Command Line Options ======================== The linker supports a plethora of command-line options, but in actual practice few of them are used in any particular context. For instance, a frequent use of `ld' is to link standard Unix object files on a standard, supported Unix system. On such a system, to link a file `hello.o': ld -o OUTPUT /lib/crt0.o hello.o -lc This tells `ld' to produce a file called OUTPUT as the result of linking the file `/lib/crt0.o' with `hello.o' and the library `libc.a', which will come from the standard search directories. (See the discussion of the `-l' option below.) Some of the command-line options to `ld' may be specified at any point in the command line. However, options which refer to files, such as `-l' or `-T', cause the file to be read at the point at which the option appears in the command line, relative to the object files and other file options. Repeating non-file options with a different argument will either have no further effect, or override prior occurrences (those further to the left on the command line) of that option. Options which may be meaningfully specified more than once are noted in the descriptions below. Non-option arguments are object files or archives which are to be linked together. They may follow, precede, or be mixed in with command-line options, except that an object file argument may not be placed between an option and its argument. Usually the linker is invoked with at least one object file, but you can specify other forms of binary input files using `-l', `-R', and the script command language. If _no_ binary input files at all are specified, the linker does not produce any output, and issues the message `No input files'. If the linker cannot recognize the format of an object file, it will assume that it is a linker script. A script specified in this way augments the main linker script used for the link (either the default linker script or the one specified by using `-T'). This feature permits the linker to link against a file which appears to be an object or an archive, but actually merely defines some symbol values, or uses `INPUT' or `GROUP' to load other objects. Specifying a script in this way merely augments the main linker script, with the extra commands placed after the main script; use the `-T' option to replace the default linker script entirely, but note the effect of the `INSERT' command. *Note Scripts::. For options whose names are a single letter, option arguments must either follow the option letter without intervening whitespace, or be given as separate arguments immediately following the option that requires them. For options whose names are multiple letters, either one dash or two can precede the option name; for example, `-trace-symbol' and `--trace-symbol' are equivalent. Note--there is one exception to this rule. Multiple letter options that start with a lower case 'o' can only be preceded by two dashes. This is to reduce confusion with the `-o' option. So for example `-omagic' sets the output file name to `magic' whereas `--omagic' sets the NMAGIC flag on the output. Arguments to multiple-letter options must either be separated from the option name by an equals sign, or be given as separate arguments immediately following the option that requires them. For example, `--trace-symbol foo' and `--trace-symbol=foo' are equivalent. Unique abbreviations of the names of multiple-letter options are accepted. Note--if the linker is being invoked indirectly, via a compiler driver (e.g. `gcc') then all the linker command line options should be prefixed by `-Wl,' (or whatever is appropriate for the particular compiler driver) like this: gcc -Wl,--start-group foo.o bar.o -Wl,--end-group This is important, because otherwise the compiler driver program may silently drop the linker options, resulting in a bad link. Confusion may also arise when passing options that require values through a driver, as the use of a space between option and argument acts as a separator, and causes the driver to pass only the option to the linker and the argument to the compiler. In this case, it is simplest to use the joined forms of both single- and multiple-letter options, such as: gcc foo.o bar.o -Wl,-eENTRY -Wl,-Map=a.map Here is a table of the generic command line switches accepted by the GNU linker: `@FILE' Read command-line options from FILE. The options read are inserted in place of the original @FILE option. If FILE does not exist, or cannot be read, then the option will be treated literally, and not removed. Options in FILE are separated by whitespace. A whitespace character may be included in an option by surrounding the entire option in either single or double quotes. Any character (including a backslash) may be included by prefixing the character to be included with a backslash. The FILE may itself contain additional @FILE options; any such options will be processed recursively. `-a KEYWORD' This option is supported for HP/UX compatibility. The KEYWORD argument must be one of the strings `archive', `shared', or `default'. `-aarchive' is functionally equivalent to `-Bstatic', and the other two keywords are functionally equivalent to `-Bdynamic'. This option may be used any number of times. `--audit AUDITLIB' Adds AUDITLIB to the `DT_AUDIT' entry of the dynamic section. AUDITLIB is not checked for existence, nor will it use the DT_SONAME specified in the library. If specified multiple times `DT_AUDIT' will contain a colon separated list of audit interfaces to use. If the linker finds an object with an audit entry while searching for shared libraries, it will add a corresponding `DT_DEPAUDIT' entry in the output file. This option is only meaningful on ELF platforms supporting the rtld-audit interface. `-A ARCHITECTURE' `--architecture=ARCHITECTURE' In the current release of `ld', this option is useful only for the Intel 960 family of architectures. In that `ld' configuration, the ARCHITECTURE argument identifies the particular architecture in the 960 family, enabling some safeguards and modifying the archive-library search path. *Note `ld' and the Intel 960 family: i960, for details. Future releases of `ld' may support similar functionality for other architecture families. `-b INPUT-FORMAT' `--format=INPUT-FORMAT' `ld' may be configured to support more than one kind of object file. If your `ld' is configured this way, you can use the `-b' option to specify the binary format for input object files that follow this option on the command line. Even when `ld' is configured to support alternative object formats, you don't usually need to specify this, as `ld' should be configured to expect as a default input format the most usual format on each machine. INPUT-FORMAT is a text string, the name of a particular format supported by the BFD libraries. (You can list the available binary formats with `objdump -i'.) *Note BFD::. You may want to use this option if you are linking files with an unusual binary format. You can also use `-b' to switch formats explicitly (when linking object files of different formats), by including `-b INPUT-FORMAT' before each group of object files in a particular format. The default format is taken from the environment variable `GNUTARGET'. *Note Environment::. You can also define the input format from a script, using the command `TARGET'; see *Note Format Commands::. `-c MRI-COMMANDFILE' `--mri-script=MRI-COMMANDFILE' For compatibility with linkers produced by MRI, `ld' accepts script files written in an alternate, restricted command language, described in *Note MRI Compatible Script Files: MRI. Introduce MRI script files with the option `-c'; use the `-T' option to run linker scripts written in the general-purpose `ld' scripting language. If MRI-CMDFILE does not exist, `ld' looks for it in the directories specified by any `-L' options. `-d' `-dc' `-dp' These three options are equivalent; multiple forms are supported for compatibility with other linkers. They assign space to common symbols even if a relocatable output file is specified (with `-r'). The script command `FORCE_COMMON_ALLOCATION' has the same effect. *Note Miscellaneous Commands::. `--depaudit AUDITLIB' `-P AUDITLIB' Adds AUDITLIB to the `DT_DEPAUDIT' entry of the dynamic section. AUDITLIB is not checked for existence, nor will it use the DT_SONAME specified in the library. If specified multiple times `DT_DEPAUDIT' will contain a colon separated list of audit interfaces to use. This option is only meaningful on ELF platforms supporting the rtld-audit interface. The -P option is provided for Solaris compatibility&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%. `-e ENTRY' `--entry=ENTRY' Use ENTRY as the explicit symbol for beginning execution of your program, rather than the default entry point. If there is no symbol named ENTRY, the linker will try to parse ENTRY as a number, and use that as the entry address (the number will be interpreted in base 10; you may use a leading `0x' for base 16, or a leading `0' for base 8). *Note Entry Point::, for a discussion of defaults and other ways of specifying the entry point. `--exclude-libs LIB,LIB,...' Specifies a list of archive libraries from which symbols should not be automatically exported. The library names may be delimited by commas or colons. Specifying `--exclude-libs ALL' excludes symbols in all archive libraries from automatic export. This option is available only for the i386 PE targeted port of the linker and for ELF targeted ports. For i386 PE, symbols explicitly listed in a .def file are still exported, regardless of this option. For ELF targeted ports, symbols affected by this option will be treated as hidden. `--exclude-modules-for-implib MODULE,MODULE,...' Specifies a list of object files or archive members, from which symbols should not be automatically exported, but which should be copied wholesale into the import library being generated during the link. The module names may be delimited by commas or colons, and must match exactly the filenames used by `ld' to open the files; for archive members, this is simply the member name, but for object files the name listed must include and match precisely any path used to specify the input file on the linker's command-line. This option is available only for the i386 PE targeted port of the linker. Symbols explicitly listed in a .def file are still exported, regardless of this option. `-E' `--export-dynamic' `--no-export-dynamic' When creating a dynamically linked executable, using the `-E' option or the `--export-dynamic' option causes the linker to add all symbols to the dynamic symbol table. The dynamic symbol table is the set of symbols which are visible from dynamic objects at run time. If you do not use either of these options (or use the `--no-export-dynamic' option to restore the default behavior), the dynamic symbol table will normally contain only those symbols which are referenced by some dynamic object mentioned in the link. If you use `dlopen' to load a dynamic object which needs to refer back to the symbols defined by the program, rather than some other dynamic object, then you will probably need to use this option when linking the program itself. You can also use the dynamic list to control what symbols should be added to the dynamic symbol table if the output format supports it. See the description of `--dynamic-list'. Note that this option is specific to ELF targeted ports. PE targets support a similar function to export all symbols from a DLL or EXE; see the description of `--export-all-symbols' below. `-EB' Link big-endian objects. This affects the default output format. `-EL' Link little-endian objects. This affects the default output format. `-f NAME' `--auxiliary=NAME' When creating an ELF shared object, set the internal DT_AUXILIARY field to the specified name. This tells the dynamic linker that the symbol table of the shared object should be used as an auxiliary filter on the symbol table of the shared object NAME. If you later link a program against this filter object, then, when you run the program, the dynamic linker will see the DT_AUXILIARY field. If the dynamic linker resolves any symbols from the filter object, it will first check whether there is a definition in the shared object NAME. If there is one, it will be used instead of the definition in the filter object. The shared object NAME need not exist. Thus the shared object NAME may be used to provide an alternative implementation of certain functions, perhaps for debugging or for machine specific performance. This option may be specified more than once. The DT_AUXILIARY entries will be created in the order in which they appear on the command line. `-F NAME' `--filter=NAME' When creating an ELF shared object, set the internal DT_FILTER field to the specified name. This tells the dynamic linker that the symbol table of the shared object which is being created should be used as a filter on the symbol table of the shared object NAME. If you later link a program against this filter object, then, when you run the program, the dynamic linker will see the DT_FILTER field. The dynamic linker will resolve symbols according to the symbol table of the filter object as usual, but it will actually link to the definitions found in the shared object NAME. Thus the filter object can be used to select a subset of the symbols provided by the object NAME. Some older linkers used the `-F' option throughout a compilation toolchain for specifying object-file format for both input and output object files. The GNU linker uses other mechanisms for this purpose: the `-b', `--format', `--oformat' options, the `TARGET' command in linker scripts, and the `GNUTARGET' environment variable. The GNU linker will ignore the `-F' option when not creating an ELF shared object. `-fini=NAME' When creating an ELF executable or shared object, call NAME when the executable or shared object is unloaded, by setting DT_FINI to the address of the function. By default, the linker uses `_fini' as the function to call. `-g' Ignored. Provided for compatibility with other tools. `-G VALUE' `--gpsize=VALUE' Set the maximum size of objects to be optimized using the GP register to SIZE. This is only meaningful for object file formats such as MIPS ECOFF which supports putting large and small objects into different sections. This is ignored for other object file formats. `-h NAME' `-soname=NAME' When creating an ELF shared object, set the internal DT_SONAME field to the specified name. When an executable is linked with a shared object which has a DT_SONAME field, then when the executable is run the dynamic linker will attempt to load the shared object specified by the DT_SONAME field rather than the using the file name given to the linker. `-i' Perform an incremental link (same as option `-r'). `-init=NAME' When creating an ELF executable or shared object, call NAME when the executable or shared object is loaded, by setting DT_INIT to the address of the function. By default, the linker uses `_init' as the function to call. `-l NAMESPEC' `--library=NAMESPEC' Add the archive or object file specified by NAMESPEC to the list of files to link. This option may be used any number of times. If NAMESPEC is of the form `:FILENAME', `ld' will search the library path for a file called FILENAME, otherwise it will search the library path for a file called `libNAMESPEC.a'. On systems which support shared libraries, `ld' may also search for files other than `libNAMESPEC.a'. Specifically, on ELF and SunOS systems, `ld' will search a directory for a library called `libNAMESPEC.so' before searching for one called `libNAMESPEC.a'. (By convention, a `.so' extension indicates a shared library.) Note that this behavior does not apply to `:FILENAME', which always specifies a file called FILENAME. The linker will search an archive only once, at the location where it is specified on the command line. If the archive defines a symbol which was undefined in some object which appeared before the archive on the command line, the linker will include the appropriate file(s) from the archive. However, an undefined symbol in an object appearing later on the command line will not cause the linker to search the archive again. See the `-(' option for a way to force the linker to search archives multiple times. You may list the same archive multiple times on the command line. This type of archive searching is standard for Unix linkers. However, if you are using `ld' on AIX, note that it is different from the behaviour of the AIX linker. `-L SEARCHDIR' `--library-path=SEARCHDIR' Add path SEARCHDIR to the list of paths that `ld' will search for archive libraries and `ld' control scripts. You may use this option any number of times. The directories are searched in the order in which they are specified on the command line. Directories specified on the command line are searched before the default directories. All `-L' options apply to all `-l' options, regardless of the order in which the options appear. `-L' options do not affect how `ld' searches for a linker script unless `-T' option is specified. If SEARCHDIR begins with `=', then the `=' will be replaced by the "sysroot prefix", a path specified when the linker is configured. The default set of paths searched (without being specified with `-L') depends on which emulation mode `ld' is using, and in some cases also on how it was configured. *Note Environment::. The paths can also be specified in a link script with the `SEARCH_DIR' command. Directories specified this way are searched at the point in which the linker script appears in the command line. `-m EMULATION' Emulate the EMULATION linker. You can list the available emulations with the `--verbose' or `-V' options. If the `-m' option is not used, the emulation is taken from the `LDEMULATION' environment variable, if that is defined. Otherwise, the default emulation depends upon how the linker was configured. `-M' `--print-map' Print a link map to the standard output. A link map provides information about the link, including the following: * Where object files are mapped into memory. * How common symbols are allocated. * All archive members included in the link, with a mention of the symbol which caused the archive member to be brought in. * The values assigned to symbols. Note - symbols whose values are computed by an expression which involves a reference to a previous value of the same symbol may not have correct result displayed in the link map. This is because the linker discards intermediate results and only retains the final value of an expression. Under such circumstances the linker will display the final value enclosed by square brackets. Thus for example a linker script containing: foo = 1 foo = foo * 4 foo = foo + 8 will produce the following output in the link map if the `-M' option is used: 0x00000001 foo = 0x1 [0x0000000c] foo = (foo * 0x4) [0x0000000c] foo = (foo + 0x8) See *Note Expressions:: for more information about expressions in linker scripts. `-n' `--nmagic' Turn off page alignment of sections, and disable linking against shared libraries. If the output format supports Unix style magic numbers, mark the output as `NMAGIC'. `-N' `--omagic' Set the text and data sections to be readable and writable. Also, do not page-align the data segment, and disable linking against shared libraries. If the output format supports Unix style magic numbers, mark the output as `OMAGIC'. Note: Although a writable text section is allowed for PE-COFF targets, it does not conform to the format specification published by Microsoft. `--no-omagic' This option negates most of the effects of the `-N' option. It sets the text section to be read-only, and forces the data segment to be page-aligned. Note - this option does not enable linking against shared libraries. Use `-Bdynamic' for this. `-o OUTPUT' `--output=OUTPUT' Use OUTPUT as the name for the program produced by `ld'; if this option is not specified, the name `a.out' is used by default. The script command `OUTPUT' can also specify the output file name. `-O LEVEL' If LEVEL is a numeric values greater than zero `ld' optimizes the output. This might take significantly longer and therefore probably should only be enabled for the final binary. At the moment this option only affects ELF shared library generation. Future releases of the linker may make more use of this option. Also currently there is no difference in the linker's behaviour for different non-zero values of this option. Again this may change with future releases. `-q' `--emit-relocs' Leave relocation sections and contents in fully linked executables. Post link analysis and optimization tools may need this information in order to perform correct modifications of executables. This results in larger executables. This option is currently only supported on ELF platforms. `--force-dynamic' Force the output file to have dynamic sections. This option is specific to VxWorks targets. `-r' `--relocatable' Generate relocatable output--i.e., generate an output file that can in turn serve as input to `ld'. This is often called "partial linking". As a side effect, in environments that support standard Unix magic numbers, this option also sets the output file's magic number to `OMAGIC'. If this option is not specified, an absolute file is produced. When linking C++ programs, this option _will not_ resolve references to constructors; to do that, use `-Ur'. When an input file does not have the same format as the output file, partial linking is only supported if that input file does not contain any relocations. Different output formats can have further restrictions; for example some `a.out'-based formats do not support partial linking with input files in other formats at all. This option does the same thing as `-i'. `-R FILENAME' `--just-symbols=FILENAME' Read symbol names and their addresses from FILENAME, but do not relocate it or include it in the output. This allows your output file to refer symbolically to absolute locations of memory defined in other programs. You may use this option more than once. For compatibility with other ELF linkers, if the `-R' option is followed by a directory name, rather than a file name, it is treated as the `-rpath' option. `-s' `--strip-all' Omit all symbol information from the output file. `-S' `--strip-debug' Omit debugger symbol information (but not all symbols) from the output file. `-t' `--trace' Print the names of the input files as `ld' processes them. `-T SCRIPTFILE' `--script=SCRIPTFILE' Use SCRIPTFILE as the linker script. This script replaces `ld''s default linker script (rather than adding to it), so COMMANDFILE must specify everything necessary to describe the output file. *Note Scripts::. If SCRIPTFILE does not exist in the current directory, `ld' looks for it in the directories specified by any preceding `-L' options. Multiple `-T' options accumulate. `-dT SCRIPTFILE' `--default-script=SCRIPTFILE' Use SCRIPTFILE as the default linker script. *Note Scripts::. This option is similar to the `--script' option except that processing of the script is delayed until after the rest of the command line has been processed. This allows options placed after the `--default-script' option on the command line to affect the behaviour of the linker script, which can be important when the linker command line cannot be directly controlled by the user. (eg because the command line is being constructed by another tool, such as `gcc'). `-u SYMBOL' `--undefined=SYMBOL' Force SYMBOL to be entered in the output file as an undefined symbol. Doing this may, for example, trigger linking of additional modules from standard libraries. `-u' may be repeated with different option arguments to enter additional undefined symbols. This option is equivalent to the `EXTERN' linker script command. `-Ur' For anything other than C++ programs, this option is equivalent to `-r': it generates relocatable output--i.e., an output file that can in turn serve as input to `ld'. When linking C++ programs, `-Ur' _does_ resolve references to constructors, unlike `-r'. It does not work to use `-Ur' on files that were themselves linked with `-Ur'; once the constructor table has been built, it cannot be added to. Use `-Ur' only for the last partial link, and `-r' for the others. `--unique[=SECTION]' Creates a separate output section for every input section matching SECTION, or if the optional wildcard SECTION argument is missing, for every orphan input section. An orphan section is one not specifically mentioned in a linker script. You may use this option multiple times on the command line; It prevents the normal merging of input sections with the same name, overriding output section assignments in a linker script. `-v' `--version' `-V' Display the version number for `ld'. The `-V' option also lists the supported emulations. `-x' `--discard-all' Delete all local symbols. `-X' `--discard-locals' Delete all temporary local symbols. (These symbols start with system-specific local label prefixes, typically `.L' for ELF systems or `L' for traditional a.out systems.) `-y SYMBOL' `--trace-symbol=SYMBOL' Print the name of each linked file in which SYMBOL appears. This option may be given any number of times. On many systems it is necessary to prepend an underscore. This option is useful when you have an undefined symbol in your link but don't know where the reference is coming from. `-Y PATH' Add PATH to the default library search path. This option exists for Solaris compatibility. `-z KEYWORD' The recognized keywords are: `combreloc' Combines multiple reloc sections and sorts them to make dynamic symbol lookup caching possible. `defs' Disallows undefined symbols in object files. Undefined symbols in shared libraries are still allowed. `execstack' Marks the object as requiring executable stack. `initfirst' This option is only meaningful when building a shared object. It marks the object so that its runtime initialization will occur before the runtime initialization of any other objects brought into the process at the same time. Similarly the runtime finalization of the object will occur after the runtime finalization of any other objects. `interpose' Marks the object that its symbol table interposes before all symbols but the primary executable. `lazy' When generating an executable or shared library, mark it to tell the dynamic linker to defer function call resolution to the point when the function is called (lazy binding), rather than at load time. Lazy binding is the default. `loadfltr' Marks the object that its filters be processed immediately at runtime. `muldefs' Allows multiple definitions. `nocombreloc' Disables multiple reloc sections combining. `nocopyreloc' Disables production of copy relocs. `nodefaultlib' Marks the object that the search for dependencies of this object will ignore any default library search paths. `nodelete' Marks the object shouldn't be unloaded at runtime. `nodlopen' Marks the object not available to `dlopen'. `nodump' Marks the object can not be dumped by `dldump'. `noexecstack' Marks the object as not requiring executable stack. `norelro' Don't create an ELF `PT_GNU_RELRO' segment header in the object. `now' When generating an executable or shared library, mark it to tell the dynamic linker to resolve all symbols when the program is started, or when the shared library is linked to using dlopen, instead of deferring function call resolution to the point when the function is first called. `origin' Marks the object may contain $ORIGIN. `relro' Create an ELF `PT_GNU_RELRO' segment header in the object. `max-page-size=VALUE' Set the emulation maximum page size to VALUE. `common-page-size=VALUE' Set the emulation common page size to VALUE. Other keywords are ignored for Solaris compatibility. `-( ARCHIVES -)' `--start-group ARCHIVES --end-group' The ARCHIVES should be a list of archive files. They may be either explicit file names, or `-l' options. The specified archives are searched repeatedly until no new undefined references are created. Normally, an archive is searched only once in the order that it is specified on the command line. If a symbol in that archive is needed to resolve an undefined symbol referred to by an object in an archive that appears later on the command line, the linker would not be able to resolve that reference. By grouping the archives, they all be searched repeatedly until all possible references are resolved. Using this option has a significant performance cost. It is best to use it only when there are unavoidable circular references between two or more archives. `--accept-unknown-input-arch' `--no-accept-unknown-input-arch' Tells the linker to accept input files whose architecture cannot be recognised. The assumption is that the user knows what they are doing and deliberately wants to link in these unknown input files. This was the default behaviour of the linker, before release 2.14. The default behaviour from release 2.14 onwards is to reject such input files, and so the `--accept-unknown-input-arch' option has been added to restore the old behaviour. `--as-needed' `--no-as-needed' This option affects ELF DT_NEEDED tags for dynamic libraries mentioned on the command line after the `--as-needed' option. Normally the linker will add a DT_NEEDED tag for each dynamic library mentioned on the command line, regardless of whether the library is actually needed or not. `--as-needed' causes a DT_NEEDED tag to only be emitted for a library that satisfies an undefined symbol reference from a regular object file or, if the library is not found in the DT_NEEDED lists of other libraries linked up to that point, an undefined symbol reference from another dynamic library. `--no-as-needed' restores the default behaviour. `--add-needed' `--no-add-needed' These two options have been deprecated because of the similarity of their names to the `--as-needed' and `--no-as-needed' options. They have been replaced by `--copy-dt-needed-entries' and `--no-copy-dt-needed-entries'. `-assert KEYWORD' This option is ignored for SunOS compatibility. `-Bdynamic' `-dy' `-call_shared' Link against dynamic libraries. This is only meaningful on platforms for which shared libraries are supported. This option is normally the default on such platforms. The different variants of this option are for compatibility with various systems. You may use this option multiple times on the command line: it affects library searching for `-l' options which follow it. `-Bgroup' Set the `DF_1_GROUP' flag in the `DT_FLAGS_1' entry in the dynamic section. This causes the runtime linker to handle lookups in this object and its dependencies to be performed only inside the group. `--unresolved-symbols=report-all' is implied. This option is only meaningful on ELF platforms which support shared libraries. `-Bstatic' `-dn' `-non_shared' `-static' Do not link against shared libraries. This is only meaningful on platforms for which shared libraries are supported. The different variants of this option are for compatibility with various systems. You may use this option multiple times on the command line: it affects library searching for `-l' options which follow it. This option also implies `--unresolved-symbols=report-all'. This option can be used with `-shared'. Doing so means that a shared library is being created but that all of the library's external references must be resolved by pulling in entries from static libraries. `-Bsymbolic' When creating a shared library, bind references to global symbols to the definition within the shared library, if any. Normally, it is possible for a program linked against a shared library to override the definition within the shared library. This option is only meaningful on ELF platforms which support shared libraries. `-Bsymbolic-functions' When creating a shared library, bind references to global function symbols to the definition within the shared library, if any. This option is only meaningful on ELF platforms which support shared libraries. `--dynamic-list=DYNAMIC-LIST-FILE' Specify the name of a dynamic list file to the linker. This is typically used when creating shared libraries to specify a list of global symbols whose references shouldn't be bound to the definition within the shared library, or creating dynamically linked executables to specify a list of symbols which should be added to the symbol table in the executable. This option is only meaningful on ELF platforms which support shared libraries. The format of