Remove remnants of NAMES_HAVE_UNDERSCORE.
[deliverable/binutils-gdb.git] / binutils / README
CommitLineData
d08a5233
PB
1This is a BETA release of a completely rewritten binutils distribution.
2The linker (ld) has been moved into a separate directory,
3which should be ../ld. Linker-specific notes are in ../ld/README.
4
5These programs have been tested on various architectures.
6Most recently tested are sun3 and sun4s running sunos4,
7as well as Sony News running newsos3.
8However, since this is a beta release taken directly from an
9evolving source tree, there might be some problems. In particular,
10the programs have not been ported to as many machines as the
11old binutils. There are also features of the old versions
12that are missing on the new programs. We would appreciate
13patches to make things run on other machines; especially welcome
14are fixes for what used to work on the old programs!
15
16Unpacking and Installation -- quick overview
17==========================
18
19In this release, the binary utilities, the linker, the generic GNU include
20files, the BFD ("binary file description") library, and getopt all have
21directories of their own underneath the binutils-2.0 directory.
22The idea is that a variety of GNU tools can
23share a common copy of these things. Configuration scripts and
24makefiles exist to cruise up and down this directory tree and
25automatically build all the pieces in the right order.
26
27When you unpack the binutils-2.0.tar.Z file, you'll get a directory called
28something like `binutils-2.0', which contains:
29
30 DOC.configure README config/ configure* ld/
31 Makefile bfd/ config.status* configure.in libiberty/
32 Makefile.in binutils/ config.sub include/ texinfo/
33
34To build binutils, you can just do:
35
36 cd binutils-2.0
37 ./configure HOSTTYPE (e.g. sun4, decstation)
38 make
39 make install # copies the programs files into /usr/local/bin by default.
40
41This will configure and build all the libraries as well as binutils
42and the linker.
43
44The binutils can be used in a cross-development environment.
45The file DOC.configure contains more information.
46
47Porting
48=======
49Binutils-2.0 supports many different architectures, but there
50are many more not supported, including some that were supported
51by earlier versions. We are hoping for volunteers to
52improve this situation.
53
54The major effort in porting binutils to a new host and/or target
55architecture involves the BFD library. There is some documentation
56in ../bfd/doc. The file ../gdb/doc/gdbint.texinfo (distributed
57with gdb-3.2) may also be of help.
58
59If your system uses some variant of old-style a.out-format,
60you can start with a copy of bfd/newsos3.c, and edit it to fit.
61(You may also need to tweak bfd/aout-target.h.)
62Alternatively, you could use the host-aout.c target. This is a
63special kludge that only works for native (non-cross) configurations.
64
65Reporting bugs
66==============
67If you can't track down a bug and send suggestions/patches
68for fixes, you should probably *not* be using this release.
69I cannot work on finding bugs at this stage (except for
70Cygnus-supported configurations). But if you have suggestions
71or patches, send them to bothner@cygnus.com, for now.
72(After the official release, the correct address will
73be bug-gnu-utils@ai.mit.edu.)
This page took 0.047203 seconds and 4 git commands to generate.