Lines Matching full:archives
126 Also, BFDs opened for archives have the additional attribute of an
407 /* Stuff only useful for archives. */
1062 * Archives::
2050 File: bfd.info, Node: Symbols, Next: Archives, Prev: Sections, Up: BFD front end
2484 File: bfd.info, Node: Archives, Next: Formats, Prev: Symbols, Up: BFD front end
2486 2.8 Archives
2511 code of any given environment. BFD archives may contain files of
2513 architectures. You may even place archives recursively into archives!
2516 more expressive than others. For instance, Intel COFF archives can
2517 preserve long filenames; SunOS a.out archives cannot. If you move a
2526 this case due to restrictions in the format of archives. Many Unix
2530 Archives are supported in BFD in `archive.c'.
2574 File: bfd.info, Node: Formats, Next: Relocations, Prev: Archives, Up: BFD front end
6679 regardless of what else is going on. This is useful in archives.
7105 `_bfd_generic_link_add_archive_symbols', because ECOFF archives already
8341 object format with no support for archives or debugging information,
9180 * bfd_get_next_mapent: Archives. (line 52)
9246 * bfd_openr_next_archived_file: Archives. (line 78)
10398 * bfd_set_archive_head: Archives. (line 69)
10469 Node: Archives95695
