Go to file
Tom Tromey 83c8b5eb33 Make nsalias.exp more reliable
nsalias.exp tries to detect a complaint that is issued when expanding
a CU.  However, the test is a bit funny in that, while gdb does
currently expand the CU and issue the complaint, it also emits this
error:

    No symbol "N100" in current context.

This series will change gdb such that this CU is not expanded -- which
makes sense, the symbol in question doesn't actually match the lookups
that are done.

So, to make the test more robust, a direct request to expand symtabs
is done instead.
2024-01-28 10:58:16 -07:00
bfd Automatic date update in version.in 2024-01-28 00:00:08 +00:00
binutils elf: Rename is_standard_elf to uses_elf_em 2024-01-26 07:32:03 -08:00
config
contrib
cpu sim: frv: fix -Wincompatible-function-pointer-types warnings [PR sim/29752] 2024-01-22 20:12:08 -05:00
elfcpp
etc
gas gas: scfi: untraceable control flow should be a hard error 2024-01-26 11:31:35 -08:00
gdb Make nsalias.exp more reliable 2024-01-28 10:58:16 -07:00
gdbserver
gdbsupport
gnulib
gold Updated Serbian translations for th bfd, gold and opcodes directories 2024-01-22 17:26:36 +00:00
gprof Updated translations for various sub-directories 2024-01-18 11:23:48 +00:00
gprofng Fix 31252 gprofng causes testsuite parallel jobs fail 2024-01-22 09:56:42 -08:00
include LoongArch: gas: Add support for s9 register 2024-01-26 16:49:43 +08:00
ld elf: Rename is_standard_elf to uses_elf_em 2024-01-26 07:32:03 -08:00
libbacktrace
libctf
libdecnumber
libiberty
libsframe libsframe: Fix calloc argument order in dump_sframe_header 2024-01-22 18:19:03 +01:00
opcodes aarch64: move SHA512 instructions to +sha3 2024-01-26 14:58:00 +00:00
readline
sim sim: sh: fix nested braces in struct init 2024-01-23 03:15:02 -05:00
texinfo
zlib
.cvsignore
.editorconfig
.gitattributes
.gitignore
ar-lib
ChangeLog
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
SECURITY.txt
setup.com
src-release.sh Add multilib.am to the list of top level files included in any release created by the src-release.sh script 2024-01-19 11:45:10 +00:00
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.