mirror of
https://review.haiku-os.org/buildtools
synced 2025-02-22 21:57:41 +01:00
465fb4d4a7
This aligns legacy gcc with the changes to gcc4 committed in 4192115 and the two subsequent commits. It also disables legacy ld's default behaviour of recursively resolving shared-library dependencies at link time, preventing missing-library warnings during the build and aligning ld's behaviour with that of more recent versions. gcc2: * CPP_SPEC: Replace non-existent command-line options with valid equivalents. * CC1_SPEC: Remove non-existent "no-fpic" option; add "fno-pic" and "fno-PIC" as options that disable the generation of position-independent code; use "-fPIC" by default. * LINK_SPEC: Pass "-shared" to the linker only if it was passed to gcc; output position-independent executables by default, exporting all symbols to match the behaviour of "-shared"; when building a dynamically linked executable, do not recursively add shared libraries as dependencies but do allow unresolved symbols in them; specify "-Bsymbolic" only when building a shared library. * All: Wrap lines at 80 columns; use more compact notation where available. ld: * Do not recursively resolve shared-library dependencies when building an executable if the "--no-add-needed" and "--allow-shlib-undefined" options are in effect. This effectively backports binutils commits 8fbb09e and 4706eab. Signed-off-by: Jérôme Duval <jerome.duval@gmail.com>
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.