Go to file
Tom Tromey 3b70bcb00f Use symbol_symtab accessor in compile-object-load.c
I noticed that compile-object-load.c directly references owner.symtab
of a symbol.  However, I think it's better for all users to call
symbol_symtab.  This patch makes this change.
2022-04-20 06:50:59 -06:00
bfd Add linker warning for when it creates an executable stack. 2022-04-20 13:39:05 +01:00
binutils Stop strip from removing debuglink sections. 2022-04-12 13:34:06 +01:00
config
contrib
cpu
elfcpp
etc
gas as: Reject unknown -gXXX option 2022-04-19 10:35:41 -07:00
gdb Use symbol_symtab accessor in compile-object-load.c 2022-04-20 06:50:59 -06:00
gdbserver gdbsupport: make gdb_abspath return an std::string 2022-04-18 15:48:03 -04:00
gdbsupport gdbsupport/selftest: Allow lazy registration 2022-04-19 09:12:42 +01:00
gnulib Update gnulib 2022-04-18 10:14:04 -06:00
gold
gprof
gprofng
include Add linker warning for when it creates an executable stack. 2022-04-20 13:39:05 +01:00
intl
ld Add linker warning for when it creates an executable stack. 2022-04-20 13:39:05 +01:00
libbacktrace
libctf
libdecnumber
libiberty
opcodes x86: VCMPSH is Evex.LLIG 2022-04-19 09:25:25 +02:00
readline
sim
texinfo
zlib Rebase the zlib sources to the 1.2.12 release 2022-04-12 16:24:10 +01:00
.cvsignore
.editorconfig
.gitattributes
.gitignore
ar-lib
ChangeLog Rebase the zlib sources to the 1.2.12 release 2022-04-12 16:24:10 +01:00
compile
config-ml.in
config.guess
config.rpath
config.sub
configure
configure.ac
COPYING
COPYING3
COPYING3.LIB
COPYING.LIB
COPYING.LIBGLOSS
COPYING.NEWLIB
depcomp
djunpack.bat
install-sh
libtool.m4
lt~obsolete.m4
ltgcc.m4
ltmain.sh
ltoptions.m4
ltsugar.m4
ltversion.m4
MAINTAINERS
Makefile.def
Makefile.in
Makefile.tpl
makefile.vms
missing
mkdep
mkinstalldirs
move-if-change
multilib.am
README
README-maintainer-mode
setup.com
src-release.sh
symlink-tree
test-driver
ylwrap

		   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.