Skip to content

Unofficial mirror of sourceware binutils-gdb repository. Updated daily.

License

Notifications You must be signed in to change notification settings

bminor/binutils-gdb

Folders and files

NameName
Last commit message
Last commit date

Latest commit

0d1f436 · Mar 28, 2025
Mar 28, 2025
Mar 28, 2025
Nov 27, 2024
Sep 4, 2024
Jan 19, 2025
Jan 19, 2025
Jan 1, 2025
Mar 27, 2025
Mar 27, 2025
Mar 27, 2025
Mar 27, 2025
Jun 9, 2024
Feb 27, 2025
Mar 14, 2025
Mar 12, 2025
Mar 26, 2025
Mar 26, 2025
Jun 9, 2024
Feb 28, 2025
Aug 12, 2023
Mar 10, 2025
Feb 4, 2025
Mar 28, 2025
Jan 4, 2025
Mar 25, 2025
Apr 21, 2009
Jun 9, 2024
Feb 13, 2007
Jan 28, 2022
Jul 25, 2022
Feb 28, 2025
Feb 4, 2025
Jul 14, 2005
Jul 16, 2005
Dec 14, 2017
Oct 1, 2013
Jul 17, 2007
Jul 17, 2007
Jan 19, 2025
Mar 18, 2024
Mar 22, 2024
Mar 22, 2024
Mar 22, 2024
May 3, 1999
Oct 4, 2022
Apr 20, 2023
Jun 19, 2018
Nov 16, 2014
Aug 12, 2023
Jan 17, 2025
Feb 13, 2011
Jan 17, 2025
Nov 26, 2024
Nov 26, 2024
Nov 16, 2014
Mar 27, 2009
Nov 16, 2014
Aug 12, 2023
Sep 29, 2008
Sep 25, 2024
Jan 9, 2010
Sep 29, 2008
Jan 9, 2010
Jan 9, 2010
May 3, 1999
Nov 16, 2014
Aug 8, 1999
Nov 16, 2014
Nov 16, 2014
Oct 31, 2018
Sep 1, 2009
Feb 4, 2025
Jul 14, 2005
Jun 19, 2018
Nov 16, 2014

Repository files navigation

		   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.