Binutils with MCST patches
Go to file
Simon Marchi 48ffa2b8cd Fix constness problem in ioscm_make_gdb_stdio_port
ioscm_make_gdb_stdio_port passes const char pointers (literal strings) to
scm_mode_bits, which takes a non-const char pointer.  Ideally, we would
change scm_mode_bits to take a const char pointer, but it's not part of
an API we control.

Instead, it's easy enough to build the string to pass to scm_mode_bits in
a (non-const) char array and pass that.

gdb/ChangeLog:

	* guile/scm-ports.c (ioscm_make_gdb_stdio_port): Pass non-const
	char pointer to scm_mode_bits.
2015-10-26 08:41:39 -04:00
bfd Automatic date update in version.in 2015-10-26 00:00:08 +00:00
binutils binutils/objcopy.c (setup_section): missing extract_symbol part 2015-10-22 16:12:35 +02:00
config
cpu
elfcpp Gold: Don't fail on R_X86_64_[REX_]GOTPCRELX relocations 2015-10-22 04:56:57 -07:00
etc
gas Add support for MSP430 silicon errata to the assembler. 2015-10-22 16:25:46 +01:00
gdb Fix constness problem in ioscm_make_gdb_stdio_port 2015-10-26 08:41:39 -04:00
gold Gold: Don't fail on R_X86_64_[REX_]GOTPCRELX relocations 2015-10-22 04:56:57 -07:00
gprof
include Add "-z call-nop=PADDING" option to ld 2015-10-22 04:56:39 -07:00
intl
ld Add a test for PR ld/19167 2015-10-23 04:23:51 -07:00
libdecnumber
libiberty
opcodes Add missing changelog entries 2015-10-14 12:19:39 +02:00
readline
sim sim: ft32: test coverage for link parameters and PM write port 2015-10-12 20:23:26 -04:00
texinfo
zlib
.cvsignore
.gitattributes
.gitignore
ChangeLog Reset x86 Linux targets to not compressing debug sections by default. Enable compression of debug sections by default in the linker, if so configured. 2015-10-21 13:15:39 +01:00
compile
config-ml.in
config.guess
config.rpath
config.sub
configure Reset x86 Linux targets to not compressing debug sections by default. Enable compression of debug sections by default in the linker, if so configured. 2015-10-21 13:15:39 +01:00
configure.ac Reset x86 Linux targets to not compressing debug sections by default. Enable compression of debug sections by default in the linker, if so configured. 2015-10-21 13:15:39 +01:00
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
README
README-maintainer-mode
setup.com
src-release.sh
symlink-tree
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.