README for LD
|
README for LD
|
|
|
This is the GNU linker. It is distributed with other "binary
|
This is the GNU linker. It is distributed with other "binary
|
utilities" which should be in ../binutils. See ../binutils/README for
|
utilities" which should be in ../binutils. See ../binutils/README for
|
more general notes, including where to send bug reports.
|
more general notes, including where to send bug reports.
|
|
|
There are many features of the linker:
|
There are many features of the linker:
|
|
|
* The linker uses a Binary File Descriptor library (../bfd)
|
* The linker uses a Binary File Descriptor library (../bfd)
|
that it uses to read and write object files. This helps
|
that it uses to read and write object files. This helps
|
insulate the linker itself from the format of object files.
|
insulate the linker itself from the format of object files.
|
|
|
* The linker supports a number of different object file
|
* The linker supports a number of different object file
|
formats. It can even handle multiple formats at once:
|
formats. It can even handle multiple formats at once:
|
Read two input formats and write a third.
|
Read two input formats and write a third.
|
|
|
* The linker can be configured for cross-linking.
|
* The linker can be configured for cross-linking.
|
|
|
* The linker supports a control language.
|
* The linker supports a control language.
|
|
|
* There is a user manual (ld.texinfo), as well as the
|
* There is a user manual (ld.texinfo), as well as the
|
beginnings of an internals manual (ldint.texinfo).
|
beginnings of an internals manual (ldint.texinfo).
|
|
|
Installation
|
Installation
|
============
|
============
|
|
|
See ../binutils/README.
|
See ../binutils/README.
|
|
|
If you want to make a cross-linker, you may want to specify
|
If you want to make a cross-linker, you may want to specify
|
a different search path of -lfoo libraries than the default.
|
a different search path of -lfoo libraries than the default.
|
You can do this by setting the LIB_PATH variable in ./Makefile
|
You can do this by setting the LIB_PATH variable in ./Makefile
|
or using the --with-lib-path configure switch.
|
or using the --with-lib-path configure switch.
|
|
|
To build just the linker, make the target all-ld from the top level
|
To build just the linker, make the target all-ld from the top level
|
directory (one directory above this one).
|
directory (one directory above this one).
|
|
|
Porting to a new target
|
Porting to a new target
|
=======================
|
=======================
|
|
|
See the ldint.texinfo manual.
|
See the ldint.texinfo manual.
|
|
|
Reporting bugs etc
|
Reporting bugs etc
|
===========================
|
===========================
|
|
|
See ../binutils/README.
|
See ../binutils/README.
|
|
|
Known problems
|
Known problems
|
==============
|
==============
|
|
|
The Solaris linker normally exports all dynamic symbols from an
|
The Solaris linker normally exports all dynamic symbols from an
|
executable. The GNU linker does not do this by default. This is
|
executable. The GNU linker does not do this by default. This is
|
because the GNU linker tries to present the same interface for all
|
because the GNU linker tries to present the same interface for all
|
similar targets (in this case, all native ELF targets). This does not
|
similar targets (in this case, all native ELF targets). This does not
|
matter for normal programs, but it can make a difference for programs
|
matter for normal programs, but it can make a difference for programs
|
which try to dlopen an executable, such as PERL or Tcl. You can make
|
which try to dlopen an executable, such as PERL or Tcl. You can make
|
the GNU linker export all dynamic symbols with the -E or
|
the GNU linker export all dynamic symbols with the -E or
|
--export-dynamic command line option.
|
--export-dynamic command line option.
|
|
|
HP/UX 9.01 has a shell bug that causes the linker scripts to be
|
HP/UX 9.01 has a shell bug that causes the linker scripts to be
|
generated incorrectly. The symptom of this appears to be "fatal error
|
generated incorrectly. The symptom of this appears to be "fatal error
|
- scanner input buffer overflow" error messages. There are various
|
- scanner input buffer overflow" error messages. There are various
|
workarounds to this:
|
workarounds to this:
|
* Build and install bash, and build with "make SHELL=bash".
|
* Build and install bash, and build with "make SHELL=bash".
|
* Update to a version of HP/UX with a working shell (e.g., 9.05).
|
* Update to a version of HP/UX with a working shell (e.g., 9.05).
|
* Replace "(. ${srcdir}/scripttempl/${SCRIPT_NAME}.sc)" in
|
* Replace "(. ${srcdir}/scripttempl/${SCRIPT_NAME}.sc)" in
|
genscripts.sh with "sh ${srcdir}..." (no parens) and make sure the
|
genscripts.sh with "sh ${srcdir}..." (no parens) and make sure the
|
emulparams script used exports any shell variables it sets.
|
emulparams script used exports any shell variables it sets.
|
|
|
