Go to file
Simon Marchi a791eef767 gdb: add IWYU export pragams to gdb_curses.h
It seems like gdb_curses.h is included whenever we want to access
ncurses functionality, instead of including directly ncurses.h.  As a
result, clangd often erroneously shows that gdb_curses.h inclusions are
unused.

By adding those pragmas, clangd (and the include-what-you-use tool)
understands that gdb_curses.h is a valid provider for whatever these
ncurses.h files provide.

Change-Id: Ia8acd761dae1577f7151d5fb558f35514b4e4ea2
Approved-By: Tom Tromey <tom@tromey.com>
2024-06-07 22:52:54 -04:00
bfd Automatic date update in version.in 2024-06-08 00:00:20 +00:00
binutils NEWS: arm: note that FPA support has been removed 2024-06-05 17:45:45 +01:00
config
contrib
cpu
elfcpp
etc
gas arm: fix testsuite fallout on arm-elf and arm-nto from FPA removal 2024-06-06 15:55:16 +01:00
gdb gdb: add IWYU export pragams to gdb_curses.h 2024-06-07 22:52:54 -04:00
gdbserver Stop 'configure --enable-threading' if std::thread doesn't work 2024-05-16 13:03:58 +01:00
gdbsupport Stop 'configure --enable-threading' if std::thread doesn't work 2024-05-16 13:03:58 +01:00
gnulib
gold
gprof
gprofng gprofng: add hardware counters for AMD Zen4 2024-06-03 11:38:58 -07:00
include RISC-V: Add support for Zvfbfwma extension 2024-06-06 16:10:53 +08:00
ld aarch64: Test DT_RELR with discarded sections 2024-06-07 08:23:23 +01:00
libbacktrace
libctf libctf testsuite compilation failure 2024-05-23 08:11:12 +09:30
libdecnumber
libiberty
libsframe
opcodes opcodes/riscv: prevent future use of disassemble_info::fprintf_func 2024-06-06 10:33:33 +01:00
readline
sim sim: riscv: Fix build issue due to recent binutils commit 2024-05-09 17:04:14 +02:00
texinfo
zlib
.cvsignore
.editorconfig
.gitattributes
.gitignore .gitignore: ignore .vscode 2024-05-30 12:09:35 +01:00
.pre-commit-config.yaml gdb: bump black version to 24.4.2 2024-05-16 11:34:40 -04:00
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 src-release.sh: fix adjusting files permissions and cleaning 2024-06-04 14:59:08 +01: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.