mirror of
https://github.com/darlinghq/darling-gdb.git
synced 2025-02-13 13:35:56 +00:00
a63e02c7f8
Use bh_root, and hh. (struct elf32_hppa_link_hash_entry): Use eh, and hsh_cache. (struct elf32_hppa_dyn_reloc_entry): Use hdh_next. (struct elf32_hppa_link_hash_table): Use etab and bstab. (stub_hash_newfunc): Use hh. (hppa_link_hash_newfunc): Use hsh_cache. (elf32_hppa_link_hash_table_create): Use etab, and bstab. (elf32_hppa_link_hash_table_free): Use bstab. (hppa_stub_name): Use eh. (hppa_get_stub_entry): Use hh, hsh_entry, and hsh_cache. (hppa_add_stub): Use bstab. (hppa_type_of_stub): Use eh. (hppa_build_one_stub): Use hh and bh_root. (elf32_hppa_copy_indirect_symbol): Use hdh_next. (elf32_hppa_check_relocs): Use eh, etab, and hdh_next. (elf32_hppa_gc_sweep_hook): Use hdh_next. (elf32_hppa_adjust_dynamic_symbol): Use hdh_next, and etab. (allocate_plt_static): Use etab. (allocate_dynrelocs): Use etab, and hdh_next. (readonly_dynrelocs): Use hdh_next. (elf32_hppa_size_dynamic_sections): Use etab, and hdh_next. (get_local_syms): Use eh, bstab, and hh. (elf32_hppa_size_stubs): Use eh, bstab, and hh. (elf32_hppa_set_gp): Use etab. (elf32_hppa_build_stubs): Use bstab. (final_link_relocate): Use eh, bh_root. (elf32_hppa_relocate_section): Use elf, etab. (elf32_hppa_finish_dynamic_sections): Use etab.
README for GNU development tools This directory contains various GNU compilers, assemblers, linkers, debuggers, etc., plus their support routines, definitions, and documentation. If you are receiving this as part of a GDB release, see the file gdb/README. If with a binutils release, see binutils/README; if with a libg++ release, see libg++/README, etc. That'll give you info about this package -- supported targets, how to use it, how to report bugs, etc. It is now possible to automatically configure and build a variety of tools with one command. To build all of the tools contained herein, run the ``configure'' script here, e.g.: ./configure make To install them (by default in /usr/local/bin, /usr/local/lib, etc), then do: make install (If the configure script can't determine your type of computer, give it the name as an argument, for instance ``./configure sun4''. You can use the script ``config.sub'' to test whether a name is recognized; if it is, config.sub translates it to a triplet specifying CPU, vendor, and OS.) If you have more than one compiler on your system, it is often best to explicitly set CC in the environment before running configure, and to also set CC when running make. For example (assuming sh/bash/ksh): CC=gcc ./configure make A similar example using csh: setenv CC gcc ./configure make Much of the code and documentation enclosed is copyright by the Free Software Foundation, Inc. See the file COPYING or COPYING.LIB in the various directories, for a description of the GNU General Public License terms under which you can copy the files. REPORTING BUGS: Again, see gdb/README, binutils/README, etc., for info on where and how to report problems.