Options For Directory Search - Red Hat ENTERPRISE LINUX 4 Manual

Chapter 4. GCC Command Options
options that were used to generate code (
1
this option.
-shared-libgcc
-static-libgcc
On systems that provide
shared or static version respectively. If no shared version of
was configured, these options have no effect.
There are several situations in which an application should use the shared
the static version. The most common of these is when the application wishes to throw and catch
exceptions across different shared libraries. In that case, each of the libraries as well as the appli-
cation itself should use the shared
Therefore, the G++ and GCJ drivers automatically add
shared library or a main executable, because C++ and Java programs typically use exceptions, so
this is the right thing to do.
If, instead, you use the GCC driver to create shared libraries, you may find that they will not
always be linked with the shared
non-GNU linker or a GNU linker that does not support option
shared version of
linker and optimize away the linking with the shared version of
version of libgcc by default. This allows exceptions to propagate through such shared libraries,
without incurring relocation costs at library load time.
However, if a library or main executable is supposed to throw or catch exceptions, you must link
it using the G++ or GCJ driver, as appropriate for the languages used in the program, or using
the option
-shared-libgcc
-symbolic
Bind references to global symbols when building a shared object. Warn about any unresolved
references (unless overridden by the link editor option
a few systems support this option.
-Xlinker
option
Pass as an option to the linker. You can use this to supply system-specific linker options
option
which GCC does not know how to recognize.
If you want to pass an option that takes an argument, you must use
option and once for the argument. For example, to pass
write
-Xlinker -assert -Xlinker definitions
"-assert definitions"
is not what the linker expects.
-Wl,
option
Pass as an option to the linker. If
option
options at the commas.
-u
symbol
Pretend the symbol
can use multiple times with different symbols to force loading of additional library modules.
-u
1. On some systems,
multi-libbed systems,
gcc -shared
the correct flags may lead to subtle defects. Supplying them in cases where they are not necessary is innocuous.
as a shared library, these options force the use of either the
libgcc
libgcc
libgcc
into shared libraries by default. Otherwise, it will take advantage of the
libgcc
, such that it is linked with the shared
, because this passes the entire string as a single argument, which
is undefined, to force linking of library modules to define it. You
symbol
needs to build supplementary stub code for constructors to work. On
gcc -shared
must select the correct support libraries to link against. Failing to supply
, , or model suboptions) when you specify
-fpic -fPIC
libgcc
.
-shared-libgcc
. If GCC finds, at its configuration time, that you have a
-Xlinker -z -Xlinker defs
-assert definitions
. It does not work to write
contains commas, it is split into multiple
option
was built when the compiler
libgcc
whenever you build a
, it will link the
-eh-frame-hdr
, linking with the static
libgcc
.
libgcc
twice, once for the
-Xlinker
83
instead of
). Only
, you must
-Xlinker