1 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
2 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
3 <html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 2. Setup</title><meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /><meta name="keywords" content=" ISO C++ , library " /><link rel="start" href="../spine.html" title="The GNU C++ Library Documentation" /><link rel="up" href="intro.html" title="Part I. Introduction" /><link rel="prev" href="bk01pt01ch01s03.html" title="Bugs" /><link rel="next" href="build.html" title="Build" /></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 2. Setup</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="bk01pt01ch01s03.html">Prev</a> </td><th width="60%" align="center">Part I. Introduction</th><td width="20%" align="right"> <a accesskey="n" href="build.html">Next</a></td></tr></table><hr /></div><div class="chapter" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="manual.intro.setup"></a>Chapter 2. Setup</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="bk01pt01ch02.html#manual.intro.setup.configure">Configure</a></span></dt><dt><span class="sect1"><a href="build.html">Build</a></span></dt><dd><dl><dt><span class="sect2"><a href="build.html#build.prereq">Prerequisites</a></span></dt><dt><span class="sect2"><a href="build.html#build.configure">Make</a></span></dt></dl></dd><dt><span class="sect1"><a href="test.html">Test</a></span></dt><dd><dl><dt><span class="sect2"><a href="test.html#test.organization">Organization</a></span></dt><dt><span class="sect2"><a href="test.html#test.naming">Naming Conventions</a></span></dt><dt><span class="sect2"><a href="test.html#test.utils">Utilities</a></span></dt><dt><span class="sect2"><a href="test.html#test.run">Running the Testsuite</a></span></dt><dt><span class="sect2"><a href="test.html#test.new_tests">New Test Cases</a></span></dt><dt><span class="sect2"><a href="test.html#test.dejagnu">Test Harness Details</a></span></dt><dt><span class="sect2"><a href="test.html#test.future">Future</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="manual.intro.setup.configure"></a>Configure</h2></div></div></div><p>
4 Here are some of the non-obvious options to libstdc++'s configure.
7 <a class="ulink" href="http://www.gnu.org/software/autoconf/manual/autoconf-2.57/html_node/autoconf_131.html#SEC131" target="_top">they
8 all have opposite forms as well</a>
9 (enable/disable and with/without). The defaults are for <span class="emphasis"><em>current
10 development sources</em></span>, which may be different than those for
12 </p><p>The canonical way to find out the configure options that are
13 available for a given set of libstdc++ sources is to go to the
14 source directory and then type:<code class="code"> ./configure --help</code>
15 </p><div class="variablelist"><dl><dt><span class="term"><code class="code">--enable-multilib</code>[default]</span></dt><dd><p>This is part of the generic multilib support for building cross
16 compilers. As such, targets like "powerpc-elf" will have
17 libstdc++ built many different ways: "-msoft-float"
18 and not, etc. A different libstdc++ will be built for each of
19 the different multilib versions. This option is on by default.
20 </p></dd><dt><span class="term"><code class="code">--enable-sjlj-exceptions</code></span></dt><dd><p>Forces old, set-jump/long-jump exception handling model. If
21 at all possible, the new, frame unwinding exception handling routines
22 should be used instead, as they significantly reduce both
23 runtime memory usage and executable size. This option can
24 change the library ABI.
25 </p></dd><dt><span class="term"><code class="code">--enable-version-specific-runtime-libs</code></span></dt><dd><p>Specify that run-time libraries should be installed in the
26 compiler-specific subdirectory (i.e.,
27 <code class="code">${libdir}/gcc-lib/${target_alias}/${gcc_version}</code>)
28 instead of <code class="code">${libdir}</code>. This option is useful if you
29 intend to use several versions of gcc in parallel. In addition,
30 libstdc++'s include files will be installed in
31 <code class="code">${libdir}/gcc-lib/${target_alias}/${gcc_version}/include/g++</code>,
32 unless you also specify
33 <code class="literal">--with-gxx-include-dir=<code class="filename">dirname</code></code> during configuration.
34 </p></dd><dt><span class="term"><code class="code">--with-gxx-include-dir=<include-files dir></code></span></dt><dd><p>Adds support for named libstdc++ include directory. For instance,
35 the following puts all the libstdc++ headers into a directory
36 called "2.97-20001008" instead of the usual
38 </p><pre class="programlisting">
39 --with-gxx-include-dir=/foo/H-x86-gcc-3-c-gxx-inc/include/2.97-20001008</pre></dd><dt><span class="term"><code class="code">--enable-cstdio</code></span></dt><dd><p>This is an abbreviated form of <code class="code">'--enable-cstdio=stdio'</code>
40 (described next). This option can change the library ABI.
41 </p></dd><dt><span class="term"><code class="code">--enable-cstdio=OPTION</code></span></dt><dd><p>Select a target-specific I/O package. At the moment, the only
42 choice is to use 'stdio', a generic "C" abstraction.
43 The default is 'stdio'.
44 </p></dd><dt><span class="term"><code class="code">--enable-clocale</code></span></dt><dd><p>This is an abbreviated form of <code class="code">'--enable-clocale=generic'</code>
45 (described next). This option can change the library ABI.
46 </p></dd><dt><span class="term"><code class="code">--enable-clocale=OPTION</code></span></dt><dd><p>Select a target-specific underlying locale package. The
47 choices are 'ieee_1003.1-2001' to specify an X/Open, Standard Unix
48 (IEEE Std. 1003.1-2001) model based on langinfo/iconv/catgets,
49 'gnu' to specify a model based on functionality from the GNU C
50 library (langinfo/iconv/gettext) (from <a class="ulink" href="http://sources.redhat.com/glibc/" target="_top">glibc</a>, the GNU C
51 library), or 'generic' to use a generic "C"
52 abstraction which consists of "C" locale info.
53 </p><p>As part of the configuration process, the "C" library is
54 probed both for sufficient vintage, and installed locale
55 data. If either of these elements are not present, the C++
56 locale model default to 'generic.' On glibc-based systems of
57 version 2.2.5 and above with installed locale files, 'gnu' is
58 automatically selected.
59 </p></dd><dt><span class="term"><code class="code">--enable-libstdcxx-allocator</code></span></dt><dd><p>This is an abbreviated form of
60 <code class="code">'--enable-libstdcxx-allocator=auto'</code> (described
61 next). This option can change the library ABI.
62 </p></dd><dt><span class="term"><code class="code">--enable-libstdcxx-allocator=OPTION </code></span></dt><dd><p>Select a target-specific underlying std::allocator. The
63 choices are 'new' to specify a wrapper for new, 'malloc' to
64 specify a wrapper for malloc, 'mt' for a fixed power of two allocator
65 (<a class="ulink" href="ext/mt_allocator.html" target="_top">documented</a> under extensions),
66 'pool' for the SGI pooled allocator or 'bitmap' for a bitmap allocator.
67 This option can change the library ABI.
68 </p></dd><dt><span class="term"><code class="code">--enable-cheaders=OPTION</code></span></dt><dd><p>This allows the user to define the approach taken for C header
69 compatibility with C++. Options are c, c_std, and c_global.
70 These correspond to the source directory's include/c,
71 include/c_std, and include/c_global, and may also include
72 include/c_compatibility. The default is c_global.
73 </p></dd><dt><span class="term"><code class="code">--enable-threads</code></span></dt><dd><p>This is an abbreviated form of <code class="code">'--enable-threads=yes'</code>
74 (described next). This option can change the library ABI.
75 </p></dd><dt><span class="term"><code class="code">--enable-threads=OPTION</code></span></dt><dd><p>Select a threading library. A full description is given in the
76 general <a class="ulink" href="http://gcc.gnu.org/install/configure.html" target="_top">compiler
77 configuration instructions</a>.
78 </p></dd><dt><span class="term"><code class="code">--enable-libstdcxx-debug</code></span></dt><dd><p>Build separate debug libraries in addition to what is normally built.
79 By default, the debug libraries are compiled with
80 <code class="code"> CXXFLAGS='-g3 -O0'</code>
81 , are installed in <code class="code">${libdir}/debug</code>, and have the
82 same names and versioning information as the non-debug
83 libraries. This option is off by default.
84 </p><p>Note this make command, executed in
85 the build directory, will do much the same thing, without the
86 configuration difference and without building everything twice:
87 <code class="code">make CXXFLAGS='-g3 -O0' all</code>
88 </p></dd><dt><span class="term"><code class="code">--enable-libstdcxx-debug-flags=FLAGS</code></span></dt><dd><p>This option is only valid when <code class="code"> --enable-debug </code>
89 is also specified, and applies to the debug builds only. With
90 this option, you can pass a specific string of flags to the
91 compiler to use when building the debug versions of libstdc++.
92 FLAGS is a quoted string of options, like
93 </p><pre class="programlisting">
94 --enable-libstdcxx-debug-flags='-g3 -O1 -gdwarf-2'</pre></dd><dt><span class="term"><code class="code">--enable-cxx-flags=FLAGS</code></span></dt><dd><p>With this option, you can pass a string of -f (functionality)
95 flags to the compiler to use when building libstdc++. This
96 option can change the library ABI. FLAGS is a quoted string of
98 </p><pre class="programlisting">
99 --enable-cxx-flags='-fvtable-gc -fomit-frame-pointer -ansi'</pre><p>
100 Note that the flags don't necessarily have to all be -f flags,
101 as shown, but usually those are the ones that will make sense
102 for experimentation and configure-time overriding.
103 </p><p>The advantage of --enable-cxx-flags over setting CXXFLAGS in
104 the 'make' environment is that, if files are automatically
105 rebuilt, the same flags will be used when compiling those files
106 as well, so that everything matches.
107 </p><p>Fun flags to try might include combinations of
108 </p><pre class="programlisting">
112 -fvtable-gc</pre><p>and opposite forms (-fno-) of the same. Tell us (the libstdc++
113 mailing list) if you discover more!
114 </p></dd><dt><span class="term"><code class="code">--enable-c99</code></span></dt><dd><p>The "long long" type was introduced in C99, along
115 with many other functions for wide characters, and math
116 classification macros, etc. If enabled, all C99 functions not
117 specified by the C++ standard will be put into <code class="code">namespace
118 __gnu_cxx</code>, and then all these names will
119 be injected into namespace std, so that C99 functions can be
120 used "as if" they were in the C++ standard (as they
121 will eventually be in some future revision of the standard,
122 without a doubt). By default, C99 support is on, assuming the
123 configure probes find all the necessary functions and bits
124 necessary. This option can change the library ABI.
125 </p></dd><dt><span class="term"><code class="code">--enable-wchar_t</code>[default]</span></dt><dd><p>Template specializations for the "wchar_t" type are
126 required for wide character conversion support. Disabling
127 wide character specializations may be expedient for initial
128 porting efforts, but builds only a subset of what is required by
129 ISO, and is not recommended. By default, this option is on.
130 This option can change the library ABI.
131 </p></dd><dt><span class="term"><code class="code">--enable-long-long </code></span></dt><dd><p>The "long long" type was introduced in C99. It is
132 provided as a GNU extension to C++98 in g++. This flag builds
133 support for "long long" into the library (specialized
134 templates and the like for iostreams). This option is on by default:
135 if enabled, users will have to either use the new-style "C"
136 headers by default (i.e., <cmath> not <math.h>)
137 or add appropriate compile-time flags to all compile lines to
138 allow "C" visibility of this feature (on GNU/Linux,
139 the flag is -D_ISOC99_SOURCE, which is added automatically via
140 CPLUSPLUS_CPP_SPEC's addition of _GNU_SOURCE).
141 This option can change the library ABI.
142 </p></dd><dt><span class="term"><code class="code">--enable-fully-dynamic-string</code></span></dt><dd><p>This option enables a special version of basic_string avoiding
143 the optimization that allocates empty objects in static memory.
144 Mostly useful together with shared memory allocators, see PR
145 libstdc++/16612 for details.
146 </p></dd><dt><span class="term"><code class="code">--enable-concept-checks</code></span></dt><dd><p>This turns on additional compile-time checks for instantiated
147 library templates, in the form of specialized templates,
148 <a class="ulink" href="19_diagnostics/howto.html#3" target="_top">described here</a>. They
149 can help users discover when they break the rules of the STL, before
151 </p></dd><dt><span class="term"><code class="code">--enable-symvers[=style]</code></span></dt><dd><p>In 3.1 and later, tries to turn on symbol versioning in the
152 shared library (if a shared library has been
153 requested). Values for 'style' that are currently supported
154 are 'gnu', 'gnu-versioned-namespace', 'darwin', and
155 'darwin-export'. Both gnu- options require that a recent
156 version of the GNU linker be in use. Both darwin options are
157 equivalent. With no style given, the configure script will try
158 to guess correct defaults for the host system, probe to see if
159 additional requirements are necessary and present for
160 activation, and if so, will turn symbol versioning on. This
161 option can change the library ABI.
162 </p></dd><dt><span class="term"><code class="code">--enable-visibility</code></span></dt><dd><p> In 4.2 and later, enables or disables visibility attributes.
163 If enabled (as by default), and the compiler seems capable of
164 passing the simple sanity checks thrown at it, adjusts items
165 in namespace std, namespace std::tr1, and namespace __gnu_cxx
166 so that -fvisibility options work.
167 </p></dd><dt><span class="term"><code class="code">--enable-libstdcxx-pch</code></span></dt><dd><p>In 3.4 and later, tries to turn on the generation of
168 stdc++.h.gch, a pre-compiled file including all the standard
169 C++ includes. If enabled (as by default), and the compiler
170 seems capable of passing the simple sanity checks thrown at
171 it, try to build stdc++.h.gch as part of the make process.
172 In addition, this generated file is used later on (by appending <code class="code">
173 --include bits/stdc++.h </code> to CXXFLAGS) when running the
175 </p></dd><dt><span class="term"><code class="code">--disable-hosted-libstdcxx</code></span></dt><dd><p>
176 By default, a complete <span class="emphasis"><em>hosted</em></span> C++ library is
177 built. The C++ Standard also describes a
178 <span class="emphasis"><em>freestanding</em></span> environment, in which only a
179 minimal set of headers are provided. This option builds such an
181 </p></dd></dl></div></div></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="bk01pt01ch01s03.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="intro.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="build.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Bugs </td><td width="20%" align="center"><a accesskey="h" href="../spine.html">Home</a></td><td width="40%" align="right" valign="top"> Build</td></tr></table></div></body></html>
projects / l4.git / blob