12.1 Fatal Errors

The following errors indicate that an internal error has occurred in the linker. If the linker emits any of the fatal errors listed below and you're using a custom linker script, check that the script specifies OUTPUT_FORMAT (elf32-tradlittlemips) and OUTPUT_ARCH (pic32mx). Other values may cause the linker to operate in an unsupported mode. Also check that you are passing only fully supported options on the linker's command line. Finally, make sure that no other applications have the linker's input or output files locked.

If the fatal error occurs with the correct OUTPUT_FORMAT, OUTPUT_ARCH, and command-line options, contact Microchip Technology at support.microchip.com for engineering support. Be sure to provide full details about the source code and command-line options that caused the error.

  • Bfd backend error: bfd_reloc_ctor unsupported
  • Bfd_hash_allocate failed creating symbol %s
  • Bfd_hash_lookup failed: %e
  • Bfd_hash_lookup for insertion failed: %e
  • Bfd_hash_table_init failed: %e
  • Bfd_hash_table_init of cref table failed: %e
  • Bfd_link_hash_lookup failed: %e
  • Bfd_new_link_order failed
  • Bfd_record_phdr failed: %e
  • Can't set bfd default target to '%s': %e
  • Can not create link hash table: %e
  • Can not make object file: %e
  • Cannot represent machine '%s'
  • Could not read relocs: %e
  • Could not read symbols
  • Cref_hash_lookup failed: %e
  • Error closing file '%s'
  • Error writing file '%s'
  • Failed to create hash table
  • Failed to merge target specific data
  • File not recognized: %e
  • Final close failed: %e
  • Final link failed: %e
  • Hash creation failed
  • Out of memory during initialization
  • Symbol '%t' missing from main hash table
  • Target %s not found
  • Target architecture respecified
  • Unknown architecture: %s
  • Unknown demangling style '%s'
  • Unknown language '%s' in version information