Lines Matching full:archives
138 Also, BFDs opened for archives have the additional attribute of an
454 normally be the same as origin, except for thin archives,
489 /* Stuff only useful for archives. */
1204 * Archives::
2226 File: bfd.info, Node: Symbols, Next: Archives, Prev: Sections, Up: BFD front end
2678 File: bfd.info, Node: Archives, Next: Formats, Prev: Symbols, Up: BFD front end
2680 2.8 Archives
2705 code of any given environment. BFD archives may contain files of
2707 architectures. You may even place archives recursively into archives!
2710 more expressive than others. For instance, Intel COFF archives can
2711 preserve long filenames; SunOS a.out archives cannot. If you move a
2720 this case due to restrictions in the format of archives. Many Unix
2724 Archives are supported in BFD in `archive.c'.
2768 File: bfd.info, Node: Formats, Next: Relocations, Prev: Archives, Up: BFD front end
7385 regardless of what else is going on. This is useful in archives.
7820 `_bfd_generic_link_add_archive_symbols', because ECOFF archives already
9146 object format with no support for archives or debugging information,
10098 * bfd_get_next_mapent: Archives. (line 52)
10166 * bfd_openr_next_archived_file: Archives. (line 78)
11560 * bfd_set_archive_head: Archives. (line 69)
11631 Node: Archives103335
