Red Hat ENTERPRISE LINUX 3 - USING ID Using Instructions page 20

Using ld, the gnu linker
Hide thumbs Also See for ENTERPRISE LINUX 3 - USING ID:
Table of Contents

Advertisement

16
set but
-no-allow-shlib-undefined
regular object files will trigger an error, but undefined symbols in shared objects will be ignored.
The reason that
ified at link time may not be the same one that is available at load time, so the symbols might
actually be resolvable at load time. Plus there are some systems, (eg BeOS) where undefined
symbols in shared libraries is normal since the kernel patches them at load time to select which
function is most appropriate for the current architecture. eg. to dynamically select an appropri-
ate memset function. Apparently it is also normal for HPPA shared libraries to have undefined
symbols.
-no-undefined-version
Normally when a symbol has an undefined version, the linker will ignore it. This option disallows
symbols with undefined version and a fatal error will be issued instead.
-no-warn-mismatch
Normally
will give an error if you try to link together input files that are mismatched for
ld
some reason, perhaps because they have been compiled for different processors or for different
endiannesses. This option tells
should only be used with care, in cases when you have taken some special action that ensures
that the linker errors are inappropriate.
-no-whole-archive
Turn off the effect of the
-noinhibit-exec
Retain the executable output file whenever it is still usable. Normally, the linker will not produce
an output file if it encounters errors during the link process; it exits without writing an output file
when it issues any error whatsoever.
-nostdlib
Only search library directories explicitly specified on the command line. Library directories spec-
ified in linker scripts (including linker scripts specified on the command line) are ignored.
-oformat
output-format
may be configured to support more than one kind of object file. If your
ld
this way, you can use the
file. Even when
to specify this, as
format on each machine.
ported by the BFD libraries. (You can list the available binary formats with
script command
it. Refer to Chapter 6 BFD.
-pie
-pic-executable
Create a position independent executable. This is currently only supported on ELF platforms.
Position independent executables are similar to shared libraries in that they are relocated by the
dynamic linker to the virtual address OS chooses for them (which can varry between invocations),
like normal dynamically linked executables they can be executed and symbols defined in the
executable cannot be overridden by shared libraries.
-allow-shlib-undefined
that it should silently permit such possible errors. This option
ld
-whole-archive
-oformat
is configured to support alternative object formats, you don't usually need
ld
should be configured to produce as a default output format the most usual
ld
output-format
can also specify the output format, but this option overrides
OUTPUT_FORMAT
is not, the net result will be that undefined symbols in
is the default is that the shared object being spec-
option for subsequent archive files.
option to specify the binary format for the output object
is a text string, the name of a particular format sup-
Chapter 3. Invocation
is configured
ld
.) The
objdump -i

Advertisement

Table of Contents
loading

This manual is also suitable for:

Enterprise linux 3

Table of Contents