Lines Matching full:archives
127 Also, BFDs opened for archives have the additional attribute of an
408 /* Stuff only useful for archives. */
1020 * Archives::
2014 File: bfd.info, Node: Symbols, Next: Archives, Prev: Sections, Up: BFD front end
2448 File: bfd.info, Node: Archives, Next: Formats, Prev: Symbols, Up: BFD front end
2450 2.8 Archives
2475 code of any given environment. BFD archives may contain files of
2477 architectures. You may even place archives recursively into archives!
2480 more expressive than others. For instance, Intel COFF archives can
2481 preserve long filenames; SunOS a.out archives cannot. If you move a
2490 this case due to restrictions in the format of archives. Many Unix
2494 Archives are supported in BFD in `archive.c'.
2538 File: bfd.info, Node: Formats, Next: Relocations, Prev: Archives, Up: BFD front end
6545 regardless of what else is going on. This is useful in archives.
6971 `_bfd_generic_link_add_archive_symbols', because ECOFF archives already
8203 object format with no support for archives or debugging information,
9038 * bfd_get_next_mapent: Archives. (line 52)
9104 * bfd_openr_next_archived_file: Archives. (line 78)
10194 * bfd_set_archive_head: Archives. (line 69)
10265 Node: Archives94851
