buildtools/binutils
Adrien Destugues 198e0fde5e haiku: Get sparc buildtools going
- If kallisti5 is having fun with RISC-V, why can't I too?
- Gets as far as complaining we don't have a libsolv package in
  non-bootstrap builds

Change-Id: I0bb2b632d8f9007d5ad130f8cfddda36787050fc
Reviewed-on: https://review.haiku-os.org/c/1060
Reviewed-by: Alex von Gluck IV <kallisti5@unixzen.com>
2019-02-19 18:28:17 +00:00
..
bfd haiku: Get sparc buildtools going 2019-02-19 18:28:17 +00:00
binutils Merge binutils 2.28.1 2017-08-06 14:09:36 +02:00
config import binutils 2.28.1 2017-08-05 16:32:14 +02:00
cpu import binutils 2.28.1 2017-08-05 16:32:14 +02:00
elfcpp import binutils 2.28.1 2017-08-05 16:32:14 +02:00
etc import binutils 2.27 2016-10-10 16:55:00 +02:00
gas haiku: Get sparc buildtools going 2019-02-19 18:28:17 +00:00
gold import binutils 2.28.1 2017-08-05 16:32:14 +02:00
gprof Merge binutils 2.28.1 2017-08-06 14:09:36 +02:00
include import binutils 2.28.1 2017-08-05 16:32:14 +02:00
intl import binutils 2.26 2016-02-10 18:58:24 +01:00
ld haiku: Get sparc buildtools going 2019-02-19 18:28:17 +00:00
libiberty import binutils 2.28.1 2017-08-05 16:32:14 +02:00
opcodes Merge binutils 2.28.1 2017-08-06 14:09:36 +02:00
texinfo
zlib import binutils 2.28.1 2017-08-05 16:32:14 +02:00
ChangeLog import binutils 2.28.1 2017-08-05 16:32:14 +02:00
compile import binutils 2.26 2016-02-10 18:58:24 +01:00
config-ml.in import binutils 2.26 2016-02-10 18:58:24 +01:00
config.guess import binutils 2.28.1 2017-08-05 16:32:14 +02:00
config.rpath
config.sub import binutils 2.28.1 2017-08-05 16:32:14 +02:00
configure Merge binutils 2.28.1 2017-08-06 14:09:36 +02:00
configure.ac Merge binutils 2.28.1 2017-08-06 14:09:36 +02:00
COPYING
COPYING3
COPYING3.LIB
COPYING.LIB
depcomp import binutils 2.26 2016-02-10 18:58:24 +01:00
install-sh import binutils 2.26 2016-02-10 18:58:24 +01:00
libtool.m4 Merge binutils 2.28.1 2017-08-06 14:09:36 +02:00
lt~obsolete.m4
ltgcc.m4
ltmain.sh
ltoptions.m4
ltsugar.m4
ltversion.m4
MAINTAINERS import binutils 2.26 2016-02-10 18:58:24 +01:00
Makefile.def import binutils 2.27 2016-10-10 16:55:00 +02:00
Makefile.in import binutils 2.27 2016-10-10 16:55:00 +02:00
Makefile.tpl import binutils 2.27 2016-10-10 16:55:00 +02:00
makefile.vms
md5.sum import binutils 2.28.1 2017-08-05 16:32:14 +02:00
missing import binutils 2.26 2016-02-10 18:58:24 +01:00
mkdep
mkinstalldirs import binutils 2.26 2016-02-10 18:58:24 +01:00
move-if-change import binutils 2.26 2016-02-10 18:58:24 +01:00
README
README-maintainer-mode
setup.com
src-release.sh import binutils 2.27 2016-10-10 16:55:00 +02:00
symlink-tree
ylwrap import binutils 2.26 2016-02-10 18:58:24 +01:00

		   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.