Binutils with MCST patches
Go to file
Pedro Alves 6d03af93d2 Make 'make check TESTS="..."' work from GDB's build dir.
I noticed 'make check TESTS="..."' works when ran from gdb/testsuite/,
but TESTS is ignored when "make check" is ran from gdb/.

The issue is that TESTS isn't being passed to the testsuite subdir
make invocation.

gdb/
2014-03-12  Pedro Alves  <palves@redhat.com>

	* Makefile.in (TARGET_FLAGS_TO_PASS): Add TESTS.
2014-03-12 19:52:00 +00:00
bfd Prevent the linker from generaing a seg-fault when the user attempts to link 2014-03-12 13:12:37 +00:00
binutils Update the documentation for the AR command so that it shows the --plugin 2014-03-12 12:34:21 +00:00
config
cpu
elfcpp Update copyright years 2014-03-05 22:16:15 +10:30
etc
gas The value of a bignum expression is held in a single global array. This means 2014-03-12 15:50:49 +00:00
gdb Make 'make check TESTS="..."' work from GDB's build dir. 2014-03-12 19:52:00 +00:00
gold autoreconf 2014-03-12 15:02:00 +10:30
gprof autoreconf 2014-03-12 15:02:00 +10:30
include sim: constify arg to sim_do_command 2014-03-10 22:57:29 -04:00
intl
ld autoreconf 2014-03-12 15:02:00 +10:30
libdecnumber
libiberty
opcodes autoreconf 2014-03-12 15:02:00 +10:30
readline
sim Add myself as the maintainer for the MSP430 sim. 2014-03-12 11:02:57 +00:00
texinfo
.cvsignore
.gitignore
COPYING
COPYING.LIB
COPYING.LIBGLOSS
COPYING.NEWLIB
COPYING3
COPYING3.LIB
ChangeLog
MAINTAINERS
Makefile.def
Makefile.in
Makefile.tpl
README
README-maintainer-mode
compile
config-ml.in
config.guess
config.rpath
config.sub
configure
configure.ac
depcomp
djunpack.bat
install-sh
libtool.m4
ltgcc.m4
ltmain.sh
ltoptions.m4
ltsugar.m4
ltversion.m4
lt~obsolete.m4
makefile.vms
missing
mkdep
mkinstalldirs
move-if-change
setup.com
src-release
symlink-tree
ylwrap

README

		   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.