src/gnu/usr.bin/binutils/libbinutils/Makefile, branch main FreeBSD source tree Retire obsolete GDB 6.1.1 2020-12-15T17:44:19+00:00 Ed Maste emaste@FreeBSD.org 2020-12-15T17:44:19+00:00 1c0ea326aa6d30385a69bd1d93ee161cfbe59a5a GDB 6.1.1 was released in June 2004 and is long obsolete. It does not support all of the architectures that FreeBSD does, and imposes limitations on the FreeBSD kernel build, such as the continued use of DWARF2 debugging information. It was kept (in /usr/libexec/) only for use by crashinfo(8), which extracts some basic information from a kernel core dump after a crash. Crashinfo already prefers gdb from port/package if installed. Future work may add kernel debug support to LLDB or find another path for crashinfo's needs, but in any case we do not want to ship the excessively outdated GDB in FreeBSD 13. Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D27610 
GDB 6.1.1 was released in June 2004 and is long obsolete. It does not
support all of the architectures that FreeBSD does, and imposes
limitations on the FreeBSD kernel build, such as the continued use of
DWARF2 debugging information.

It was kept (in /usr/libexec/) only for use by crashinfo(8), which
extracts some basic information from a kernel core dump after a crash.
Crashinfo already prefers gdb from port/package if installed.

Future work may add kernel debug support to LLDB or find another path
for crashinfo's needs, but in any case we do not want to ship the
excessively outdated GDB in FreeBSD 13.

Sponsored by:	The FreeBSD Foundation
Differential Revision:	https://reviews.freebsd.org/D27610
Define YY_NO_INPUT when building libbinutils, to prevent warnings about 2011-12-16T22:19:13+00:00 Dimitry Andric dim@FreeBSD.org 2011-12-16T22:19:13+00:00 6aff93296ddb4c5b7b370dd8c1e0637d3cc8ac25 unused input() functions emitted by lex. MFC after: 1 week 
unused input() functions emitted by lex.

MFC after:	1 week
Update Makefile and config.h.bsd for libbinutils. 2010-11-01T19:42:29+00:00 Dimitry Andric dim@FreeBSD.org 2010-11-01T19:42:29+00:00 28b535d1e0096acee0ccf66247b20ce55ae48990 






Most of binutils now compiles at WARNS=3, except for libiberty and
2010-10-22T20:46:08+00:00

Dimitry Andric
dim@FreeBSD.org

2010-10-22T20:46:08+00:00

e083002bcac10c4257d937b7b5f44360136962a4

libbfd, which still need WARNS=2.





libbfd, which still need WARNS=2.







Add new upstream file, and update TARGET definition.
2010-10-21T20:21:36+00:00

Dimitry Andric
dim@FreeBSD.org

2010-10-21T20:21:36+00:00

bebf80241981a8e50fcfdf661f96b12ed2867ab2












Use one file per line in SRCS= definition, to make insertions and
2010-10-21T20:20:33+00:00

Dimitry Andric
dim@FreeBSD.org

2010-10-21T20:20:33+00:00

8114428ba2a41227df5af016d45ee27c8ecb3ff8

deletions easier, and sort the file list.





deletions easier, and sort the file list.







For variables that are only checked with defined(), don't provide
2004-10-24T15:33:08+00:00

Ruslan Ermilov
ru@FreeBSD.org

2004-10-24T15:33:08+00:00

a35d88931c87cfe6bd38f01d7bad22140b3b38f3

any fake value.





any fake value.







Updated Bmake framework for Binutils 2.15.
2004-06-16T07:09:44+00:00

David E. O'Brien
obrien@FreeBSD.org

2004-06-16T07:09:44+00:00

e223c68bfc26436d6e1e39202cf7262335ca1f7c












style.Makefile(5):
2004-02-24T19:23:33+00:00

Johan Karlsson
johan@FreeBSD.org

2004-02-24T19:23:33+00:00

7ff8c436d3890e42fa1dce8faf5d61042c398591

	Use WARNS?= instead of WARNS=

For this to work properly for all part is the subdirectories
the WARNS assignments in Makefile.inc0 are moved to the correspondning
Makefile.inc.

Approved by:	obrien (binutils maintainer)
Tested by:	make universe





	Use WARNS?= instead of WARNS=

For this to work properly for all part is the subdirectories
the WARNS assignments in Makefile.inc0 are moved to the correspondning
Makefile.inc.

Approved by:	obrien (binutils maintainer)
Tested by:	make universe







Set the binutils arch for as/nm correctly on the amd64 platform.
2003-05-08T06:39:31+00:00

Peter Wemm
peter@FreeBSD.org

2003-05-08T06:39:31+00:00

bd3aef3d0dd12e560f0e5fc50f3367f03fe01640

As far as binutils is concerned, the amd64 platform is still called
"x86-64"/"x86_64".  Setting things from ${MACHINE_ARCH} breaks that.

Approved by:  re (scottl)





As far as binutils is concerned, the amd64 platform is still called
"x86-64"/"x86_64".  Setting things from ${MACHINE_ARCH} breaks that.

Approved by:  re (scottl)