Lines Matching full:archives
137 Also, BFDs opened for archives have the additional attribute of an
432 normally be the same as origin, except for thin archives,
467 /* Stuff only useful for archives. */
1163 * Archives::
2150 File: bfd.info, Node: Symbols, Next: Archives, Prev: Sections, Up: BFD front end
2595 File: bfd.info, Node: Archives, Next: Formats, Prev: Symbols, Up: BFD front end
2597 2.8 Archives
2622 code of any given environment. BFD archives may contain files of
2624 architectures. You may even place archives recursively into archives!
2627 more expressive than others. For instance, Intel COFF archives can
2628 preserve long filenames; SunOS a.out archives cannot. If you move a
2637 this case due to restrictions in the format of archives. Many Unix
2641 Archives are supported in BFD in `archive.c'.
2685 File: bfd.info, Node: Formats, Next: Relocations, Prev: Archives, Up: BFD front end
6913 regardless of what else is going on. This is useful in archives.
7339 `_bfd_generic_link_add_archive_symbols', because ECOFF archives already
8583 object format with no support for archives or debugging information,
9423 * bfd_get_next_mapent: Archives. (line 52)
9489 * bfd_openr_next_archived_file: Archives. (line 78)
10711 * bfd_set_archive_head: Archives. (line 69)
10782 Node: Archives100090
