mirror of
https://github.com/bminor/binutils-gdb.git
synced 2026-02-04 08:41:30 +00:00
9f8be1f638
This shows the fruits of the recent ctf_err rework: the fusion of a bunch of error codes for which we had different error codes solely so that users could see different output in the ctf_errmsg(). Now that we have an error-handling scheme which can produce the function name and arbitrary extra printf()ed strings, we can merge a whole bunch of these codes together, making the codes purely semantic and much less granular, since we only really care that an error code is unambiguous with respect to any given API function (e.g. if ctf_add_forward() and ctf_member_count() both return ECTF_WRONGTYPE, you know perfectly well what it means in each case, even though it means something quite different: you can't make a forward to nonforwardable types like ints, and you can't count the members of a basic type.) There is one tiny semantic change of sorts: ctf_member_info(), ctf_enum_name() and ctf_enum_value() used to set an error if the name specified wasn't found. This is a fairly expected case, so we change it to a warning. A message is still logged on the error/warning stream, and ECTF_NONAME is set as the ctf_errno; if the caller handles it, they can use ctf_errwarning_remove() to remove the most ECTF_NONAME from the stream once they've done so. (Among all the removed ECTF_NOT* error codes, we have kept one, ECTF_NOTREF, because it is actually useful to be able to distinguish "you passed in the outright wrong kind" from "this type just doesn't point to another one", and some existing callers do make this distinction.) Error code count: 78 -> 63: 15 removed. More will go.
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, and so on. 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.