configure.html revision 1.14
1 1.10 mrg <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> 2 1.10 mrg <html> 3 1.14 mrg <!-- Created by GNU Texinfo 6.8, https://www.gnu.org/software/texinfo/ --> 4 1.14 mrg <head> 5 1.14 mrg <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> 6 1.13 mrg <!-- Copyright (C) 1988-2020 Free Software Foundation, Inc. 7 1.1 mrg 8 1.10 mrg Permission is granted to copy, distribute and/or modify this document 9 1.3 skrll under the terms of the GNU Free Documentation License, Version 1.3 or 10 1.1 mrg any later version published by the Free Software Foundation; with no 11 1.1 mrg Invariant Sections, the Front-Cover texts being (a) (see below), and 12 1.1 mrg with the Back-Cover Texts being (b) (see below). A copy of the 13 1.10 mrg license is included in the section entitled "GNU 14 1.10 mrg Free Documentation License". 15 1.1 mrg 16 1.1 mrg (a) The FSF's Front-Cover Text is: 17 1.1 mrg 18 1.10 mrg A GNU Manual 19 1.1 mrg 20 1.1 mrg (b) The FSF's Back-Cover Text is: 21 1.1 mrg 22 1.10 mrg You have freedom to copy and modify this GNU Manual, like GNU 23 1.1 mrg software. Copies published by the Free Software Foundation raise 24 1.10 mrg funds for GNU development. --> 25 1.13 mrg <title>Installing GCC: Configuration</title> 26 1.10 mrg 27 1.13 mrg <meta name="description" content="Installing GCC: Configuration"> 28 1.13 mrg <meta name="keywords" content="Installing GCC: Configuration"> 29 1.10 mrg <meta name="resource-type" content="document"> 30 1.10 mrg <meta name="distribution" content="global"> 31 1.10 mrg <meta name="Generator" content="makeinfo"> 32 1.14 mrg <meta name="viewport" content="width=device-width,initial-scale=1"> 33 1.14 mrg 34 1.10 mrg <style type="text/css"> 35 1.10 mrg <!-- 36 1.14 mrg a.copiable-anchor {visibility: hidden; text-decoration: none; line-height: 0em} 37 1.10 mrg a.summary-letter {text-decoration: none} 38 1.10 mrg blockquote.indentedblock {margin-right: 0em} 39 1.10 mrg div.display {margin-left: 3.2em} 40 1.10 mrg div.example {margin-left: 3.2em} 41 1.10 mrg kbd {font-style: oblique} 42 1.10 mrg pre.display {font-family: inherit} 43 1.10 mrg pre.format {font-family: inherit} 44 1.10 mrg pre.menu-comment {font-family: serif} 45 1.10 mrg pre.menu-preformatted {font-family: serif} 46 1.10 mrg span.nolinebreak {white-space: nowrap} 47 1.10 mrg span.roman {font-family: initial; font-weight: normal} 48 1.10 mrg span.sansserif {font-family: sans-serif; font-weight: normal} 49 1.14 mrg span:hover a.copiable-anchor {visibility: visible} 50 1.10 mrg ul.no-bullet {list-style: none} 51 1.10 mrg --> 52 1.10 mrg </style> 53 1.10 mrg 54 1.10 mrg 55 1.1 mrg </head> 56 1.10 mrg 57 1.10 mrg <body lang="en"> 58 1.13 mrg <h1 class="settitle" align="center">Installing GCC: Configuration</h1> 59 1.10 mrg 60 1.10 mrg 61 1.10 mrg 62 1.10 mrg 63 1.10 mrg 64 1.10 mrg 65 1.10 mrg 66 1.10 mrg 67 1.10 mrg 68 1.10 mrg 69 1.10 mrg 70 1.10 mrg 71 1.10 mrg 72 1.10 mrg 73 1.10 mrg 74 1.10 mrg 75 1.10 mrg 76 1.10 mrg 77 1.10 mrg 78 1.14 mrg <span id="index-Configuration"></span> 79 1.14 mrg <span id="index-Installing-GCC_003a-Configuration"></span> 80 1.10 mrg 81 1.10 mrg <p>Like most GNU software, GCC must be configured before it can be built. 82 1.9 mrg This document describes the recommended configuration procedure 83 1.9 mrg for both native and cross targets. 84 1.10 mrg </p> 85 1.10 mrg <p>We use <var>srcdir</var> to refer to the toplevel source directory for 86 1.9 mrg GCC; we use <var>objdir</var> to refer to the toplevel build/object directory. 87 1.10 mrg </p> 88 1.11 mrg <p>If you obtained the sources by cloning the repository, <var>srcdir</var> 89 1.11 mrg must refer to the top <samp>gcc</samp> directory, the one where the 90 1.11 mrg <samp>MAINTAINERS</samp> file can be found, and not its <samp>gcc</samp> 91 1.11 mrg subdirectory, otherwise the build will fail. 92 1.10 mrg </p> 93 1.10 mrg <p>If either <var>srcdir</var> or <var>objdir</var> is located on an automounted NFS 94 1.10 mrg file system, the shell’s built-in <code>pwd</code> command will return 95 1.1 mrg temporary pathnames. Using these can lead to various sorts of build 96 1.10 mrg problems. To avoid this issue, set the <code>PWDCMD</code> environment 97 1.10 mrg variable to an automounter-aware <code>pwd</code> command, e.g., 98 1.10 mrg <code>pawd</code> or ‘<samp>amq -w</samp>’, during the configuration and build 99 1.1 mrg phases. 100 1.10 mrg </p> 101 1.10 mrg <p>First, we <strong>highly</strong> recommend that GCC be built into a 102 1.1 mrg separate directory from the sources which does <strong>not</strong> reside 103 1.1 mrg within the source tree. This is how we generally build GCC; building 104 1.10 mrg where <var>srcdir</var> == <var>objdir</var> should still work, but doesn’t 105 1.1 mrg get extensive testing; building where <var>objdir</var> is a subdirectory 106 1.1 mrg of <var>srcdir</var> is unsupported. 107 1.10 mrg </p> 108 1.10 mrg <p>If you have previously built GCC in the same directory for a 109 1.10 mrg different target machine, do ‘<samp>make distclean</samp>’ to delete all files 110 1.10 mrg that might be invalid. One of the files this deletes is <samp>Makefile</samp>; 111 1.10 mrg if ‘<samp>make distclean</samp>’ complains that <samp>Makefile</samp> does not exist 112 1.10 mrg or issues a message like “don’t know how to make distclean” it probably 113 1.1 mrg means that the directory is already suitably clean. However, with the 114 1.1 mrg recommended method of building in a separate <var>objdir</var>, you should 115 1.1 mrg simply use a different <var>objdir</var> for each target. 116 1.10 mrg </p> 117 1.10 mrg <p>Second, when configuring a native system, either <code>cc</code> or 118 1.10 mrg <code>gcc</code> must be in your path or you must set <code>CC</code> in 119 1.1 mrg your environment before running configure. Otherwise the configuration 120 1.1 mrg scripts may fail. 121 1.10 mrg </p> 122 1.1 mrg 123 1.10 mrg <p>To configure GCC: 124 1.10 mrg </p> 125 1.14 mrg <div class="example"> 126 1.14 mrg <pre class="example">% mkdir <var>objdir</var> 127 1.10 mrg % cd <var>objdir</var> 128 1.10 mrg % <var>srcdir</var>/configure [<var>options</var>] [<var>target</var>] 129 1.10 mrg </pre></div> 130 1.1 mrg 131 1.14 mrg <span id="Distributor-options"></span><h3 class="heading">Distributor options</h3> 132 1.1 mrg 133 1.1 mrg <p>If you will be distributing binary versions of GCC, with modifications 134 1.1 mrg to the source code, you should use the options described in this 135 1.1 mrg section to make clear that your version contains modifications. 136 1.10 mrg </p> 137 1.10 mrg <dl compact="compact"> 138 1.14 mrg <dt><span><code>--with-pkgversion=<var>version</var></code></span></dt> 139 1.10 mrg <dd><p>Specify a string that identifies your package. You may wish 140 1.1 mrg to include a build number or build date. This version string will be 141 1.10 mrg included in the output of <code>gcc --version</code>. This suffix does 142 1.10 mrg not replace the default version string, only the ‘<samp>GCC</samp>’ part. 143 1.10 mrg </p> 144 1.10 mrg <p>The default value is ‘<samp>GCC</samp>’. 145 1.10 mrg </p> 146 1.10 mrg </dd> 147 1.14 mrg <dt><span><code>--with-bugurl=<var>url</var></code></span></dt> 148 1.10 mrg <dd><p>Specify the URL that users should visit if they wish to report a bug. 149 1.1 mrg You are of course welcome to forward bugs reported to you to the FSF, 150 1.1 mrg if you determine that they are not bugs in your modifications. 151 1.10 mrg </p> 152 1.10 mrg <p>The default value refers to the FSF’s GCC bug tracker. 153 1.10 mrg </p> 154 1.10 mrg </dd> 155 1.14 mrg <dt><span><code>--with-documentation-root-url=<var>url</var></code></span></dt> 156 1.13 mrg <dd><p>Specify the URL root that contains GCC option documentation. The <var>url</var> 157 1.13 mrg should end with a <code>/</code> character. 158 1.13 mrg </p> 159 1.13 mrg <p>The default value is <a href="https://gcc.gnu.org/onlinedocs/">https://gcc.gnu.org/onlinedocs/</a>. 160 1.13 mrg </p> 161 1.13 mrg </dd> 162 1.14 mrg <dt><span><code>--with-changes-root-url=<var>url</var></code></span></dt> 163 1.13 mrg <dd><p>Specify the URL root that contains information about changes in GCC 164 1.13 mrg releases like <code>gcc-<var>version</var>/changes.html</code>. 165 1.13 mrg The <var>url</var> should end with a <code>/</code> character. 166 1.13 mrg </p> 167 1.13 mrg <p>The default value is <a href="https://gcc.gnu.org/">https://gcc.gnu.org/</a>. 168 1.13 mrg </p> 169 1.13 mrg </dd> 170 1.10 mrg </dl> 171 1.1 mrg 172 1.14 mrg <span id="Target-specification"></span><h3 class="heading">Target specification</h3> 173 1.10 mrg <ul> 174 1.10 mrg <li> GCC has code to correctly determine the correct value for <var>target</var> 175 1.1 mrg for nearly all native systems. Therefore, we highly recommend you do 176 1.1 mrg not provide a configure target when configuring a native compiler. 177 1.1 mrg 178 1.10 mrg </li><li> <var>target</var> must be specified as <samp>--target=<var>target</var></samp> 179 1.1 mrg when configuring a cross compiler; examples of valid targets would be 180 1.1 mrg m68k-elf, sh-elf, etc. 181 1.1 mrg 182 1.10 mrg </li><li> Specifying just <var>target</var> instead of <samp>--target=<var>target</var></samp> 183 1.10 mrg implies that the host defaults to <var>target</var>. 184 1.10 mrg </li></ul> 185 1.10 mrg 186 1.1 mrg 187 1.14 mrg <span id="Options-specification"></span><h3 class="heading">Options specification</h3> 188 1.1 mrg 189 1.1 mrg <p>Use <var>options</var> to override several configure time options for 190 1.10 mrg GCC. A list of supported <var>options</var> follows; ‘<samp>configure 191 1.10 mrg --help</samp>’ may list other options, but those not listed below may not 192 1.1 mrg work and should not normally be used. 193 1.10 mrg </p> 194 1.10 mrg <p>Note that each <samp>--enable</samp> option has a corresponding 195 1.10 mrg <samp>--disable</samp> option and that each <samp>--with</samp> option has a 196 1.10 mrg corresponding <samp>--without</samp> option. 197 1.10 mrg </p> 198 1.10 mrg <dl compact="compact"> 199 1.14 mrg <dt><span><code>--prefix=<var>dirname</var></code></span></dt> 200 1.10 mrg <dd><p>Specify the toplevel installation 201 1.1 mrg directory. This is the recommended way to install the tools into a directory 202 1.1 mrg other than the default. The toplevel installation directory defaults to 203 1.10 mrg <samp>/usr/local</samp>. 204 1.10 mrg </p> 205 1.10 mrg <p>We <strong>highly</strong> recommend against <var>dirname</var> being the same or a 206 1.1 mrg subdirectory of <var>objdir</var> or vice versa. If specifying a directory 207 1.10 mrg beneath a user’s home directory tree, some shells will not expand 208 1.10 mrg <var>dirname</var> correctly if it contains the ‘<samp>~</samp>’ metacharacter; use 209 1.10 mrg <code>$HOME</code> instead. 210 1.10 mrg </p> 211 1.10 mrg <p>The following standard <code>autoconf</code> options are supported. Normally you 212 1.1 mrg should not need to use these options. 213 1.10 mrg </p><dl compact="compact"> 214 1.14 mrg <dt><span><code>--exec-prefix=<var>dirname</var></code></span></dt> 215 1.10 mrg <dd><p>Specify the toplevel installation directory for architecture-dependent 216 1.1 mrg files. The default is <samp><var>prefix</var></samp>. 217 1.10 mrg </p> 218 1.10 mrg </dd> 219 1.14 mrg <dt><span><code>--bindir=<var>dirname</var></code></span></dt> 220 1.10 mrg <dd><p>Specify the installation directory for the executables called by users 221 1.10 mrg (such as <code>gcc</code> and <code>g++</code>). The default is 222 1.10 mrg <samp><var>exec-prefix</var>/bin</samp>. 223 1.10 mrg </p> 224 1.10 mrg </dd> 225 1.14 mrg <dt><span><code>--libdir=<var>dirname</var></code></span></dt> 226 1.10 mrg <dd><p>Specify the installation directory for object code libraries and 227 1.10 mrg internal data files of GCC. The default is <samp><var>exec-prefix</var>/lib</samp>. 228 1.10 mrg </p> 229 1.10 mrg </dd> 230 1.14 mrg <dt><span><code>--libexecdir=<var>dirname</var></code></span></dt> 231 1.10 mrg <dd><p>Specify the installation directory for internal executables of GCC. 232 1.10 mrg The default is <samp><var>exec-prefix</var>/libexec</samp>. 233 1.10 mrg </p> 234 1.10 mrg </dd> 235 1.14 mrg <dt><span><code>--with-slibdir=<var>dirname</var></code></span></dt> 236 1.10 mrg <dd><p>Specify the installation directory for the shared libgcc library. The 237 1.1 mrg default is <samp><var>libdir</var></samp>. 238 1.10 mrg </p> 239 1.10 mrg </dd> 240 1.14 mrg <dt><span><code>--datarootdir=<var>dirname</var></code></span></dt> 241 1.10 mrg <dd><p>Specify the root of the directory tree for read-only architecture-independent 242 1.10 mrg data files referenced by GCC. The default is <samp><var>prefix</var>/share</samp>. 243 1.10 mrg </p> 244 1.10 mrg </dd> 245 1.14 mrg <dt><span><code>--infodir=<var>dirname</var></code></span></dt> 246 1.10 mrg <dd><p>Specify the installation directory for documentation in info format. 247 1.10 mrg The default is <samp><var>datarootdir</var>/info</samp>. 248 1.10 mrg </p> 249 1.10 mrg </dd> 250 1.14 mrg <dt><span><code>--datadir=<var>dirname</var></code></span></dt> 251 1.10 mrg <dd><p>Specify the installation directory for some architecture-independent 252 1.1 mrg data files referenced by GCC. The default is <samp><var>datarootdir</var></samp>. 253 1.10 mrg </p> 254 1.10 mrg </dd> 255 1.14 mrg <dt><span><code>--docdir=<var>dirname</var></code></span></dt> 256 1.10 mrg <dd><p>Specify the installation directory for documentation files (other 257 1.10 mrg than Info) for GCC. The default is <samp><var>datarootdir</var>/doc</samp>. 258 1.10 mrg </p> 259 1.10 mrg </dd> 260 1.14 mrg <dt><span><code>--htmldir=<var>dirname</var></code></span></dt> 261 1.10 mrg <dd><p>Specify the installation directory for HTML documentation files. 262 1.1 mrg The default is <samp><var>docdir</var></samp>. 263 1.10 mrg </p> 264 1.10 mrg </dd> 265 1.14 mrg <dt><span><code>--pdfdir=<var>dirname</var></code></span></dt> 266 1.10 mrg <dd><p>Specify the installation directory for PDF documentation files. 267 1.1 mrg The default is <samp><var>docdir</var></samp>. 268 1.10 mrg </p> 269 1.10 mrg </dd> 270 1.14 mrg <dt><span><code>--mandir=<var>dirname</var></code></span></dt> 271 1.10 mrg <dd><p>Specify the installation directory for manual pages. The default is 272 1.10 mrg <samp><var>datarootdir</var>/man</samp>. (Note that the manual pages are only extracts 273 1.1 mrg from the full GCC manuals, which are provided in Texinfo format. The manpages 274 1.1 mrg are derived by an automatic conversion process from parts of the full 275 1.1 mrg manual.) 276 1.10 mrg </p> 277 1.10 mrg </dd> 278 1.14 mrg <dt><span><code>--with-gxx-include-dir=<var>dirname</var></code></span></dt> 279 1.10 mrg <dd><p>Specify 280 1.1 mrg the installation directory for G++ header files. The default depends 281 1.1 mrg on other configuration options, and differs between cross and native 282 1.1 mrg configurations. 283 1.10 mrg </p> 284 1.10 mrg </dd> 285 1.14 mrg <dt><span><code>--with-specs=<var>specs</var></code></span></dt> 286 1.10 mrg <dd><p>Specify additional command line driver SPECS. 287 1.3 skrll This can be useful if you need to turn on a non-standard feature by 288 1.10 mrg default without modifying the compiler’s source code, for instance 289 1.10 mrg <samp>--with-specs=%{!fcommon:%{!fno-common:-fno-common}}</samp>. 290 1.3 skrll See “Spec Files” in the main manual 291 1.10 mrg </p> 292 1.10 mrg </dd> 293 1.10 mrg </dl> 294 1.3 skrll 295 1.10 mrg </dd> 296 1.14 mrg <dt><span><code>--program-prefix=<var>prefix</var></code></span></dt> 297 1.10 mrg <dd><p>GCC supports some transformations of the names of its programs when 298 1.1 mrg installing them. This option prepends <var>prefix</var> to the names of 299 1.1 mrg programs to install in <var>bindir</var> (see above). For example, specifying 300 1.10 mrg <samp>--program-prefix=foo-</samp> would result in ‘<samp>gcc</samp>’ 301 1.10 mrg being installed as <samp>/usr/local/bin/foo-gcc</samp>. 302 1.10 mrg </p> 303 1.10 mrg </dd> 304 1.14 mrg <dt><span><code>--program-suffix=<var>suffix</var></code></span></dt> 305 1.10 mrg <dd><p>Appends <var>suffix</var> to the names of programs to install in <var>bindir</var> 306 1.10 mrg (see above). For example, specifying <samp>--program-suffix=-3.1</samp> 307 1.10 mrg would result in ‘<samp>gcc</samp>’ being installed as 308 1.10 mrg <samp>/usr/local/bin/gcc-3.1</samp>. 309 1.10 mrg </p> 310 1.10 mrg </dd> 311 1.14 mrg <dt><span><code>--program-transform-name=<var>pattern</var></code></span></dt> 312 1.10 mrg <dd><p>Applies the ‘<samp>sed</samp>’ script <var>pattern</var> to be applied to the names 313 1.1 mrg of programs to install in <var>bindir</var> (see above). <var>pattern</var> has to 314 1.10 mrg consist of one or more basic ‘<samp>sed</samp>’ editing commands, separated by 315 1.10 mrg semicolons. For example, if you want the ‘<samp>gcc</samp>’ program name to be 316 1.10 mrg transformed to the installed program <samp>/usr/local/bin/myowngcc</samp> and 317 1.10 mrg the ‘<samp>g++</samp>’ program name to be transformed to 318 1.10 mrg <samp>/usr/local/bin/gspecial++</samp> without changing other program names, 319 1.1 mrg you could use the pattern 320 1.10 mrg <samp>--program-transform-name='s/^gcc$/myowngcc/; s/^g++$/gspecial++/'</samp> 321 1.1 mrg to achieve this effect. 322 1.10 mrg </p> 323 1.10 mrg <p>All three options can be combined and used together, resulting in more 324 1.1 mrg complex conversion patterns. As a basic rule, <var>prefix</var> (and 325 1.1 mrg <var>suffix</var>) are prepended (appended) before further transformations 326 1.1 mrg can happen with a special transformation script <var>pattern</var>. 327 1.10 mrg </p> 328 1.10 mrg <p>As currently implemented, this option only takes effect for native 329 1.10 mrg builds; cross compiler binaries’ names are not transformed even when a 330 1.1 mrg transformation is explicitly asked for by one of these options. 331 1.10 mrg </p> 332 1.10 mrg <p>For native builds, some of the installed programs are also installed 333 1.1 mrg with the target alias in front of their name, as in 334 1.10 mrg ‘<samp>i686-pc-linux-gnu-gcc</samp>’. All of the above transformations happen 335 1.1 mrg before the target alias is prepended to the name—so, specifying 336 1.10 mrg <samp>--program-prefix=foo-</samp> and <samp>program-suffix=-3.1</samp>, the 337 1.1 mrg resulting binary would be installed as 338 1.10 mrg <samp>/usr/local/bin/i686-pc-linux-gnu-foo-gcc-3.1</samp>. 339 1.10 mrg </p> 340 1.10 mrg <p>As a last shortcoming, none of the installed Ada programs are 341 1.1 mrg transformed yet, which will be fixed in some time. 342 1.10 mrg </p> 343 1.10 mrg </dd> 344 1.14 mrg <dt><span><code>--with-local-prefix=<var>dirname</var></code></span></dt> 345 1.10 mrg <dd><p>Specify the 346 1.1 mrg installation directory for local include files. The default is 347 1.10 mrg <samp>/usr/local</samp>. Specify this option if you want the compiler to 348 1.10 mrg search directory <samp><var>dirname</var>/include</samp> for locally installed 349 1.10 mrg header files <em>instead</em> of <samp>/usr/local/include</samp>. 350 1.10 mrg </p> 351 1.10 mrg <p>You should specify <samp>--with-local-prefix</samp> <strong>only</strong> if your 352 1.10 mrg site has a different convention (not <samp>/usr/local</samp>) for where to put 353 1.1 mrg site-specific files. 354 1.10 mrg </p> 355 1.10 mrg <p>The default value for <samp>--with-local-prefix</samp> is <samp>/usr/local</samp> 356 1.10 mrg regardless of the value of <samp>--prefix</samp>. Specifying 357 1.10 mrg <samp>--prefix</samp> has no effect on which directory GCC searches for 358 1.1 mrg local header files. This may seem counterintuitive, but actually it is 359 1.1 mrg logical. 360 1.10 mrg </p> 361 1.10 mrg <p>The purpose of <samp>--prefix</samp> is to specify where to <em>install 362 1.10 mrg GCC</em>. The local header files in <samp>/usr/local/include</samp>—if you put 363 1.1 mrg any in that directory—are not part of GCC. They are part of other 364 1.1 mrg programs—perhaps many others. (GCC installs its own header files in 365 1.10 mrg another directory which is based on the <samp>--prefix</samp> value.) 366 1.10 mrg </p> 367 1.10 mrg <p>Both the local-prefix include directory and the GCC-prefix include 368 1.10 mrg directory are part of GCC’s “system include” directories. Although these 369 1.1 mrg two directories are not fixed, they need to be searched in the proper 370 1.1 mrg order for the correct processing of the include_next directive. The 371 1.1 mrg local-prefix include directory is searched before the GCC-prefix 372 1.1 mrg include directory. Another characteristic of system include directories 373 1.1 mrg is that pedantic warnings are turned off for headers in these directories. 374 1.10 mrg </p> 375 1.10 mrg <p>Some autoconf macros add <samp>-I <var>directory</var></samp> options to the 376 1.1 mrg compiler command line, to ensure that directories containing installed 377 1.10 mrg packages’ headers are searched. When <var>directory</var> is one of GCC’s 378 1.1 mrg system include directories, GCC will ignore the option so that system 379 1.1 mrg directories continue to be processed in the correct order. This 380 1.1 mrg may result in a search order different from what was specified but the 381 1.1 mrg directory will still be searched. 382 1.10 mrg </p> 383 1.10 mrg <p>GCC automatically searches for ordinary libraries using 384 1.10 mrg <code>GCC_EXEC_PREFIX</code>. Thus, when the same installation prefix is 385 1.1 mrg used for both GCC and packages, GCC will automatically search for 386 1.1 mrg both headers and libraries. This provides a configuration that is 387 1.1 mrg easy to use. GCC behaves in a manner similar to that when it is 388 1.10 mrg installed as a system compiler in <samp>/usr</samp>. 389 1.10 mrg </p> 390 1.10 mrg <p>Sites that need to install multiple versions of GCC may not want to 391 1.1 mrg use the above simple configuration. It is possible to use the 392 1.10 mrg <samp>--program-prefix</samp>, <samp>--program-suffix</samp> and 393 1.10 mrg <samp>--program-transform-name</samp> options to install multiple versions 394 1.1 mrg into a single directory, but it may be simpler to use different prefixes 395 1.10 mrg and the <samp>--with-local-prefix</samp> option to specify the location of the 396 1.1 mrg site-specific files for each version. It will then be necessary for 397 1.1 mrg users to specify explicitly the location of local site libraries 398 1.10 mrg (e.g., with <code>LIBRARY_PATH</code>). 399 1.10 mrg </p> 400 1.10 mrg <p>The same value can be used for both <samp>--with-local-prefix</samp> and 401 1.10 mrg <samp>--prefix</samp> provided it is not <samp>/usr</samp>. This can be used 402 1.10 mrg to avoid the default search of <samp>/usr/local/include</samp>. 403 1.10 mrg </p> 404 1.10 mrg <p><strong>Do not</strong> specify <samp>/usr</samp> as the <samp>--with-local-prefix</samp>! 405 1.10 mrg The directory you use for <samp>--with-local-prefix</samp> <strong>must not</strong> 406 1.10 mrg contain any of the system’s standard header files. If it did contain 407 1.1 mrg them, certain programs would be miscompiled (including GNU Emacs, on 408 1.1 mrg certain targets), because this would override and nullify the header 409 1.10 mrg file corrections made by the <code>fixincludes</code> script. 410 1.10 mrg </p> 411 1.10 mrg <p>Indications are that people who use this option use it based on mistaken 412 1.1 mrg ideas of what it is for. People use it as if it specified where to 413 1.1 mrg install part of GCC. Perhaps they make this assumption because 414 1.1 mrg installing GCC creates the directory. 415 1.10 mrg </p> 416 1.10 mrg </dd> 417 1.14 mrg <dt><span><code>--with-gcc-major-version-only</code></span></dt> 418 1.10 mrg <dd><p>Specifies that GCC should use only the major number rather than 419 1.9 mrg <var>major</var>.<var>minor</var>.<var>patchlevel</var> in filesystem paths. 420 1.10 mrg </p> 421 1.10 mrg </dd> 422 1.14 mrg <dt><span><code>--with-native-system-header-dir=<var>dirname</var></code></span></dt> 423 1.10 mrg <dd><p>Specifies that <var>dirname</var> is the directory that contains native system 424 1.10 mrg header files, rather than <samp>/usr/include</samp>. This option is most useful 425 1.3 skrll if you are creating a compiler that should be isolated from the system 426 1.3 skrll as much as possible. It is most commonly used with the 427 1.10 mrg <samp>--with-sysroot</samp> option and will cause GCC to search 428 1.3 skrll <var>dirname</var> inside the system root specified by that option. 429 1.10 mrg </p> 430 1.10 mrg </dd> 431 1.14 mrg <dt><span><code>--enable-shared[=<var>package</var>[,…]]</code></span></dt> 432 1.10 mrg <dd><p>Build shared versions of libraries, if shared libraries are supported on 433 1.1 mrg the target platform. Unlike GCC 2.95.x and earlier, shared libraries 434 1.1 mrg are enabled by default on all platforms that support shared libraries. 435 1.10 mrg </p> 436 1.10 mrg <p>If a list of packages is given as an argument, build shared libraries 437 1.1 mrg only for the listed packages. For other packages, only static libraries 438 1.1 mrg will be built. Package names currently recognized in the GCC tree are 439 1.10 mrg ‘<samp>libgcc</samp>’ (also known as ‘<samp>gcc</samp>’), ‘<samp>libstdc++</samp>’ (not 440 1.10 mrg ‘<samp>libstdc++-v3</samp>’), ‘<samp>libffi</samp>’, ‘<samp>zlib</samp>’, ‘<samp>boehm-gc</samp>’, 441 1.12 mrg ‘<samp>ada</samp>’, ‘<samp>libada</samp>’, ‘<samp>libgo</samp>’, ‘<samp>libobjc</samp>’, and ‘<samp>libphobos</samp>’. 442 1.10 mrg Note ‘<samp>libiberty</samp>’ does not support shared libraries at all. 443 1.10 mrg </p> 444 1.10 mrg <p>Use <samp>--disable-shared</samp> to build only static libraries. Note that 445 1.10 mrg <samp>--disable-shared</samp> does not accept a list of package names as 446 1.10 mrg argument, only <samp>--enable-shared</samp> does. 447 1.10 mrg </p> 448 1.10 mrg <p>Contrast with <samp>--enable-host-shared</samp>, which affects <em>host</em> 449 1.5 mrg code. 450 1.10 mrg </p> 451 1.10 mrg </dd> 452 1.14 mrg <dt><span><code>--enable-host-shared</code></span></dt> 453 1.10 mrg <dd><p>Specify that the <em>host</em> code should be built into position-independent 454 1.5 mrg machine code (with -fPIC), allowing it to be used within shared libraries, 455 1.5 mrg but yielding a slightly slower compiler. 456 1.10 mrg </p> 457 1.10 mrg <p>This option is required when building the libgccjit.so library. 458 1.10 mrg </p> 459 1.10 mrg <p>Contrast with <samp>--enable-shared</samp>, which affects <em>target</em> 460 1.5 mrg libraries. 461 1.10 mrg </p> 462 1.10 mrg </dd> 463 1.14 mrg <dt><span><code><span id="with-gnu-as"></span>--with-gnu-as</code></span></dt> 464 1.10 mrg <dd><p>Specify that the compiler should assume that the 465 1.1 mrg assembler it finds is the GNU assembler. However, this does not modify 466 1.1 mrg the rules to find an assembler and will result in confusion if the 467 1.1 mrg assembler found is not actually the GNU assembler. (Confusion may also 468 1.1 mrg result if the compiler finds the GNU assembler but has not been 469 1.10 mrg configured with <samp>--with-gnu-as</samp>.) If you have more than one 470 1.1 mrg assembler installed on your system, you may want to use this option in 471 1.10 mrg connection with <samp>--with-as=<var>pathname</var></samp> or 472 1.10 mrg <samp>--with-build-time-tools=<var>pathname</var></samp>. 473 1.10 mrg </p> 474 1.10 mrg <p>The following systems are the only ones where it makes a difference 475 1.1 mrg whether you use the GNU assembler. On any other system, 476 1.10 mrg <samp>--with-gnu-as</samp> has no effect. 477 1.10 mrg </p> 478 1.10 mrg <ul> 479 1.10 mrg <li> ‘<samp>hppa1.0-<var>any</var>-<var>any</var></samp>’ 480 1.10 mrg </li><li> ‘<samp>hppa1.1-<var>any</var>-<var>any</var></samp>’ 481 1.10 mrg </li><li> ‘<samp>sparc-sun-solaris2.<var>any</var></samp>’ 482 1.10 mrg </li><li> ‘<samp>sparc64-<var>any</var>-solaris2.<var>any</var></samp>’ 483 1.10 mrg </li></ul> 484 1.10 mrg 485 1.10 mrg </dd> 486 1.14 mrg <dt><span><code><span id="with-as"></span>--with-as=<var>pathname</var></code></span></dt> 487 1.10 mrg <dd><p>Specify that the compiler should use the assembler pointed to by 488 1.1 mrg <var>pathname</var>, rather than the one found by the standard rules to find 489 1.1 mrg an assembler, which are: 490 1.10 mrg </p><ul> 491 1.10 mrg <li> Unless GCC is being built with a cross compiler, check the 492 1.10 mrg <samp><var>libexec</var>/gcc/<var>target</var>/<var>version</var></samp> directory. 493 1.10 mrg <var>libexec</var> defaults to <samp><var>exec-prefix</var>/libexec</samp>; 494 1.1 mrg <var>exec-prefix</var> defaults to <var>prefix</var>, which 495 1.10 mrg defaults to <samp>/usr/local</samp> unless overridden by the 496 1.10 mrg <samp>--prefix=<var>pathname</var></samp> switch described above. <var>target</var> 497 1.10 mrg is the target system triple, such as ‘<samp>sparc-sun-solaris2.7</samp>’, and 498 1.1 mrg <var>version</var> denotes the GCC version, such as 3.0. 499 1.1 mrg 500 1.10 mrg </li><li> If the target system is the same that you are building on, check 501 1.10 mrg operating system specific directories (e.g. <samp>/usr/ccs/bin</samp> on 502 1.13 mrg Solaris 2). 503 1.1 mrg 504 1.10 mrg </li><li> Check in the <code>PATH</code> for a tool whose name is prefixed by the 505 1.1 mrg target system triple. 506 1.1 mrg 507 1.10 mrg </li><li> Check in the <code>PATH</code> for a tool whose name is not prefixed by the 508 1.1 mrg target system triple, if the host and target system triple are 509 1.1 mrg the same (in other words, we use a host tool if it can be used for 510 1.10 mrg the target as well). 511 1.10 mrg </li></ul> 512 1.1 mrg 513 1.10 mrg <p>You may want to use <samp>--with-as</samp> if no assembler 514 1.1 mrg is installed in the directories listed above, or if you have multiple 515 1.1 mrg assemblers installed and want to choose one that is not found by the 516 1.1 mrg above rules. 517 1.10 mrg </p> 518 1.10 mrg </dd> 519 1.14 mrg <dt><span><code><span id="with-gnu-ld"></span>--with-gnu-ld</code></span></dt> 520 1.10 mrg <dd><p>Same as <a href="#with-gnu-as"><samp>--with-gnu-as</samp></a> 521 1.1 mrg but for the linker. 522 1.10 mrg </p> 523 1.10 mrg </dd> 524 1.14 mrg <dt><span><code>--with-ld=<var>pathname</var></code></span></dt> 525 1.10 mrg <dd><p>Same as <a href="#with-as"><samp>--with-as</samp></a> 526 1.1 mrg but for the linker. 527 1.10 mrg </p> 528 1.10 mrg </dd> 529 1.14 mrg <dt><span><code>--with-dsymutil=<var>pathname</var></code></span></dt> 530 1.14 mrg <dd><p>Same as <a href="#with-as"><samp>--with-as</samp></a> 531 1.14 mrg but for the debug linker (only used on Darwin platforms so far). 532 1.14 mrg </p> 533 1.14 mrg </dd> 534 1.14 mrg <dt><span><code>--with-stabs</code></span></dt> 535 1.10 mrg <dd><p>Specify that stabs debugging 536 1.1 mrg information should be used instead of whatever format the host normally 537 1.1 mrg uses. Normally GCC uses the same debug format as the host system. 538 1.10 mrg </p> 539 1.10 mrg </dd> 540 1.14 mrg <dt><span><code>--with-tls=<var>dialect</var></code></span></dt> 541 1.10 mrg <dd><p>Specify the default TLS dialect, for systems were there is a choice. 542 1.3 skrll For ARM targets, possible values for <var>dialect</var> are <code>gnu</code> or 543 1.3 skrll <code>gnu2</code>, which select between the original GNU dialect and the GNU TLS 544 1.3 skrll descriptor-based dialect. 545 1.10 mrg </p> 546 1.10 mrg </dd> 547 1.14 mrg <dt><span><code>--enable-multiarch</code></span></dt> 548 1.10 mrg <dd><p>Specify whether to enable or disable multiarch support. The default is 549 1.3 skrll to check for glibc start files in a multiarch location, and enable it 550 1.3 skrll if the files are found. The auto detection is enabled for native builds, 551 1.10 mrg and for cross builds configured with <samp>--with-sysroot</samp>, and without 552 1.10 mrg <samp>--with-native-system-header-dir</samp>. 553 1.3 skrll More documentation about multiarch can be found at 554 1.7 mrg <a href="https://wiki.debian.org/Multiarch">https://wiki.debian.org/Multiarch</a>. 555 1.10 mrg </p> 556 1.10 mrg </dd> 557 1.14 mrg <dt><span><code>--enable-sjlj-exceptions</code></span></dt> 558 1.10 mrg <dd><p>Force use of the <code>setjmp</code>/<code>longjmp</code>-based scheme for exceptions. 559 1.10 mrg ‘<samp>configure</samp>’ ordinarily picks the correct value based on the platform. 560 1.6 mrg Only use this option if you are sure you need a different setting. 561 1.10 mrg </p> 562 1.10 mrg </dd> 563 1.14 mrg <dt><span><code>--enable-vtable-verify</code></span></dt> 564 1.10 mrg <dd><p>Specify whether to enable or disable the vtable verification feature. 565 1.5 mrg Enabling this feature causes libstdc++ to be built with its virtual calls 566 1.5 mrg in verifiable mode. This means that, when linked with libvtv, every 567 1.5 mrg virtual call in libstdc++ will verify the vtable pointer through which the 568 1.5 mrg call will be made before actually making the call. If not linked with libvtv, 569 1.10 mrg the verifier will call stub functions (in libstdc++ itself) and do nothing. 570 1.5 mrg If vtable verification is disabled, then libstdc++ is not built with its 571 1.5 mrg virtual calls in verifiable mode at all. However the libvtv library will 572 1.10 mrg still be built (see <samp>--disable-libvtv</samp> to turn off building libvtv). 573 1.10 mrg <samp>--disable-vtable-verify</samp> is the default. 574 1.10 mrg </p> 575 1.10 mrg </dd> 576 1.14 mrg <dt><span><code>--disable-gcov</code></span></dt> 577 1.12 mrg <dd><p>Specify that the run-time library used for coverage analysis 578 1.12 mrg and associated host tools should not be built. 579 1.12 mrg </p> 580 1.12 mrg </dd> 581 1.14 mrg <dt><span><code>--disable-multilib</code></span></dt> 582 1.10 mrg <dd><p>Specify that multiple target 583 1.1 mrg libraries to support different target variants, calling 584 1.1 mrg conventions, etc. should not be built. The default is to build a 585 1.1 mrg predefined set of them. 586 1.10 mrg </p> 587 1.10 mrg <p>Some targets provide finer-grained control over which multilibs are built 588 1.10 mrg (e.g., <samp>--disable-softfloat</samp>): 589 1.10 mrg </p><dl compact="compact"> 590 1.14 mrg <dt><span><code>arm-*-*</code></span></dt> 591 1.10 mrg <dd><p>fpu, 26bit, underscore, interwork, biendian, nofmult. 592 1.10 mrg </p> 593 1.10 mrg </dd> 594 1.14 mrg <dt><span><code>m68*-*-*</code></span></dt> 595 1.10 mrg <dd><p>softfloat, m68881, m68000, m68020. 596 1.10 mrg </p> 597 1.10 mrg </dd> 598 1.14 mrg <dt><span><code>mips*-*-*</code></span></dt> 599 1.10 mrg <dd><p>single-float, biendian, softfloat. 600 1.10 mrg </p> 601 1.10 mrg </dd> 602 1.14 mrg <dt><span><code>msp430-*-*</code></span></dt> 603 1.13 mrg <dd><p>no-exceptions 604 1.13 mrg </p> 605 1.13 mrg </dd> 606 1.14 mrg <dt><span><code>powerpc*-*-*, rs6000*-*-*</code></span></dt> 607 1.10 mrg <dd><p>aix64, pthread, softfloat, powercpu, powerpccpu, powerpcos, biendian, 608 1.1 mrg sysv, aix. 609 1.10 mrg </p> 610 1.10 mrg </dd> 611 1.10 mrg </dl> 612 1.1 mrg 613 1.10 mrg </dd> 614 1.14 mrg <dt><span><code>--with-multilib-list=<var>list</var></code></span></dt> 615 1.14 mrg <dt><span><code>--without-multilib-list</code></span></dt> 616 1.10 mrg <dd><p>Specify what multilibs to build. <var>list</var> is a comma separated list of 617 1.9 mrg values, possibly consisting of a single value. Currently only implemented 618 1.12 mrg for aarch64*-*-*, arm*-*-*, riscv*-*-*, sh*-*-* and x86-64-*-linux*. The 619 1.12 mrg accepted values and meaning for each target is given below. 620 1.10 mrg </p> 621 1.10 mrg <dl compact="compact"> 622 1.14 mrg <dt><span><code>aarch64*-*-*</code></span></dt> 623 1.10 mrg <dd><p><var>list</var> is a comma separated list of <code>ilp32</code>, and <code>lp64</code> 624 1.10 mrg to enable ILP32 and LP64 run-time libraries, respectively. If 625 1.10 mrg <var>list</var> is empty, then there will be no multilibs and only the 626 1.10 mrg default run-time library will be built. If <var>list</var> is 627 1.10 mrg <code>default</code> or –with-multilib-list= is not specified, then the 628 1.10 mrg default set of libraries is selected based on the value of 629 1.10 mrg <samp>--target</samp>. 630 1.10 mrg </p> 631 1.10 mrg </dd> 632 1.14 mrg <dt><span><code>arm*-*-*</code></span></dt> 633 1.12 mrg <dd><p><var>list</var> is a comma separated list of <code>aprofile</code> and 634 1.12 mrg <code>rmprofile</code> to build multilibs for A or R and M architecture 635 1.12 mrg profiles respectively. Note that, due to some limitation of the current 636 1.12 mrg multilib framework, using the combined <code>aprofile,rmprofile</code> 637 1.12 mrg multilibs selects in some cases a less optimal multilib than when using 638 1.12 mrg the multilib profile for the architecture targetted. The special value 639 1.12 mrg <code>default</code> is also accepted and is equivalent to omitting the 640 1.12 mrg option, i.e., only the default run-time library will be enabled. 641 1.12 mrg </p> 642 1.12 mrg <p><var>list</var> may instead contain <code>@name</code>, to use the multilib 643 1.12 mrg configuration Makefile fragment <samp>name</samp> in <samp>gcc/config/arm</samp> in 644 1.12 mrg the source tree (it is part of the corresponding sources, after all). 645 1.12 mrg It is recommended, but not required, that files used for this purpose to 646 1.12 mrg be named starting with <samp>t-ml-</samp>, to make their intended purpose 647 1.12 mrg self-evident, in line with GCC conventions. Such files enable custom, 648 1.12 mrg user-chosen multilib lists to be configured. Whether multiple such 649 1.12 mrg files can be used together depends on the contents of the supplied 650 1.12 mrg files. See <samp>gcc/config/arm/t-multilib</samp> and its supplementary 651 1.12 mrg <samp>gcc/config/arm/t-*profile</samp> files for an example of what such 652 1.12 mrg Makefile fragments might look like for this version of GCC. The macros 653 1.12 mrg expected to be defined in these fragments are not stable across GCC 654 1.12 mrg releases, so make sure they define the <code>MULTILIB</code>-related macros 655 1.12 mrg expected by the version of GCC you are building. 656 1.12 mrg See “Target Makefile Fragments” in the internals manual. 657 1.10 mrg </p> 658 1.10 mrg <p>The table below gives the combination of ISAs, architectures, FPUs and 659 1.12 mrg floating-point ABIs for which multilibs are built for each predefined 660 1.12 mrg profile. The union of these options is considered when specifying both 661 1.12 mrg <code>aprofile</code> and <code>rmprofile</code>. 662 1.10 mrg </p> 663 1.10 mrg <table> 664 1.10 mrg <tr><td width="15%">Option</td><td width="28%">aprofile</td><td width="30%">rmprofile</td></tr> 665 1.10 mrg <tr><td width="15%">ISAs</td><td width="28%"><code>-marm</code> and <code>-mthumb</code></td><td width="30%"><code>-mthumb</code></td></tr> 666 1.10 mrg <tr><td width="15%">Architectures<br><br><br><br><br><br></td><td width="28%">default architecture<br> 667 1.9 mrg <code>-march=armv7-a</code><br> 668 1.9 mrg <code>-march=armv7ve</code><br> 669 1.10 mrg <code>-march=armv8-a</code><br><br><br></td><td width="30%">default architecture<br> 670 1.9 mrg <code>-march=armv6s-m</code><br> 671 1.9 mrg <code>-march=armv7-m</code><br> 672 1.9 mrg <code>-march=armv7e-m</code><br> 673 1.9 mrg <code>-march=armv8-m.base</code><br> 674 1.9 mrg <code>-march=armv8-m.main</code><br> 675 1.10 mrg <code>-march=armv7</code></td></tr> 676 1.10 mrg <tr><td width="15%">FPUs<br><br><br><br><br></td><td width="28%">none<br> 677 1.9 mrg <code>-mfpu=vfpv3-d16</code><br> 678 1.9 mrg <code>-mfpu=neon</code><br> 679 1.9 mrg <code>-mfpu=vfpv4-d16</code><br> 680 1.9 mrg <code>-mfpu=neon-vfpv4</code><br> 681 1.10 mrg <code>-mfpu=neon-fp-armv8</code></td><td width="30%">none<br> 682 1.9 mrg <code>-mfpu=vfpv3-d16</code><br> 683 1.9 mrg <code>-mfpu=fpv4-sp-d16</code><br> 684 1.9 mrg <code>-mfpu=fpv5-sp-d16</code><br> 685 1.10 mrg <code>-mfpu=fpv5-d16</code><br></td></tr> 686 1.10 mrg <tr><td width="15%">floating-point ABIs<br><br></td><td width="28%"><code>-mfloat-abi=soft</code><br> 687 1.9 mrg <code>-mfloat-abi=softfp</code><br> 688 1.10 mrg <code>-mfloat-abi=hard</code></td><td width="30%"><code>-mfloat-abi=soft</code><br> 689 1.9 mrg <code>-mfloat-abi=softfp</code><br> 690 1.10 mrg <code>-mfloat-abi=hard</code></td></tr> 691 1.10 mrg </table> 692 1.9 mrg 693 1.10 mrg </dd> 694 1.14 mrg <dt><span><code>riscv*-*-*</code></span></dt> 695 1.12 mrg <dd><p><var>list</var> is a single ABI name. The target architecture must be either 696 1.12 mrg <code>rv32gc</code> or <code>rv64gc</code>. This will build a single multilib for the 697 1.12 mrg specified architecture and ABI pair. If <code>--with-multilib-list</code> is not 698 1.12 mrg given, then a default set of multilibs is selected based on the value of 699 1.12 mrg <samp>--target</samp>. This is usually a large set of multilibs. 700 1.12 mrg </p> 701 1.12 mrg </dd> 702 1.14 mrg <dt><span><code>sh*-*-*</code></span></dt> 703 1.10 mrg <dd><p><var>list</var> is a comma separated list of CPU names. These must be of the 704 1.1 mrg form <code>sh*</code> or <code>m*</code> (in which case they match the compiler option 705 1.1 mrg for that processor). The list should not contain any endian options - 706 1.10 mrg these are handled by <samp>--with-endian</samp>. 707 1.10 mrg </p> 708 1.10 mrg <p>If <var>list</var> is empty, then there will be no multilibs for extra 709 1.1 mrg processors. The multilib for the secondary endian remains enabled. 710 1.10 mrg </p> 711 1.10 mrg <p>As a special case, if an entry in the list starts with a <code>!</code> 712 1.10 mrg (exclamation point), then it is added to the list of excluded multilibs. 713 1.10 mrg Entries of this sort should be compatible with ‘<samp>MULTILIB_EXCLUDES</samp>’ 714 1.1 mrg (once the leading <code>!</code> has been stripped). 715 1.10 mrg </p> 716 1.10 mrg <p>If <samp>--with-multilib-list</samp> is not given, then a default set of 717 1.10 mrg multilibs is selected based on the value of <samp>--target</samp>. This is 718 1.1 mrg usually the complete set of libraries, but some targets imply a more 719 1.1 mrg specialized subset. 720 1.10 mrg </p> 721 1.10 mrg <p>Example 1: to configure a compiler for SH4A only, but supporting both 722 1.10 mrg endians, with little endian being the default: 723 1.14 mrg </p><div class="example"> 724 1.14 mrg <pre class="example">--with-cpu=sh4a --with-endian=little,big --with-multilib-list= 725 1.10 mrg </pre></div> 726 1.9 mrg 727 1.10 mrg <p>Example 2: to configure a compiler for both SH4A and SH4AL-DSP, but with 728 1.1 mrg only little endian SH4AL: 729 1.14 mrg </p><div class="example"> 730 1.14 mrg <pre class="example">--with-cpu=sh4a --with-endian=little,big \ 731 1.10 mrg --with-multilib-list=sh4al,!mb/m4al 732 1.10 mrg </pre></div> 733 1.10 mrg 734 1.10 mrg </dd> 735 1.14 mrg <dt><span><code>x86-64-*-linux*</code></span></dt> 736 1.10 mrg <dd><p><var>list</var> is a comma separated list of <code>m32</code>, <code>m64</code> and 737 1.3 skrll <code>mx32</code> to enable 32-bit, 64-bit and x32 run-time libraries, 738 1.3 skrll respectively. If <var>list</var> is empty, then there will be no multilibs 739 1.3 skrll and only the default run-time library will be enabled. 740 1.10 mrg </p> 741 1.10 mrg <p>If <samp>--with-multilib-list</samp> is not given, then only 32-bit and 742 1.10 mrg 64-bit run-time libraries will be enabled. 743 1.10 mrg </p></dd> 744 1.3 skrll </dl> 745 1.3 skrll 746 1.10 mrg </dd> 747 1.14 mrg <dt><span><code>--with-endian=<var>endians</var></code></span></dt> 748 1.10 mrg <dd><p>Specify what endians to use. 749 1.1 mrg Currently only implemented for sh*-*-*. 750 1.10 mrg </p> 751 1.10 mrg <p><var>endians</var> may be one of the following: 752 1.10 mrg </p><dl compact="compact"> 753 1.14 mrg <dt><span><code>big</code></span></dt> 754 1.10 mrg <dd><p>Use big endian exclusively. 755 1.10 mrg </p></dd> 756 1.14 mrg <dt><span><code>little</code></span></dt> 757 1.10 mrg <dd><p>Use little endian exclusively. 758 1.10 mrg </p></dd> 759 1.14 mrg <dt><span><code>big,little</code></span></dt> 760 1.10 mrg <dd><p>Use big endian by default. Provide a multilib for little endian. 761 1.10 mrg </p></dd> 762 1.14 mrg <dt><span><code>little,big</code></span></dt> 763 1.10 mrg <dd><p>Use little endian by default. Provide a multilib for big endian. 764 1.10 mrg </p></dd> 765 1.1 mrg </dl> 766 1.1 mrg 767 1.10 mrg </dd> 768 1.14 mrg <dt><span><code>--enable-threads</code></span></dt> 769 1.10 mrg <dd><p>Specify that the target 770 1.1 mrg supports threads. This affects the Objective-C compiler and runtime 771 1.10 mrg library, and exception handling for other languages like C++. 772 1.1 mrg On some systems, this is the default. 773 1.10 mrg </p> 774 1.10 mrg <p>In general, the best (and, in many cases, the only known) threading 775 1.1 mrg model available will be configured for use. Beware that on some 776 1.1 mrg systems, GCC has not been taught what threading models are generally 777 1.10 mrg available for the system. In this case, <samp>--enable-threads</samp> is an 778 1.10 mrg alias for <samp>--enable-threads=single</samp>. 779 1.10 mrg </p> 780 1.10 mrg </dd> 781 1.14 mrg <dt><span><code>--disable-threads</code></span></dt> 782 1.10 mrg <dd><p>Specify that threading support should be disabled for the system. 783 1.10 mrg This is an alias for <samp>--enable-threads=single</samp>. 784 1.10 mrg </p> 785 1.10 mrg </dd> 786 1.14 mrg <dt><span><code>--enable-threads=<var>lib</var></code></span></dt> 787 1.10 mrg <dd><p>Specify that 788 1.1 mrg <var>lib</var> is the thread support library. This affects the Objective-C 789 1.1 mrg compiler and runtime library, and exception handling for other languages 790 1.9 mrg like C++. The possibilities for <var>lib</var> are: 791 1.10 mrg </p> 792 1.10 mrg <dl compact="compact"> 793 1.14 mrg <dt><span><code>aix</code></span></dt> 794 1.10 mrg <dd><p>AIX thread support. 795 1.10 mrg </p></dd> 796 1.14 mrg <dt><span><code>dce</code></span></dt> 797 1.10 mrg <dd><p>DCE thread support. 798 1.10 mrg </p></dd> 799 1.14 mrg <dt><span><code>lynx</code></span></dt> 800 1.10 mrg <dd><p>LynxOS thread support. 801 1.10 mrg </p></dd> 802 1.14 mrg <dt><span><code>mipssde</code></span></dt> 803 1.10 mrg <dd><p>MIPS SDE thread support. 804 1.10 mrg </p></dd> 805 1.14 mrg <dt><span><code>no</code></span></dt> 806 1.10 mrg <dd><p>This is an alias for ‘<samp>single</samp>’. 807 1.10 mrg </p></dd> 808 1.14 mrg <dt><span><code>posix</code></span></dt> 809 1.10 mrg <dd><p>Generic POSIX/Unix98 thread support. 810 1.10 mrg </p></dd> 811 1.14 mrg <dt><span><code>rtems</code></span></dt> 812 1.10 mrg <dd><p>RTEMS thread support. 813 1.10 mrg </p></dd> 814 1.14 mrg <dt><span><code>single</code></span></dt> 815 1.10 mrg <dd><p>Disable thread support, should work for all platforms. 816 1.10 mrg </p></dd> 817 1.14 mrg <dt><span><code>tpf</code></span></dt> 818 1.10 mrg <dd><p>TPF thread support. 819 1.10 mrg </p></dd> 820 1.14 mrg <dt><span><code>vxworks</code></span></dt> 821 1.10 mrg <dd><p>VxWorks thread support. 822 1.10 mrg </p></dd> 823 1.14 mrg <dt><span><code>win32</code></span></dt> 824 1.10 mrg <dd><p>Microsoft Win32 API thread support. 825 1.10 mrg </p></dd> 826 1.1 mrg </dl> 827 1.1 mrg 828 1.10 mrg </dd> 829 1.14 mrg <dt><span><code>--enable-tls</code></span></dt> 830 1.10 mrg <dd><p>Specify that the target supports TLS (Thread Local Storage). Usually 831 1.1 mrg configure can correctly determine if TLS is supported. In cases where 832 1.1 mrg it guesses incorrectly, TLS can be explicitly enabled or disabled with 833 1.10 mrg <samp>--enable-tls</samp> or <samp>--disable-tls</samp>. This can happen if 834 1.1 mrg the assembler supports TLS but the C library does not, or if the 835 1.1 mrg assumptions made by the configure test are incorrect. 836 1.10 mrg </p> 837 1.10 mrg </dd> 838 1.14 mrg <dt><span><code>--disable-tls</code></span></dt> 839 1.10 mrg <dd><p>Specify that the target does not support TLS. 840 1.10 mrg This is an alias for <samp>--enable-tls=no</samp>. 841 1.10 mrg </p> 842 1.10 mrg </dd> 843 1.14 mrg <dt><span><code>--disable-tm-clone-registry</code></span></dt> 844 1.13 mrg <dd><p>Disable TM clone registry in libgcc. It is enabled in libgcc by default. 845 1.13 mrg This option helps to reduce code size for embedded targets which do 846 1.13 mrg not use transactional memory. 847 1.13 mrg </p> 848 1.13 mrg </dd> 849 1.14 mrg <dt><span><code>--with-cpu=<var>cpu</var></code></span></dt> 850 1.14 mrg <dt><span><code>--with-cpu-32=<var>cpu</var></code></span></dt> 851 1.14 mrg <dt><span><code>--with-cpu-64=<var>cpu</var></code></span></dt> 852 1.10 mrg <dd><p>Specify which cpu variant the compiler should generate code for by default. 853 1.10 mrg <var>cpu</var> will be used as the default value of the <samp>-mcpu=</samp> switch. 854 1.5 mrg This option is only supported on some targets, including ARC, ARM, i386, M68k, 855 1.10 mrg PowerPC, and SPARC. It is mandatory for ARC. The <samp>--with-cpu-32</samp> and 856 1.10 mrg <samp>--with-cpu-64</samp> options specify separate default CPUs for 857 1.13 mrg 32-bit and 64-bit modes; these options are only supported for aarch64, i386, 858 1.7 mrg x86-64, PowerPC, and SPARC. 859 1.10 mrg </p> 860 1.10 mrg </dd> 861 1.14 mrg <dt><span><code>--with-schedule=<var>cpu</var></code></span></dt> 862 1.14 mrg <dt><span><code>--with-arch=<var>cpu</var></code></span></dt> 863 1.14 mrg <dt><span><code>--with-arch-32=<var>cpu</var></code></span></dt> 864 1.14 mrg <dt><span><code>--with-arch-64=<var>cpu</var></code></span></dt> 865 1.14 mrg <dt><span><code>--with-tune=<var>cpu</var></code></span></dt> 866 1.14 mrg <dt><span><code>--with-tune-32=<var>cpu</var></code></span></dt> 867 1.14 mrg <dt><span><code>--with-tune-64=<var>cpu</var></code></span></dt> 868 1.14 mrg <dt><span><code>--with-abi=<var>abi</var></code></span></dt> 869 1.14 mrg <dt><span><code>--with-fpu=<var>type</var></code></span></dt> 870 1.14 mrg <dt><span><code>--with-float=<var>type</var></code></span></dt> 871 1.10 mrg <dd><p>These configure options provide default values for the <samp>-mschedule=</samp>, 872 1.10 mrg <samp>-march=</samp>, <samp>-mtune=</samp>, <samp>-mabi=</samp>, and <samp>-mfpu=</samp> 873 1.10 mrg options and for <samp>-mhard-float</samp> or <samp>-msoft-float</samp>. As with 874 1.10 mrg <samp>--with-cpu</samp>, which switches will be accepted and acceptable values 875 1.1 mrg of the arguments depend on the target. 876 1.10 mrg </p> 877 1.10 mrg </dd> 878 1.14 mrg <dt><span><code>--with-mode=<var>mode</var></code></span></dt> 879 1.10 mrg <dd><p>Specify if the compiler should default to <samp>-marm</samp> or <samp>-mthumb</samp>. 880 1.1 mrg This option is only supported on ARM targets. 881 1.10 mrg </p> 882 1.10 mrg </dd> 883 1.14 mrg <dt><span><code>--with-stack-offset=<var>num</var></code></span></dt> 884 1.10 mrg <dd><p>This option sets the default for the -mstack-offset=<var>num</var> option, 885 1.3 skrll and will thus generally also control the setting of this option for 886 1.3 skrll libraries. This option is only supported on Epiphany targets. 887 1.10 mrg </p> 888 1.10 mrg </dd> 889 1.14 mrg <dt><span><code>--with-fpmath=<var>isa</var></code></span></dt> 890 1.10 mrg <dd><p>This options sets <samp>-mfpmath=sse</samp> by default and specifies the default 891 1.10 mrg ISA for floating-point arithmetics. You can select either ‘<samp>sse</samp>’ which 892 1.10 mrg enables <samp>-msse2</samp> or ‘<samp>avx</samp>’ which enables <samp>-mavx</samp> by default. 893 1.3 skrll This option is only supported on i386 and x86-64 targets. 894 1.10 mrg </p> 895 1.10 mrg </dd> 896 1.14 mrg <dt><span><code>--with-fp-32=<var>mode</var></code></span></dt> 897 1.10 mrg <dd><p>On MIPS targets, set the default value for the <samp>-mfp</samp> option when using 898 1.5 mrg the o32 ABI. The possibilities for <var>mode</var> are: 899 1.10 mrg </p><dl compact="compact"> 900 1.14 mrg <dt><span><code>32</code></span></dt> 901 1.10 mrg <dd><p>Use the o32 FP32 ABI extension, as with the <samp>-mfp32</samp> command-line 902 1.10 mrg option. 903 1.10 mrg </p></dd> 904 1.14 mrg <dt><span><code>xx</code></span></dt> 905 1.10 mrg <dd><p>Use the o32 FPXX ABI extension, as with the <samp>-mfpxx</samp> command-line 906 1.10 mrg option. 907 1.10 mrg </p></dd> 908 1.14 mrg <dt><span><code>64</code></span></dt> 909 1.10 mrg <dd><p>Use the o32 FP64 ABI extension, as with the <samp>-mfp64</samp> command-line 910 1.10 mrg option. 911 1.10 mrg </p></dd> 912 1.5 mrg </dl> 913 1.10 mrg <p>In the absence of this configuration option the default is to use the o32 914 1.5 mrg FP32 ABI extension. 915 1.10 mrg </p> 916 1.10 mrg </dd> 917 1.14 mrg <dt><span><code>--with-odd-spreg-32</code></span></dt> 918 1.10 mrg <dd><p>On MIPS targets, set the <samp>-modd-spreg</samp> option by default when using 919 1.5 mrg the o32 ABI. 920 1.10 mrg </p> 921 1.10 mrg </dd> 922 1.14 mrg <dt><span><code>--without-odd-spreg-32</code></span></dt> 923 1.10 mrg <dd><p>On MIPS targets, set the <samp>-mno-odd-spreg</samp> option by default when using 924 1.5 mrg the o32 ABI. This is normally used in conjunction with 925 1.10 mrg <samp>--with-fp-32=64</samp> in order to target the o32 FP64A ABI extension. 926 1.10 mrg </p> 927 1.10 mrg </dd> 928 1.14 mrg <dt><span><code>--with-nan=<var>encoding</var></code></span></dt> 929 1.10 mrg <dd><p>On MIPS targets, set the default encoding convention to use for the 930 1.5 mrg special not-a-number (NaN) IEEE 754 floating-point data. The 931 1.5 mrg possibilities for <var>encoding</var> are: 932 1.10 mrg </p><dl compact="compact"> 933 1.14 mrg <dt><span><code>legacy</code></span></dt> 934 1.10 mrg <dd><p>Use the legacy encoding, as with the <samp>-mnan=legacy</samp> command-line 935 1.10 mrg option. 936 1.10 mrg </p></dd> 937 1.14 mrg <dt><span><code>2008</code></span></dt> 938 1.10 mrg <dd><p>Use the 754-2008 encoding, as with the <samp>-mnan=2008</samp> command-line 939 1.10 mrg option. 940 1.10 mrg </p></dd> 941 1.5 mrg </dl> 942 1.10 mrg <p>To use this configuration option you must have an assembler version 943 1.10 mrg installed that supports the <samp>-mnan=</samp> command-line option too. 944 1.5 mrg In the absence of this configuration option the default convention is 945 1.10 mrg the legacy encoding, as when neither of the <samp>-mnan=2008</samp> and 946 1.10 mrg <samp>-mnan=legacy</samp> command-line options has been used. 947 1.10 mrg </p> 948 1.10 mrg </dd> 949 1.14 mrg <dt><span><code>--with-divide=<var>type</var></code></span></dt> 950 1.10 mrg <dd><p>Specify how the compiler should generate code for checking for 951 1.10 mrg division by zero. This option is only supported on the MIPS target. 952 1.1 mrg The possibilities for <var>type</var> are: 953 1.10 mrg </p><dl compact="compact"> 954 1.14 mrg <dt><span><code>traps</code></span></dt> 955 1.10 mrg <dd><p>Division by zero checks use conditional traps (this is the default on 956 1.10 mrg systems that support conditional traps). 957 1.10 mrg </p></dd> 958 1.14 mrg <dt><span><code>breaks</code></span></dt> 959 1.10 mrg <dd><p>Division by zero checks use the break instruction. 960 1.10 mrg </p></dd> 961 1.1 mrg </dl> 962 1.1 mrg 963 1.10 mrg 964 1.10 mrg </dd> 965 1.14 mrg <dt><span><code>--with-llsc</code></span></dt> 966 1.10 mrg <dd><p>On MIPS targets, make <samp>-mllsc</samp> the default when no 967 1.10 mrg <samp>-mno-llsc</samp> option is passed. This is the default for 968 1.1 mrg Linux-based targets, as the kernel will emulate them if the ISA does 969 1.1 mrg not provide them. 970 1.10 mrg </p> 971 1.10 mrg </dd> 972 1.14 mrg <dt><span><code>--without-llsc</code></span></dt> 973 1.10 mrg <dd><p>On MIPS targets, make <samp>-mno-llsc</samp> the default when no 974 1.10 mrg <samp>-mllsc</samp> option is passed. 975 1.10 mrg </p> 976 1.10 mrg </dd> 977 1.14 mrg <dt><span><code>--with-synci</code></span></dt> 978 1.10 mrg <dd><p>On MIPS targets, make <samp>-msynci</samp> the default when no 979 1.10 mrg <samp>-mno-synci</samp> option is passed. 980 1.10 mrg </p> 981 1.10 mrg </dd> 982 1.14 mrg <dt><span><code>--without-synci</code></span></dt> 983 1.10 mrg <dd><p>On MIPS targets, make <samp>-mno-synci</samp> the default when no 984 1.10 mrg <samp>-msynci</samp> option is passed. This is the default. 985 1.10 mrg </p> 986 1.10 mrg </dd> 987 1.14 mrg <dt><span><code>--with-lxc1-sxc1</code></span></dt> 988 1.10 mrg <dd><p>On MIPS targets, make <samp>-mlxc1-sxc1</samp> the default when no 989 1.10 mrg <samp>-mno-lxc1-sxc1</samp> option is passed. This is the default. 990 1.10 mrg </p> 991 1.10 mrg </dd> 992 1.14 mrg <dt><span><code>--without-lxc1-sxc1</code></span></dt> 993 1.10 mrg <dd><p>On MIPS targets, make <samp>-mno-lxc1-sxc1</samp> the default when no 994 1.10 mrg <samp>-mlxc1-sxc1</samp> option is passed. The indexed load/store 995 1.9 mrg instructions are not directly a problem but can lead to unexpected 996 1.9 mrg behaviour when deployed in an application intended for a 32-bit address 997 1.9 mrg space but run on a 64-bit processor. The issue is seen because all 998 1.9 mrg known MIPS 64-bit Linux kernels execute o32 and n32 applications 999 1.9 mrg with 64-bit addressing enabled which affects the overflow behaviour 1000 1.9 mrg of the indexed addressing mode. GCC will assume that ordinary 1001 1.9 mrg 32-bit arithmetic overflow behaviour is the same whether performed 1002 1.9 mrg as an <code>addu</code> instruction or as part of the address calculation 1003 1.9 mrg in <code>lwxc1</code> type instructions. This assumption holds true in a 1004 1.9 mrg pure 32-bit environment and can hold true in a 64-bit environment if 1005 1.9 mrg the address space is accurately set to be 32-bit for o32 and n32. 1006 1.10 mrg </p> 1007 1.10 mrg </dd> 1008 1.14 mrg <dt><span><code>--with-madd4</code></span></dt> 1009 1.10 mrg <dd><p>On MIPS targets, make <samp>-mmadd4</samp> the default when no 1010 1.10 mrg <samp>-mno-madd4</samp> option is passed. This is the default. 1011 1.10 mrg </p> 1012 1.10 mrg </dd> 1013 1.14 mrg <dt><span><code>--without-madd4</code></span></dt> 1014 1.10 mrg <dd><p>On MIPS targets, make <samp>-mno-madd4</samp> the default when no 1015 1.10 mrg <samp>-mmadd4</samp> option is passed. The <code>madd4</code> instruction 1016 1.9 mrg family can be problematic when targeting a combination of cores that 1017 1.9 mrg implement these instructions differently. There are two known cores 1018 1.9 mrg that implement these as fused operations instead of unfused (where 1019 1.9 mrg unfused is normally expected). Disabling these instructions is the 1020 1.9 mrg only way to ensure compatible code is generated; this will incur 1021 1.9 mrg a performance penalty. 1022 1.10 mrg </p> 1023 1.10 mrg </dd> 1024 1.14 mrg <dt><span><code>--with-mips-plt</code></span></dt> 1025 1.10 mrg <dd><p>On MIPS targets, make use of copy relocations and PLTs. 1026 1.1 mrg These features are extensions to the traditional 1027 1.1 mrg SVR4-based MIPS ABIs and require support from GNU binutils 1028 1.1 mrg and the runtime C library. 1029 1.10 mrg </p> 1030 1.10 mrg </dd> 1031 1.14 mrg <dt><span><code>--with-stack-clash-protection-guard-size=<var>size</var></code></span></dt> 1032 1.12 mrg <dd><p>On certain targets this option sets the default stack clash protection guard 1033 1.12 mrg size as a power of two in bytes. On AArch64 <var>size</var> is required to be either 1034 1.12 mrg 12 (4KB) or 16 (64KB). 1035 1.12 mrg </p> 1036 1.12 mrg </dd> 1037 1.14 mrg <dt><span><code>--enable-__cxa_atexit</code></span></dt> 1038 1.10 mrg <dd><p>Define if you want to use __cxa_atexit, rather than atexit, to 1039 1.10 mrg register C++ destructors for local statics and global objects. 1040 1.1 mrg This is essential for fully standards-compliant handling of 1041 1.1 mrg destructors, but requires __cxa_atexit in libc. This option is currently 1042 1.1 mrg only available on systems with GNU libc. When enabled, this will cause 1043 1.10 mrg <samp>-fuse-cxa-atexit</samp> to be passed by default. 1044 1.10 mrg </p> 1045 1.10 mrg </dd> 1046 1.14 mrg <dt><span><code>--enable-gnu-indirect-function</code></span></dt> 1047 1.10 mrg <dd><p>Define if you want to enable the <code>ifunc</code> attribute. This option is 1048 1.3 skrll currently only available on systems with GNU libc on certain targets. 1049 1.10 mrg </p> 1050 1.10 mrg </dd> 1051 1.14 mrg <dt><span><code>--enable-target-optspace</code></span></dt> 1052 1.10 mrg <dd><p>Specify that target 1053 1.10 mrg libraries should be optimized for code space instead of code speed. 1054 1.1 mrg This is the default for the m32r platform. 1055 1.10 mrg </p> 1056 1.10 mrg </dd> 1057 1.14 mrg <dt><span><code>--with-cpp-install-dir=<var>dirname</var></code></span></dt> 1058 1.10 mrg <dd><p>Specify that the user visible <code>cpp</code> program should be installed 1059 1.10 mrg in <samp><var>prefix</var>/<var>dirname</var>/cpp</samp>, in addition to <var>bindir</var>. 1060 1.10 mrg </p> 1061 1.10 mrg </dd> 1062 1.14 mrg <dt><span><code>--enable-comdat</code></span></dt> 1063 1.10 mrg <dd><p>Enable COMDAT group support. This is primarily used to override the 1064 1.1 mrg automatically detected value. 1065 1.10 mrg </p> 1066 1.10 mrg </dd> 1067 1.14 mrg <dt><span><code>--enable-initfini-array</code></span></dt> 1068 1.10 mrg <dd><p>Force the use of sections <code>.init_array</code> and <code>.fini_array</code> 1069 1.1 mrg (instead of <code>.init</code> and <code>.fini</code>) for constructors and 1070 1.10 mrg destructors. Option <samp>--disable-initfini-array</samp> has the 1071 1.1 mrg opposite effect. If neither option is specified, the configure script 1072 1.1 mrg will try to guess whether the <code>.init_array</code> and 1073 1.1 mrg <code>.fini_array</code> sections are supported and, if they are, use them. 1074 1.10 mrg </p> 1075 1.10 mrg </dd> 1076 1.14 mrg <dt><span><code>--enable-link-mutex</code></span></dt> 1077 1.10 mrg <dd><p>When building GCC, use a mutex to avoid linking the compilers for 1078 1.5 mrg multiple languages at the same time, to avoid thrashing on build 1079 1.5 mrg systems with limited free memory. The default is not to use such a mutex. 1080 1.10 mrg </p> 1081 1.10 mrg </dd> 1082 1.14 mrg <dt><span><code>--enable-maintainer-mode</code></span></dt> 1083 1.10 mrg <dd><p>The build rules that regenerate the Autoconf and Automake output files as 1084 1.10 mrg well as the GCC master message catalog <samp>gcc.pot</samp> are normally 1085 1.1 mrg disabled. This is because it can only be rebuilt if the complete source 1086 1.1 mrg tree is present. If you have changed the sources and want to rebuild the 1087 1.10 mrg catalog, configuring with <samp>--enable-maintainer-mode</samp> will enable 1088 1.1 mrg this. Note that you need a recent version of the <code>gettext</code> tools 1089 1.1 mrg to do so. 1090 1.10 mrg </p> 1091 1.10 mrg </dd> 1092 1.14 mrg <dt><span><code>--disable-bootstrap</code></span></dt> 1093 1.10 mrg <dd><p>For a native build, the default configuration is to perform 1094 1.10 mrg a 3-stage bootstrap of the compiler when ‘<samp>make</samp>’ is invoked, 1095 1.1 mrg testing that GCC can compile itself correctly. If you want to disable 1096 1.10 mrg this process, you can configure with <samp>--disable-bootstrap</samp>. 1097 1.10 mrg </p> 1098 1.10 mrg </dd> 1099 1.14 mrg <dt><span><code>--enable-bootstrap</code></span></dt> 1100 1.10 mrg <dd><p>In special cases, you may want to perform a 3-stage build 1101 1.10 mrg even if the target and host triplets are different. 1102 1.1 mrg This is possible when the host can run code compiled for 1103 1.10 mrg the target (e.g. host is i686-linux, target is i486-linux). 1104 1.1 mrg Starting from GCC 4.2, to do this you have to configure explicitly 1105 1.10 mrg with <samp>--enable-bootstrap</samp>. 1106 1.10 mrg </p> 1107 1.10 mrg </dd> 1108 1.14 mrg <dt><span><code>--enable-generated-files-in-srcdir</code></span></dt> 1109 1.10 mrg <dd><p>Neither the .c and .h files that are generated from Bison and flex nor the 1110 1.1 mrg info manuals and man pages that are built from the .texi files are present 1111 1.11 mrg in the repository development tree. When building GCC from that development tree, 1112 1.1 mrg or from one of our snapshots, those generated files are placed in your 1113 1.1 mrg build directory, which allows for the source to be in a readonly 1114 1.1 mrg directory. 1115 1.10 mrg </p> 1116 1.10 mrg <p>If you configure with <samp>--enable-generated-files-in-srcdir</samp> then those 1117 1.1 mrg generated files will go into the source directory. This is mainly intended 1118 1.1 mrg for generating release or prerelease tarballs of the GCC sources, since it 1119 1.1 mrg is not a requirement that the users of source releases to have flex, Bison, 1120 1.1 mrg or makeinfo. 1121 1.10 mrg </p> 1122 1.10 mrg </dd> 1123 1.14 mrg <dt><span><code>--enable-version-specific-runtime-libs</code></span></dt> 1124 1.10 mrg <dd><p>Specify 1125 1.1 mrg that runtime libraries should be installed in the compiler specific 1126 1.10 mrg subdirectory (<samp><var>libdir</var>/gcc</samp>) rather than the usual places. In 1127 1.10 mrg addition, ‘<samp>libstdc++</samp>’’s include files will be installed into 1128 1.1 mrg <samp><var>libdir</var></samp> unless you overruled it by using 1129 1.10 mrg <samp>--with-gxx-include-dir=<var>dirname</var></samp>. Using this option is 1130 1.1 mrg particularly useful if you intend to use several versions of GCC in 1131 1.13 mrg parallel. The default is ‘<samp>yes</samp>’ for ‘<samp>libada</samp>’, and ‘<samp>no</samp>’ for 1132 1.13 mrg the remaining libraries. 1133 1.10 mrg </p> 1134 1.10 mrg </dd> 1135 1.14 mrg <dt><span><code><span id="WithAixSoname"></span>--with-aix-soname=‘<samp>aix</samp>’, ‘<samp>svr4</samp>’ or ‘<samp>both</samp>’</code></span></dt> 1136 1.10 mrg <dd><p>Traditional AIX shared library versioning (versioned <code>Shared Object</code> 1137 1.5 mrg files as members of unversioned <code>Archive Library</code> files named 1138 1.10 mrg ‘<samp>lib.a</samp>’) causes numerous headaches for package managers. However, 1139 1.5 mrg <code>Import Files</code> as members of <code>Archive Library</code> files allow for 1140 1.5 mrg <strong>filename-based versioning</strong> of shared libraries as seen on Linux/SVR4, 1141 1.10 mrg where this is called the "SONAME". But as they prevent static linking, 1142 1.5 mrg <code>Import Files</code> may be used with <code>Runtime Linking</code> only, where the 1143 1.10 mrg linker does search for ‘<samp>libNAME.so</samp>’ before ‘<samp>libNAME.a</samp>’ library 1144 1.10 mrg filenames with the ‘<samp>-lNAME</samp>’ linker flag. 1145 1.10 mrg </p> 1146 1.14 mrg <span id="AixLdCommand"></span><p>For detailed information please refer to the AIX 1147 1.10 mrg <a href="https://www.ibm.com/support/knowledgecenter/search/%22the%20ld%20command%2C%20also%20called%20the%20linkage%20editor%20or%20binder%22">ld 1148 1.10 mrg Command</a> reference. 1149 1.10 mrg </p> 1150 1.10 mrg <p>As long as shared library creation is enabled, upon: 1151 1.10 mrg </p><dl compact="compact"> 1152 1.14 mrg <dt><span><code>--with-aix-soname=aix</code></span></dt> 1153 1.14 mrg <dt><span><code>--with-aix-soname=both</code></span></dt> 1154 1.10 mrg <dd><p>A (traditional AIX) <code>Shared Archive Library</code> file is created: 1155 1.10 mrg </p><ul> 1156 1.10 mrg <li> using the ‘<samp>libNAME.a</samp>’ filename scheme 1157 1.10 mrg </li><li> with the <code>Shared Object</code> file as archive member named 1158 1.10 mrg ‘<samp>libNAME.so.V</samp>’ (except for ‘<samp>libgcc_s</samp>’, where the <code>Shared 1159 1.10 mrg Object</code> file is named ‘<samp>shr.o</samp>’ for backwards compatibility), which 1160 1.10 mrg <ul class="no-bullet"> 1161 1.10 mrg <li>- is used for runtime loading from inside the ‘<samp>libNAME.a</samp>’ file 1162 1.10 mrg </li><li>- is used for dynamic loading via 1163 1.10 mrg <code>dlopen("libNAME.a(libNAME.so.V)", RTLD_MEMBER)</code> 1164 1.10 mrg </li><li>- is used for shared linking 1165 1.10 mrg </li><li>- is used for static linking, so no separate <code>Static Archive 1166 1.5 mrg Library</code> file is needed 1167 1.10 mrg </li></ul> 1168 1.10 mrg </li></ul> 1169 1.10 mrg </dd> 1170 1.14 mrg <dt><span><code>--with-aix-soname=both</code></span></dt> 1171 1.14 mrg <dt><span><code>--with-aix-soname=svr4</code></span></dt> 1172 1.10 mrg <dd><p>A (second) <code>Shared Archive Library</code> file is created: 1173 1.10 mrg </p><ul> 1174 1.10 mrg <li> using the ‘<samp>libNAME.so.V</samp>’ filename scheme 1175 1.10 mrg </li><li> with the <code>Shared Object</code> file as archive member named 1176 1.10 mrg ‘<samp>shr.o</samp>’, which 1177 1.10 mrg <ul class="no-bullet"> 1178 1.10 mrg <li>- is created with the <code>-G linker flag</code> 1179 1.10 mrg </li><li>- has the <code>F_LOADONLY</code> flag set 1180 1.10 mrg </li><li>- is used for runtime loading from inside the ‘<samp>libNAME.so.V</samp>’ file 1181 1.10 mrg </li><li>- is used for dynamic loading via <code>dlopen("libNAME.so.V(shr.o)", 1182 1.5 mrg RTLD_MEMBER)</code> 1183 1.10 mrg </li></ul> 1184 1.10 mrg </li><li> with the <code>Import File</code> as archive member named ‘<samp>shr.imp</samp>’, 1185 1.5 mrg which 1186 1.10 mrg <ul class="no-bullet"> 1187 1.10 mrg <li>- refers to ‘<samp>libNAME.so.V(shr.o)</samp>’ as the "SONAME", to be recorded 1188 1.5 mrg in the <code>Loader Section</code> of subsequent binaries 1189 1.10 mrg </li><li>- indicates whether ‘<samp>libNAME.so.V(shr.o)</samp>’ is 32 or 64 bit 1190 1.10 mrg </li><li>- lists all the public symbols exported by ‘<samp>lib.so.V(shr.o)</samp>’, 1191 1.10 mrg eventually decorated with the <code>‘<samp>weak</samp>’ Keyword</code> 1192 1.10 mrg </li><li>- is necessary for shared linking against ‘<samp>lib.so.V(shr.o)</samp>’ 1193 1.10 mrg </li></ul> 1194 1.10 mrg </li></ul> 1195 1.10 mrg <p>A symbolic link using the ‘<samp>libNAME.so</samp>’ filename scheme is created: 1196 1.10 mrg </p><ul> 1197 1.10 mrg <li> pointing to the ‘<samp>libNAME.so.V</samp>’ <code>Shared Archive Library</code> file 1198 1.10 mrg </li><li> to permit the <code>ld Command</code> to find ‘<samp>lib.so.V(shr.imp)</samp>’ via 1199 1.10 mrg the ‘<samp>-lNAME</samp>’ argument (requires <code>Runtime Linking</code> to be enabled) 1200 1.10 mrg </li><li> to permit dynamic loading of ‘<samp>lib.so.V(shr.o)</samp>’ without the need 1201 1.10 mrg to specify the version number via <code>dlopen("libNAME.so(shr.o)", 1202 1.5 mrg RTLD_MEMBER)</code> 1203 1.10 mrg </li></ul> 1204 1.10 mrg </dd> 1205 1.10 mrg </dl> 1206 1.5 mrg 1207 1.10 mrg <p>As long as static library creation is enabled, upon: 1208 1.10 mrg </p><dl compact="compact"> 1209 1.14 mrg <dt><span><code>--with-aix-soname=svr4</code></span></dt> 1210 1.10 mrg <dd><p>A <code>Static Archive Library</code> is created: 1211 1.10 mrg </p><ul> 1212 1.10 mrg <li> using the ‘<samp>libNAME.a</samp>’ filename scheme 1213 1.10 mrg </li><li> with all the <code>Static Object</code> files as archive members, which 1214 1.10 mrg <ul class="no-bullet"> 1215 1.10 mrg <li>- are used for static linking 1216 1.10 mrg </li></ul> 1217 1.10 mrg </li></ul> 1218 1.10 mrg </dd> 1219 1.10 mrg </dl> 1220 1.5 mrg 1221 1.10 mrg <p>While the aix-soname=‘<samp>svr4</samp>’ option does not create <code>Shared Object</code> 1222 1.5 mrg files as members of unversioned <code>Archive Library</code> files any more, package 1223 1.5 mrg managers still are responsible to 1224 1.5 mrg <a href="./specific.html#TransferAixShobj">transfer</a> <code>Shared Object</code> files 1225 1.5 mrg found as member of a previously installed unversioned <code>Archive Library</code> 1226 1.5 mrg file into the newly installed <code>Archive Library</code> file with the same 1227 1.5 mrg filename. 1228 1.10 mrg </p> 1229 1.10 mrg <p><em>WARNING:</em> Creating <code>Shared Object</code> files with <code>Runtime Linking</code> 1230 1.5 mrg enabled may bloat the TOC, eventually leading to <code>TOC overflow</code> errors, 1231 1.10 mrg requiring the use of either the <samp>-Wl,-bbigtoc</samp> linker flag (seen to 1232 1.5 mrg break with the <code>GDB</code> debugger) or some of the TOC-related compiler flags, 1233 1.5 mrg see “RS/6000 and PowerPC Options” in the main manual. 1234 1.10 mrg </p> 1235 1.10 mrg <p><samp>--with-aix-soname</samp> is currently supported by ‘<samp>libgcc_s</samp>’ only, so 1236 1.5 mrg this option is still experimental and not for normal use yet. 1237 1.10 mrg </p> 1238 1.10 mrg <p>Default is the traditional behavior <samp>--with-aix-soname=‘<samp>aix</samp>’</samp>. 1239 1.10 mrg </p> 1240 1.10 mrg </dd> 1241 1.14 mrg <dt><span><code>--enable-languages=<var>lang1</var>,<var>lang2</var>,…</code></span></dt> 1242 1.10 mrg <dd><p>Specify that only a particular subset of compilers and 1243 1.1 mrg their runtime libraries should be built. For a list of valid values for 1244 1.1 mrg <var>langN</var> you can issue the following command in the 1245 1.10 mrg <samp>gcc</samp> directory of your GCC source tree:<br> 1246 1.14 mrg </p><div class="example"> 1247 1.14 mrg <pre class="example">grep ^language= */config-lang.in 1248 1.10 mrg </pre></div> 1249 1.10 mrg <p>Currently, you can use any of the following: 1250 1.12 mrg <code>all</code>, <code>default</code>, <code>ada</code>, <code>c</code>, <code>c++</code>, <code>d</code>, 1251 1.12 mrg <code>fortran</code>, <code>go</code>, <code>jit</code>, <code>lto</code>, <code>objc</code>, <code>obj-c++</code>. 1252 1.10 mrg Building the Ada compiler has special requirements, see below. 1253 1.10 mrg If you do not pass this flag, or specify the option <code>default</code>, then the 1254 1.10 mrg default languages available in the <samp>gcc</samp> sub-tree will be configured. 1255 1.12 mrg Ada, D, Go, Jit, and Objective-C++ are not default languages. LTO is not a 1256 1.10 mrg default language, but is built by default because <samp>--enable-lto</samp> is 1257 1.10 mrg enabled by default. The other languages are default languages. If 1258 1.10 mrg <code>all</code> is specified, then all available languages are built. An 1259 1.10 mrg exception is <code>jit</code> language, which requires 1260 1.10 mrg <samp>--enable-host-shared</samp> to be included with <code>all</code>. 1261 1.10 mrg </p> 1262 1.10 mrg </dd> 1263 1.14 mrg <dt><span><code>--enable-stage1-languages=<var>lang1</var>,<var>lang2</var>,…</code></span></dt> 1264 1.10 mrg <dd><p>Specify that a particular subset of compilers and their runtime 1265 1.1 mrg libraries should be built with the system C compiler during stage 1 of 1266 1.1 mrg the bootstrap process, rather than only in later stages with the 1267 1.1 mrg bootstrapped C compiler. The list of valid values is the same as for 1268 1.10 mrg <samp>--enable-languages</samp>, and the option <code>all</code> will select all 1269 1.10 mrg of the languages enabled by <samp>--enable-languages</samp>. This option is 1270 1.1 mrg primarily useful for GCC development; for instance, when a development 1271 1.1 mrg version of the compiler cannot bootstrap due to compiler bugs, or when 1272 1.1 mrg one is debugging front ends other than the C front end. When this 1273 1.1 mrg option is used, one can then build the target libraries for the 1274 1.10 mrg specified languages with the stage-1 compiler by using <code>make 1275 1.10 mrg stage1-bubble all-target</code>, or run the testsuite on the stage-1 compiler 1276 1.10 mrg for the specified languages using <code>make stage1-start check-gcc</code>. 1277 1.10 mrg </p> 1278 1.10 mrg </dd> 1279 1.14 mrg <dt><span><code>--disable-libada</code></span></dt> 1280 1.10 mrg <dd><p>Specify that the run-time libraries and tools used by GNAT should not 1281 1.1 mrg be built. This can be useful for debugging, or for compatibility with 1282 1.1 mrg previous Ada build procedures, when it was required to explicitly 1283 1.10 mrg do a ‘<samp>make -C gcc gnatlib_and_tools</samp>’. 1284 1.10 mrg </p> 1285 1.10 mrg </dd> 1286 1.14 mrg <dt><span><code>--disable-libsanitizer</code></span></dt> 1287 1.10 mrg <dd><p>Specify that the run-time libraries for the various sanitizers should 1288 1.5 mrg not be built. 1289 1.10 mrg </p> 1290 1.10 mrg </dd> 1291 1.14 mrg <dt><span><code>--disable-libssp</code></span></dt> 1292 1.10 mrg <dd><p>Specify that the run-time libraries for stack smashing protection 1293 1.10 mrg should not be built or linked against. On many targets library support 1294 1.10 mrg is provided by the C library instead. 1295 1.10 mrg </p> 1296 1.10 mrg </dd> 1297 1.14 mrg <dt><span><code>--disable-libquadmath</code></span></dt> 1298 1.10 mrg <dd><p>Specify that the GCC quad-precision math library should not be built. 1299 1.3 skrll On some systems, the library is required to be linkable when building 1300 1.10 mrg the Fortran front end, unless <samp>--disable-libquadmath-support</samp> 1301 1.3 skrll is used. 1302 1.10 mrg </p> 1303 1.10 mrg </dd> 1304 1.14 mrg <dt><span><code>--disable-libquadmath-support</code></span></dt> 1305 1.10 mrg <dd><p>Specify that the Fortran front end and <code>libgfortran</code> do not add 1306 1.3 skrll support for <code>libquadmath</code> on systems supporting it. 1307 1.10 mrg </p> 1308 1.10 mrg </dd> 1309 1.14 mrg <dt><span><code>--disable-libgomp</code></span></dt> 1310 1.10 mrg <dd><p>Specify that the GNU Offloading and Multi Processing Runtime Library 1311 1.5 mrg should not be built. 1312 1.10 mrg </p> 1313 1.10 mrg </dd> 1314 1.14 mrg <dt><span><code>--disable-libvtv</code></span></dt> 1315 1.10 mrg <dd><p>Specify that the run-time libraries used by vtable verification 1316 1.5 mrg should not be built. 1317 1.10 mrg </p> 1318 1.10 mrg </dd> 1319 1.14 mrg <dt><span><code>--with-dwarf2</code></span></dt> 1320 1.10 mrg <dd><p>Specify that the compiler should 1321 1.1 mrg use DWARF 2 debugging information as the default. 1322 1.10 mrg </p> 1323 1.10 mrg </dd> 1324 1.14 mrg <dt><span><code>--with-advance-toolchain=<var>at</var></code></span></dt> 1325 1.10 mrg <dd><p>On 64-bit PowerPC Linux systems, configure the compiler to use the 1326 1.7 mrg header files, library files, and the dynamic linker from the Advance 1327 1.7 mrg Toolchain release <var>at</var> instead of the default versions that are 1328 1.7 mrg provided by the Linux distribution. In general, this option is 1329 1.7 mrg intended for the developers of GCC, and it is not intended for general 1330 1.7 mrg use. 1331 1.10 mrg </p> 1332 1.10 mrg </dd> 1333 1.14 mrg <dt><span><code>--enable-targets=all</code></span></dt> 1334 1.14 mrg <dt><span><code>--enable-targets=<var>target_list</var></code></span></dt> 1335 1.10 mrg <dd><p>Some GCC targets, e.g. powerpc64-linux, build bi-arch compilers. 1336 1.1 mrg These are compilers that are able to generate either 64-bit or 32-bit 1337 1.10 mrg code. Typically, the corresponding 32-bit target, e.g. 1338 1.1 mrg powerpc-linux for powerpc64-linux, only generates 32-bit code. This 1339 1.1 mrg option enables the 32-bit target to be a bi-arch compiler, which is 1340 1.1 mrg useful when you want a bi-arch compiler that defaults to 32-bit, and 1341 1.10 mrg you are building a bi-arch or multi-arch binutils in a combined tree. 1342 1.1 mrg On mips-linux, this will build a tri-arch compiler (ABI o32/n32/64), 1343 1.10 mrg defaulted to o32. 1344 1.3 skrll Currently, this option only affects sparc-linux, powerpc-linux, x86-linux, 1345 1.3 skrll mips-linux and s390-linux. 1346 1.10 mrg </p> 1347 1.10 mrg </dd> 1348 1.14 mrg <dt><span><code>--enable-default-pie</code></span></dt> 1349 1.10 mrg <dd><p>Turn on <samp>-fPIE</samp> and <samp>-pie</samp> by default. 1350 1.10 mrg </p> 1351 1.10 mrg </dd> 1352 1.14 mrg <dt><span><code>--enable-secureplt</code></span></dt> 1353 1.10 mrg <dd><p>This option enables <samp>-msecure-plt</samp> by default for powerpc-linux. 1354 1.1 mrg See “RS/6000 and PowerPC Options” in the main manual 1355 1.10 mrg </p> 1356 1.10 mrg </dd> 1357 1.14 mrg <dt><span><code>--enable-default-ssp</code></span></dt> 1358 1.10 mrg <dd><p>Turn on <samp>-fstack-protector-strong</samp> by default. 1359 1.10 mrg </p> 1360 1.10 mrg </dd> 1361 1.14 mrg <dt><span><code>--enable-cld</code></span></dt> 1362 1.10 mrg <dd><p>This option enables <samp>-mcld</samp> by default for 32-bit x86 targets. 1363 1.1 mrg See “i386 and x86-64 Options” in the main manual 1364 1.10 mrg </p> 1365 1.10 mrg </dd> 1366 1.14 mrg <dt><span><code>--enable-large-address-aware</code></span></dt> 1367 1.12 mrg <dd><p>The <samp>--enable-large-address-aware</samp> option arranges for MinGW 1368 1.12 mrg executables to be linked using the <samp>--large-address-aware</samp> 1369 1.12 mrg option, that enables the use of more than 2GB of memory. If GCC is 1370 1.12 mrg configured with this option, its effects can be reversed by passing the 1371 1.12 mrg <samp>-Wl,--disable-large-address-aware</samp> option to the so-configured 1372 1.12 mrg compiler driver. 1373 1.12 mrg </p> 1374 1.12 mrg </dd> 1375 1.14 mrg <dt><span><code>--enable-win32-registry</code></span></dt> 1376 1.14 mrg <dt><span><code>--enable-win32-registry=<var>key</var></code></span></dt> 1377 1.14 mrg <dt><span><code>--disable-win32-registry</code></span></dt> 1378 1.10 mrg <dd><p>The <samp>--enable-win32-registry</samp> option enables Microsoft Windows-hosted GCC 1379 1.1 mrg to look up installations paths in the registry using the following key: 1380 1.10 mrg </p> 1381 1.14 mrg <div class="example"> 1382 1.14 mrg <pre class="example"><code>HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\<var>key</var></code> 1383 1.10 mrg </pre></div> 1384 1.1 mrg 1385 1.10 mrg <p><var>key</var> defaults to GCC version number, and can be overridden by the 1386 1.10 mrg <samp>--enable-win32-registry=<var>key</var></samp> option. Vendors and distributors 1387 1.1 mrg who use custom installers are encouraged to provide a different key, 1388 1.1 mrg perhaps one comprised of vendor name and GCC version number, to 1389 1.1 mrg avoid conflict with existing installations. This feature is enabled 1390 1.10 mrg by default, and can be disabled by <samp>--disable-win32-registry</samp> 1391 1.1 mrg option. This option has no effect on the other hosts. 1392 1.10 mrg </p> 1393 1.10 mrg </dd> 1394 1.14 mrg <dt><span><code>--nfp</code></span></dt> 1395 1.10 mrg <dd><p>Specify that the machine does not have a floating point unit. This 1396 1.10 mrg option only applies to ‘<samp>m68k-sun-sunos<var>n</var></samp>’. On any other 1397 1.10 mrg system, <samp>--nfp</samp> has no effect. 1398 1.10 mrg </p> 1399 1.10 mrg </dd> 1400 1.14 mrg <dt><span><code>--enable-werror</code></span></dt> 1401 1.14 mrg <dt><span><code>--disable-werror</code></span></dt> 1402 1.14 mrg <dt><span><code>--enable-werror=yes</code></span></dt> 1403 1.14 mrg <dt><span><code>--enable-werror=no</code></span></dt> 1404 1.10 mrg <dd><p>When you specify this option, it controls whether certain files in the 1405 1.10 mrg compiler are built with <samp>-Werror</samp> in bootstrap stage2 and later. 1406 1.10 mrg If you don’t specify it, <samp>-Werror</samp> is turned on for the main 1407 1.1 mrg development trunk. However it defaults to off for release branches and 1408 1.10 mrg final releases. The specific files which get <samp>-Werror</samp> are 1409 1.1 mrg controlled by the Makefiles. 1410 1.10 mrg </p> 1411 1.10 mrg </dd> 1412 1.14 mrg <dt><span><code>--enable-checking</code></span></dt> 1413 1.14 mrg <dt><span><code>--disable-checking</code></span></dt> 1414 1.14 mrg <dt><span><code>--enable-checking=<var>list</var></code></span></dt> 1415 1.11 mrg <dd><p>This option controls performing internal consistency checks in the compiler. 1416 1.11 mrg It does not change the generated code, but adds error checking of the 1417 1.11 mrg requested complexity. This slows down the compiler and may only work 1418 1.11 mrg properly if you are building the compiler with GCC. 1419 1.11 mrg </p> 1420 1.11 mrg <p>When the option is not specified, the active set of checks depends on context. 1421 1.11 mrg Namely, bootstrap stage 1 defaults to ‘<samp>--enable-checking=yes</samp>’, builds 1422 1.11 mrg from release branches or release archives default to 1423 1.11 mrg ‘<samp>--enable-checking=release</samp>’, and otherwise 1424 1.11 mrg ‘<samp>--enable-checking=yes,extra</samp>’ is used. When the option is 1425 1.11 mrg specified without a <var>list</var>, the result is the same as 1426 1.11 mrg ‘<samp>--enable-checking=yes</samp>’. Likewise, ‘<samp>--disable-checking</samp>’ is 1427 1.11 mrg equivalent to ‘<samp>--enable-checking=no</samp>’. 1428 1.11 mrg </p> 1429 1.11 mrg <p>The categories of checks available in <var>list</var> are ‘<samp>yes</samp>’ (most common 1430 1.11 mrg checks ‘<samp>assert,misc,gc,gimple,rtlflag,runtime,tree,types</samp>’), ‘<samp>no</samp>’ 1431 1.11 mrg (no checks at all), ‘<samp>all</samp>’ (all but ‘<samp>valgrind</samp>’), ‘<samp>release</samp>’ 1432 1.11 mrg (cheapest checks ‘<samp>assert,runtime</samp>’) or ‘<samp>none</samp>’ (same as ‘<samp>no</samp>’). 1433 1.11 mrg ‘<samp>release</samp>’ checks are always on and to disable them 1434 1.11 mrg ‘<samp>--disable-checking</samp>’ or ‘<samp>--enable-checking=no[,<other checks>]</samp>’ 1435 1.11 mrg must be explicitly requested. Disabling assertions makes the compiler and 1436 1.11 mrg runtime slightly faster but increases the risk of undetected internal errors 1437 1.11 mrg causing wrong code to be generated. 1438 1.11 mrg </p> 1439 1.11 mrg <p>Individual checks can be enabled with these flags: ‘<samp>assert</samp>’, ‘<samp>df</samp>’, 1440 1.11 mrg ‘<samp>extra</samp>’, ‘<samp>fold</samp>’, ‘<samp>gc</samp>’, ‘<samp>gcac</samp>’, ‘<samp>gimple</samp>’, 1441 1.11 mrg ‘<samp>misc</samp>’, ‘<samp>rtl</samp>’, ‘<samp>rtlflag</samp>’, ‘<samp>runtime</samp>’, ‘<samp>tree</samp>’, 1442 1.11 mrg ‘<samp>types</samp>’ and ‘<samp>valgrind</samp>’. ‘<samp>extra</samp>’ extends ‘<samp>misc</samp>’ 1443 1.11 mrg checking with extra checks that might affect code generation and should 1444 1.11 mrg therefore not differ between stage1 and later stages in bootstrap. 1445 1.11 mrg </p> 1446 1.11 mrg <p>The ‘<samp>valgrind</samp>’ check requires the external <code>valgrind</code> simulator, 1447 1.11 mrg available from <a href="http://valgrind.org/">http://valgrind.org/</a>. The ‘<samp>rtl</samp>’ checks are 1448 1.11 mrg expensive and the ‘<samp>df</samp>’, ‘<samp>gcac</samp>’ and ‘<samp>valgrind</samp>’ checks are very 1449 1.11 mrg expensive. 1450 1.10 mrg </p> 1451 1.10 mrg </dd> 1452 1.14 mrg <dt><span><code>--disable-stage1-checking</code></span></dt> 1453 1.14 mrg <dt><span><code>--enable-stage1-checking</code></span></dt> 1454 1.14 mrg <dt><span><code>--enable-stage1-checking=<var>list</var></code></span></dt> 1455 1.11 mrg <dd><p>This option affects only bootstrap build. If no <samp>--enable-checking</samp> 1456 1.11 mrg option is specified the stage1 compiler is built with ‘<samp>yes</samp>’ checking 1457 1.11 mrg enabled, otherwise the stage1 checking flags are the same as specified by 1458 1.10 mrg <samp>--enable-checking</samp>. To build the stage1 compiler with 1459 1.10 mrg different checking options use <samp>--enable-stage1-checking</samp>. 1460 1.10 mrg The list of checking options is the same as for <samp>--enable-checking</samp>. 1461 1.1 mrg If your system is too slow or too small to bootstrap a released compiler 1462 1.10 mrg with checking for stage1 enabled, you can use ‘<samp>--disable-stage1-checking</samp>’ 1463 1.1 mrg to disable checking for the stage1 compiler. 1464 1.10 mrg </p> 1465 1.10 mrg </dd> 1466 1.14 mrg <dt><span><code>--enable-coverage</code></span></dt> 1467 1.14 mrg <dt><span><code>--enable-coverage=<var>level</var></code></span></dt> 1468 1.10 mrg <dd><p>With this option, the compiler is built to collect self coverage 1469 1.1 mrg information, every time it is run. This is for internal development 1470 1.1 mrg purposes, and only works when the compiler is being built with gcc. The 1471 1.1 mrg <var>level</var> argument controls whether the compiler is built optimized or 1472 1.10 mrg not, values are ‘<samp>opt</samp>’ and ‘<samp>noopt</samp>’. For coverage analysis you 1473 1.1 mrg want to disable optimization, for performance analysis you want to 1474 1.1 mrg enable optimization. When coverage is enabled, the default level is 1475 1.1 mrg without optimization. 1476 1.10 mrg </p> 1477 1.10 mrg </dd> 1478 1.14 mrg <dt><span><code>--enable-gather-detailed-mem-stats</code></span></dt> 1479 1.10 mrg <dd><p>When this option is specified more detailed information on memory 1480 1.1 mrg allocation is gathered. This information is printed when using 1481 1.10 mrg <samp>-fmem-report</samp>. 1482 1.10 mrg </p> 1483 1.10 mrg </dd> 1484 1.14 mrg <dt><span><code>--enable-valgrind-annotations</code></span></dt> 1485 1.10 mrg <dd><p>Mark selected memory related operations in the compiler when run under 1486 1.7 mrg valgrind to suppress false positives. 1487 1.10 mrg </p> 1488 1.10 mrg </dd> 1489 1.14 mrg <dt><span><code>--enable-nls</code></span></dt> 1490 1.14 mrg <dt><span><code>--disable-nls</code></span></dt> 1491 1.10 mrg <dd><p>The <samp>--enable-nls</samp> option enables Native Language Support (NLS), 1492 1.1 mrg which lets GCC output diagnostics in languages other than American 1493 1.1 mrg English. Native Language Support is enabled by default if not doing a 1494 1.10 mrg canadian cross build. The <samp>--disable-nls</samp> option disables NLS. 1495 1.10 mrg </p> 1496 1.10 mrg </dd> 1497 1.14 mrg <dt><span><code>--with-included-gettext</code></span></dt> 1498 1.10 mrg <dd><p>If NLS is enabled, the <samp>--with-included-gettext</samp> option causes the build 1499 1.10 mrg procedure to prefer its copy of GNU <code>gettext</code>. 1500 1.10 mrg </p> 1501 1.10 mrg </dd> 1502 1.14 mrg <dt><span><code>--with-catgets</code></span></dt> 1503 1.10 mrg <dd><p>If NLS is enabled, and if the host lacks <code>gettext</code> but has the 1504 1.1 mrg inferior <code>catgets</code> interface, the GCC build procedure normally 1505 1.10 mrg ignores <code>catgets</code> and instead uses GCC’s copy of the GNU 1506 1.10 mrg <code>gettext</code> library. The <samp>--with-catgets</samp> option causes the 1507 1.10 mrg build procedure to use the host’s <code>catgets</code> in this situation. 1508 1.10 mrg </p> 1509 1.10 mrg </dd> 1510 1.14 mrg <dt><span><code>--with-libiconv-prefix=<var>dir</var></code></span></dt> 1511 1.10 mrg <dd><p>Search for libiconv header files in <samp><var>dir</var>/include</samp> and 1512 1.10 mrg libiconv library files in <samp><var>dir</var>/lib</samp>. 1513 1.10 mrg </p> 1514 1.10 mrg </dd> 1515 1.14 mrg <dt><span><code>--enable-obsolete</code></span></dt> 1516 1.10 mrg <dd><p>Enable configuration for an obsoleted system. If you attempt to 1517 1.1 mrg configure GCC for a system (build, host, or target) which has been 1518 1.1 mrg obsoleted, and you do not specify this flag, configure will halt with an 1519 1.1 mrg error message. 1520 1.10 mrg </p> 1521 1.10 mrg <p>All support for systems which have been obsoleted in one release of GCC 1522 1.1 mrg is removed entirely in the next major release, unless someone steps 1523 1.1 mrg forward to maintain the port. 1524 1.10 mrg </p> 1525 1.10 mrg </dd> 1526 1.14 mrg <dt><span><code>--enable-decimal-float</code></span></dt> 1527 1.14 mrg <dt><span><code>--enable-decimal-float=yes</code></span></dt> 1528 1.14 mrg <dt><span><code>--enable-decimal-float=no</code></span></dt> 1529 1.14 mrg <dt><span><code>--enable-decimal-float=bid</code></span></dt> 1530 1.14 mrg <dt><span><code>--enable-decimal-float=dpd</code></span></dt> 1531 1.14 mrg <dt><span><code>--disable-decimal-float</code></span></dt> 1532 1.10 mrg <dd><p>Enable (or disable) support for the C decimal floating point extension 1533 1.1 mrg that is in the IEEE 754-2008 standard. This is enabled by default only 1534 1.1 mrg on PowerPC, i386, and x86_64 GNU/Linux systems. Other systems may also 1535 1.1 mrg support it, but require the user to specifically enable it. You can 1536 1.1 mrg optionally control which decimal floating point format is used (either 1537 1.10 mrg ‘<samp>bid</samp>’ or ‘<samp>dpd</samp>’). The ‘<samp>bid</samp>’ (binary integer decimal) 1538 1.10 mrg format is default on i386 and x86_64 systems, and the ‘<samp>dpd</samp>’ 1539 1.1 mrg (densely packed decimal) format is default on PowerPC systems. 1540 1.10 mrg </p> 1541 1.10 mrg </dd> 1542 1.14 mrg <dt><span><code>--enable-fixed-point</code></span></dt> 1543 1.14 mrg <dt><span><code>--disable-fixed-point</code></span></dt> 1544 1.10 mrg <dd><p>Enable (or disable) support for C fixed-point arithmetic. 1545 1.1 mrg This option is enabled by default for some targets (such as MIPS) which 1546 1.1 mrg have hardware-support for fixed-point operations. On other targets, you 1547 1.1 mrg may enable this option manually. 1548 1.10 mrg </p> 1549 1.10 mrg </dd> 1550 1.14 mrg <dt><span><code>--with-long-double-128</code></span></dt> 1551 1.10 mrg <dd><p>Specify if <code>long double</code> type should be 128-bit by default on selected 1552 1.1 mrg GNU/Linux architectures. If using <code>--without-long-double-128</code>, 1553 1.10 mrg <code>long double</code> will be by default 64-bit, the same as <code>double</code> type. 1554 1.1 mrg When neither of these configure options are used, the default will be 1555 1.1 mrg 128-bit <code>long double</code> when built against GNU C Library 2.4 and later, 1556 1.1 mrg 64-bit <code>long double</code> otherwise. 1557 1.10 mrg </p> 1558 1.10 mrg </dd> 1559 1.14 mrg <dt><span><code>--with-long-double-format=ibm</code></span></dt> 1560 1.14 mrg <dt><span><code>--with-long-double-format=ieee</code></span></dt> 1561 1.10 mrg <dd><p>Specify whether <code>long double</code> uses the IBM extended double format 1562 1.10 mrg or the IEEE 128-bit floating point format on PowerPC Linux systems. 1563 1.10 mrg This configuration switch will only work on little endian PowerPC 1564 1.10 mrg Linux systems and on big endian 64-bit systems where the default cpu 1565 1.10 mrg is at least power7 (i.e. <samp>--with-cpu=power7</samp>, 1566 1.10 mrg <samp>--with-cpu=power8</samp>, or <samp>--with-cpu=power9</samp> is used). 1567 1.10 mrg </p> 1568 1.10 mrg <p>If you use the <samp>--with-long-double-64</samp> configuration option, 1569 1.10 mrg the <samp>--with-long-double-format=ibm</samp> and 1570 1.10 mrg <samp>--with-long-double-format=ieee</samp> options are ignored. 1571 1.10 mrg </p> 1572 1.10 mrg <p>The default <code>long double</code> format is to use IBM extended double. 1573 1.10 mrg Until all of the libraries are converted to use IEEE 128-bit floating 1574 1.10 mrg point, it is not recommended to use 1575 1.10 mrg <samp>--with-long-double-format=ieee</samp>. 1576 1.10 mrg </p> 1577 1.10 mrg <p>On little endian PowerPC Linux systems, if you explicitly set the 1578 1.10 mrg <code>long double</code> type, it will build multilibs to allow you to 1579 1.10 mrg select either <code>long double</code> format, unless you disable multilibs 1580 1.10 mrg with the <code>--disable-multilib</code> option. At present, 1581 1.10 mrg <code>long double</code> multilibs are not built on big endian PowerPC Linux 1582 1.10 mrg systems. If you are building multilibs, you will need to configure 1583 1.10 mrg the compiler using the <samp>--with-system-zlib</samp> option. 1584 1.10 mrg </p> 1585 1.10 mrg <p>If you do not set the <code>long double</code> type explicitly, no multilibs 1586 1.10 mrg will be generated. 1587 1.10 mrg </p> 1588 1.10 mrg </dd> 1589 1.14 mrg <dt><span><code>--enable-fdpic</code></span></dt> 1590 1.10 mrg <dd><p>On SH Linux systems, generate ELF FDPIC code. 1591 1.10 mrg </p> 1592 1.10 mrg </dd> 1593 1.14 mrg <dt><span><code>--with-gmp=<var>pathname</var></code></span></dt> 1594 1.14 mrg <dt><span><code>--with-gmp-include=<var>pathname</var></code></span></dt> 1595 1.14 mrg <dt><span><code>--with-gmp-lib=<var>pathname</var></code></span></dt> 1596 1.14 mrg <dt><span><code>--with-mpfr=<var>pathname</var></code></span></dt> 1597 1.14 mrg <dt><span><code>--with-mpfr-include=<var>pathname</var></code></span></dt> 1598 1.14 mrg <dt><span><code>--with-mpfr-lib=<var>pathname</var></code></span></dt> 1599 1.14 mrg <dt><span><code>--with-mpc=<var>pathname</var></code></span></dt> 1600 1.14 mrg <dt><span><code>--with-mpc-include=<var>pathname</var></code></span></dt> 1601 1.14 mrg <dt><span><code>--with-mpc-lib=<var>pathname</var></code></span></dt> 1602 1.10 mrg <dd><p>If you want to build GCC but do not have the GMP library, the MPFR 1603 1.1 mrg library and/or the MPC library installed in a standard location and 1604 1.3 skrll do not have their sources present in the GCC source tree then you 1605 1.3 skrll can explicitly specify the directory where they are installed 1606 1.10 mrg (‘<samp>--with-gmp=<var>gmpinstalldir</var></samp>’, 1607 1.10 mrg ‘<samp>--with-mpfr=<var>mpfrinstalldir</var></samp>’, 1608 1.10 mrg ‘<samp>--with-mpc=<var>mpcinstalldir</var></samp>’). The 1609 1.10 mrg <samp>--with-gmp=<var>gmpinstalldir</var></samp> option is shorthand for 1610 1.10 mrg <samp>--with-gmp-lib=<var>gmpinstalldir</var>/lib</samp> and 1611 1.10 mrg <samp>--with-gmp-include=<var>gmpinstalldir</var>/include</samp>. Likewise the 1612 1.10 mrg <samp>--with-mpfr=<var>mpfrinstalldir</var></samp> option is shorthand for 1613 1.10 mrg <samp>--with-mpfr-lib=<var>mpfrinstalldir</var>/lib</samp> and 1614 1.10 mrg <samp>--with-mpfr-include=<var>mpfrinstalldir</var>/include</samp>, also the 1615 1.10 mrg <samp>--with-mpc=<var>mpcinstalldir</var></samp> option is shorthand for 1616 1.10 mrg <samp>--with-mpc-lib=<var>mpcinstalldir</var>/lib</samp> and 1617 1.10 mrg <samp>--with-mpc-include=<var>mpcinstalldir</var>/include</samp>. If these 1618 1.1 mrg shorthand assumptions are not correct, you can use the explicit 1619 1.3 skrll include and lib options directly. You might also need to ensure the 1620 1.3 skrll shared libraries can be found by the dynamic linker when building and 1621 1.3 skrll using GCC, for example by setting the runtime shared library path 1622 1.10 mrg variable (<code>LD_LIBRARY_PATH</code> on GNU/Linux and Solaris systems). 1623 1.10 mrg </p> 1624 1.10 mrg <p>These flags are applicable to the host platform only. When building 1625 1.3 skrll a cross compiler, they will not be used to configure target libraries. 1626 1.10 mrg </p> 1627 1.10 mrg </dd> 1628 1.14 mrg <dt><span><code>--with-isl=<var>pathname</var></code></span></dt> 1629 1.14 mrg <dt><span><code>--with-isl-include=<var>pathname</var></code></span></dt> 1630 1.14 mrg <dt><span><code>--with-isl-lib=<var>pathname</var></code></span></dt> 1631 1.10 mrg <dd><p>If you do not have the isl library installed in a standard location and you 1632 1.5 mrg want to build GCC, you can explicitly specify the directory where it is 1633 1.10 mrg installed (‘<samp>--with-isl=<var>islinstalldir</var></samp>’). The 1634 1.10 mrg <samp>--with-isl=<var>islinstalldir</var></samp> option is shorthand for 1635 1.10 mrg <samp>--with-isl-lib=<var>islinstalldir</var>/lib</samp> and 1636 1.10 mrg <samp>--with-isl-include=<var>islinstalldir</var>/include</samp>. If this 1637 1.5 mrg shorthand assumption is not correct, you can use the explicit 1638 1.1 mrg include and lib options directly. 1639 1.10 mrg </p> 1640 1.10 mrg <p>These flags are applicable to the host platform only. When building 1641 1.3 skrll a cross compiler, they will not be used to configure target libraries. 1642 1.10 mrg </p> 1643 1.10 mrg </dd> 1644 1.14 mrg <dt><span><code>--with-stage1-ldflags=<var>flags</var></code></span></dt> 1645 1.10 mrg <dd><p>This option may be used to set linker flags to be used when linking 1646 1.1 mrg stage 1 of GCC. These are also used when linking GCC if configured with 1647 1.10 mrg <samp>--disable-bootstrap</samp>. If <samp>--with-stage1-libs</samp> is not set to a 1648 1.10 mrg value, then the default is ‘<samp>-static-libstdc++ -static-libgcc</samp>’, if 1649 1.7 mrg supported. 1650 1.10 mrg </p> 1651 1.10 mrg </dd> 1652 1.14 mrg <dt><span><code>--with-stage1-libs=<var>libs</var></code></span></dt> 1653 1.10 mrg <dd><p>This option may be used to set libraries to be used when linking stage 1 1654 1.1 mrg of GCC. These are also used when linking GCC if configured with 1655 1.10 mrg <samp>--disable-bootstrap</samp>. 1656 1.10 mrg </p> 1657 1.10 mrg </dd> 1658 1.14 mrg <dt><span><code>--with-boot-ldflags=<var>flags</var></code></span></dt> 1659 1.10 mrg <dd><p>This option may be used to set linker flags to be used when linking 1660 1.7 mrg stage 2 and later when bootstrapping GCC. If –with-boot-libs 1661 1.7 mrg is not is set to a value, then the default is 1662 1.10 mrg ‘<samp>-static-libstdc++ -static-libgcc</samp>’. 1663 1.10 mrg </p> 1664 1.10 mrg </dd> 1665 1.14 mrg <dt><span><code>--with-boot-libs=<var>libs</var></code></span></dt> 1666 1.10 mrg <dd><p>This option may be used to set libraries to be used when linking stage 2 1667 1.7 mrg and later when bootstrapping GCC. 1668 1.10 mrg </p> 1669 1.10 mrg </dd> 1670 1.14 mrg <dt><span><code>--with-debug-prefix-map=<var>map</var></code></span></dt> 1671 1.10 mrg <dd><p>Convert source directory names using <samp>-fdebug-prefix-map</samp> when 1672 1.1 mrg building runtime libraries. ‘<samp><var>map</var></samp>’ is a space-separated 1673 1.10 mrg list of maps of the form ‘<samp><var>old</var>=<var>new</var></samp>’. 1674 1.10 mrg </p> 1675 1.10 mrg </dd> 1676 1.14 mrg <dt><span><code>--enable-linker-build-id</code></span></dt> 1677 1.10 mrg <dd><p>Tells GCC to pass <samp>--build-id</samp> option to the linker for all final 1678 1.10 mrg links (links performed without the <samp>-r</samp> or <samp>--relocatable</samp> 1679 1.1 mrg option), if the linker supports it. If you specify 1680 1.10 mrg <samp>--enable-linker-build-id</samp>, but your linker does not 1681 1.10 mrg support <samp>--build-id</samp> option, a warning is issued and the 1682 1.10 mrg <samp>--enable-linker-build-id</samp> option is ignored. The default is off. 1683 1.10 mrg </p> 1684 1.10 mrg </dd> 1685 1.14 mrg <dt><span><code>--with-linker-hash-style=<var>choice</var></code></span></dt> 1686 1.10 mrg <dd><p>Tells GCC to pass <samp>--hash-style=<var>choice</var></samp> option to the 1687 1.3 skrll linker for all final links. <var>choice</var> can be one of 1688 1.10 mrg ‘<samp>sysv</samp>’, ‘<samp>gnu</samp>’, and ‘<samp>both</samp>’ where ‘<samp>sysv</samp>’ is the default. 1689 1.10 mrg </p> 1690 1.10 mrg </dd> 1691 1.14 mrg <dt><span><code>--enable-gnu-unique-object</code></span></dt> 1692 1.14 mrg <dt><span><code>--disable-gnu-unique-object</code></span></dt> 1693 1.10 mrg <dd><p>Tells GCC to use the gnu_unique_object relocation for C++ template 1694 1.1 mrg static data members and inline function local statics. Enabled by 1695 1.5 mrg default for a toolchain with an assembler that accepts it and 1696 1.1 mrg GLIBC 2.11 or above, otherwise disabled. 1697 1.10 mrg </p> 1698 1.10 mrg </dd> 1699 1.14 mrg <dt><span><code>--with-diagnostics-color=<var>choice</var></code></span></dt> 1700 1.10 mrg <dd><p>Tells GCC to use <var>choice</var> as the default for <samp>-fdiagnostics-color=</samp> 1701 1.5 mrg option (if not used explicitly on the command line). <var>choice</var> 1702 1.10 mrg can be one of ‘<samp>never</samp>’, ‘<samp>auto</samp>’, ‘<samp>always</samp>’, and ‘<samp>auto-if-env</samp>’ 1703 1.13 mrg where ‘<samp>auto</samp>’ is the default. ‘<samp>auto-if-env</samp>’ makes 1704 1.13 mrg <samp>-fdiagnostics-color=auto</samp> the default if <code>GCC_COLORS</code> 1705 1.13 mrg is present and non-empty in the environment of the compiler, and 1706 1.10 mrg <samp>-fdiagnostics-color=never</samp> otherwise. 1707 1.10 mrg </p> 1708 1.10 mrg </dd> 1709 1.14 mrg <dt><span><code>--with-diagnostics-urls=<var>choice</var></code></span></dt> 1710 1.13 mrg <dd><p>Tells GCC to use <var>choice</var> as the default for <samp>-fdiagnostics-urls=</samp> 1711 1.13 mrg option (if not used explicitly on the command line). <var>choice</var> 1712 1.13 mrg can be one of ‘<samp>never</samp>’, ‘<samp>auto</samp>’, ‘<samp>always</samp>’, and ‘<samp>auto-if-env</samp>’ 1713 1.13 mrg where ‘<samp>auto</samp>’ is the default. ‘<samp>auto-if-env</samp>’ makes 1714 1.13 mrg <samp>-fdiagnostics-urls=auto</samp> the default if <code>GCC_URLS</code> 1715 1.13 mrg or <code>TERM_URLS</code> is present and non-empty in the environment of the 1716 1.13 mrg compiler, and <samp>-fdiagnostics-urls=never</samp> otherwise. 1717 1.13 mrg </p> 1718 1.13 mrg </dd> 1719 1.14 mrg <dt><span><code>--enable-lto</code></span></dt> 1720 1.14 mrg <dt><span><code>--disable-lto</code></span></dt> 1721 1.10 mrg <dd><p>Enable support for link-time optimization (LTO). This is enabled by 1722 1.10 mrg default, and may be disabled using <samp>--disable-lto</samp>. 1723 1.10 mrg </p> 1724 1.10 mrg </dd> 1725 1.14 mrg <dt><span><code>--enable-linker-plugin-configure-flags=FLAGS</code></span></dt> 1726 1.14 mrg <dt><span><code>--enable-linker-plugin-flags=FLAGS</code></span></dt> 1727 1.10 mrg <dd><p>By default, linker plugins (such as the LTO plugin) are built for the 1728 1.5 mrg host system architecture. For the case that the linker has a 1729 1.5 mrg different (but run-time compatible) architecture, these flags can be 1730 1.5 mrg specified to build plugins that are compatible to the linker. For 1731 1.5 mrg example, if you are building GCC for a 64-bit x86_64 1732 1.12 mrg (‘<samp>x86_64-pc-linux-gnu</samp>’) host system, but have a 32-bit x86 1733 1.10 mrg GNU/Linux (‘<samp>i686-pc-linux-gnu</samp>’) linker executable (which is 1734 1.5 mrg executable on the former system), you can configure GCC as follows for 1735 1.5 mrg getting compatible linker plugins: 1736 1.10 mrg </p> 1737 1.14 mrg <div class="example"> 1738 1.14 mrg <pre class="example">% <var>srcdir</var>/configure \ 1739 1.12 mrg --host=x86_64-pc-linux-gnu \ 1740 1.10 mrg --enable-linker-plugin-configure-flags=--host=i686-pc-linux-gnu \ 1741 1.10 mrg --enable-linker-plugin-flags='CC=gcc\ -m32\ -Wl,-rpath,[...]/i686-pc-linux-gnu/lib' 1742 1.10 mrg </pre></div> 1743 1.10 mrg 1744 1.10 mrg </dd> 1745 1.14 mrg <dt><span><code>--with-plugin-ld=<var>pathname</var></code></span></dt> 1746 1.10 mrg <dd><p>Enable an alternate linker to be used at link-time optimization (LTO) 1747 1.10 mrg link time when <samp>-fuse-linker-plugin</samp> is enabled. 1748 1.3 skrll This linker should have plugin support such as gold starting with 1749 1.10 mrg version 2.20 or GNU ld starting with version 2.21. 1750 1.10 mrg See <samp>-fuse-linker-plugin</samp> for details. 1751 1.10 mrg </p> 1752 1.10 mrg </dd> 1753 1.14 mrg <dt><span><code>--enable-canonical-system-headers</code></span></dt> 1754 1.14 mrg <dt><span><code>--disable-canonical-system-headers</code></span></dt> 1755 1.10 mrg <dd><p>Enable system header path canonicalization for <samp>libcpp</samp>. This can 1756 1.3 skrll produce shorter header file paths in diagnostics and dependency output 1757 1.3 skrll files, but these changed header paths may conflict with some compilation 1758 1.3 skrll environments. Enabled by default, and may be disabled using 1759 1.10 mrg <samp>--disable-canonical-system-headers</samp>. 1760 1.10 mrg </p> 1761 1.10 mrg </dd> 1762 1.14 mrg <dt><span><code>--with-glibc-version=<var>major</var>.<var>minor</var></code></span></dt> 1763 1.10 mrg <dd><p>Tell GCC that when the GNU C Library (glibc) is used on the target it 1764 1.5 mrg will be version <var>major</var>.<var>minor</var> or later. Normally this can 1765 1.10 mrg be detected from the C library’s header files, but this option may be 1766 1.5 mrg needed when bootstrapping a cross toolchain without the header files 1767 1.5 mrg available for building the initial bootstrap compiler. 1768 1.10 mrg </p> 1769 1.10 mrg <p>If GCC is configured with some multilibs that use glibc and some that 1770 1.10 mrg do not, this option applies only to the multilibs that use glibc. 1771 1.5 mrg However, such configurations may not work well as not all the relevant 1772 1.5 mrg configuration in GCC is on a per-multilib basis. 1773 1.10 mrg </p> 1774 1.10 mrg </dd> 1775 1.14 mrg <dt><span><code>--enable-as-accelerator-for=<var>target</var></code></span></dt> 1776 1.10 mrg <dd><p>Build as offload target compiler. Specify offload host triple by <var>target</var>. 1777 1.10 mrg </p> 1778 1.10 mrg </dd> 1779 1.14 mrg <dt><span><code>--enable-offload-targets=<var>target1</var>[=<var>path1</var>],…,<var>targetN</var>[=<var>pathN</var>]</code></span></dt> 1780 1.10 mrg <dd><p>Enable offloading to targets <var>target1</var>, …, <var>targetN</var>. 1781 1.5 mrg Offload compilers are expected to be already installed. Default search 1782 1.5 mrg path for them is <samp><var>exec-prefix</var></samp>, but it can be changed by 1783 1.10 mrg specifying paths <var>path1</var>, …, <var>pathN</var>. 1784 1.10 mrg </p> 1785 1.14 mrg <div class="example"> 1786 1.14 mrg <pre class="example">% <var>srcdir</var>/configure \ 1787 1.12 mrg --enable-offload-targets=x86_64-intelmicemul-linux-gnu=/path/to/x86_64/compiler,nvptx-none,hsa 1788 1.10 mrg </pre></div> 1789 1.7 mrg 1790 1.10 mrg <p>If ‘<samp>hsa</samp>’ is specified as one of the targets, the compiler will be 1791 1.7 mrg built with support for HSA GPU accelerators. Because the same 1792 1.7 mrg compiler will emit the accelerator code, no path should be specified. 1793 1.10 mrg </p> 1794 1.10 mrg </dd> 1795 1.14 mrg <dt><span><code>--with-hsa-runtime=<var>pathname</var></code></span></dt> 1796 1.14 mrg <dt><span><code>--with-hsa-runtime-include=<var>pathname</var></code></span></dt> 1797 1.14 mrg <dt><span><code>--with-hsa-runtime-lib=<var>pathname</var></code></span></dt> 1798 1.10 mrg <dd> 1799 1.10 mrg <p>If you configure GCC with HSA offloading but do not have the HSA 1800 1.7 mrg run-time library installed in a standard location then you can 1801 1.7 mrg explicitly specify the directory where they are installed. The 1802 1.10 mrg <samp>--with-hsa-runtime=<var>hsainstalldir</var></samp> option is a 1803 1.7 mrg shorthand for 1804 1.10 mrg <samp>--with-hsa-runtime-lib=<var>hsainstalldir</var>/lib</samp> and 1805 1.10 mrg <samp>--with-hsa-runtime-include=<var>hsainstalldir</var>/include</samp>. 1806 1.10 mrg </p> 1807 1.10 mrg </dd> 1808 1.14 mrg <dt><span><code>--enable-cet</code></span></dt> 1809 1.14 mrg <dt><span><code>--disable-cet</code></span></dt> 1810 1.10 mrg <dd><p>Enable building target run-time libraries with control-flow 1811 1.10 mrg instrumentation, see <samp>-fcf-protection</samp> option. When 1812 1.10 mrg <code>--enable-cet</code> is specified target libraries are configured 1813 1.10 mrg to add <samp>-fcf-protection</samp> and, if needed, other target 1814 1.10 mrg specific options to a set of building options. 1815 1.10 mrg </p> 1816 1.10 mrg <p>The option is disabled by default. When <code>--enable-cet=auto</code> 1817 1.10 mrg is used, it is enabled on Linux/x86 if target binutils 1818 1.10 mrg supports <code>Intel CET</code> instructions and disabled otherwise. 1819 1.10 mrg In this case the target libraries are configured to get additional 1820 1.10 mrg <samp>-fcf-protection</samp> option. 1821 1.12 mrg </p> 1822 1.12 mrg </dd> 1823 1.14 mrg <dt><span><code>--with-riscv-attribute=‘<samp>yes</samp>’, ‘<samp>no</samp>’ or ‘<samp>default</samp>’</code></span></dt> 1824 1.12 mrg <dd><p>Generate RISC-V attribute by default, in order to record extra build 1825 1.12 mrg information in object. 1826 1.12 mrg </p> 1827 1.12 mrg <p>The option is disabled by default. It is enabled on RISC-V/ELF (bare-metal) 1828 1.12 mrg target if target binutils supported. 1829 1.10 mrg </p></dd> 1830 1.6 mrg </dl> 1831 1.1 mrg 1832 1.14 mrg <span id="Cross-Compiler-Specific-Options"></span><h4 class="subheading">Cross-Compiler-Specific Options</h4> 1833 1.1 mrg <p>The following options only apply to building cross compilers. 1834 1.10 mrg </p> 1835 1.10 mrg <dl compact="compact"> 1836 1.14 mrg <dt><span><code>--with-toolexeclibdir=<var>dir</var></code></span></dt> 1837 1.13 mrg <dd><p>Specify the installation directory for libraries built with a cross compiler. 1838 1.13 mrg The default is <samp>${gcc_tooldir}/lib</samp>. 1839 1.13 mrg </p> 1840 1.13 mrg </dd> 1841 1.14 mrg <dt><span><code>--with-sysroot</code></span></dt> 1842 1.14 mrg <dt><span><code>--with-sysroot=<var>dir</var></code></span></dt> 1843 1.10 mrg <dd><p>Tells GCC to consider <var>dir</var> as the root of a tree that contains 1844 1.10 mrg (a subset of) the root filesystem of the target operating system. 1845 1.1 mrg Target system headers, libraries and run-time object files will be 1846 1.3 skrll searched for in there. More specifically, this acts as if 1847 1.10 mrg <samp>--sysroot=<var>dir</var></samp> was added to the default options of the built 1848 1.1 mrg compiler. The specified directory is not copied into the 1849 1.10 mrg install tree, unlike the options <samp>--with-headers</samp> and 1850 1.10 mrg <samp>--with-libs</samp> that this option obsoletes. The default value, 1851 1.10 mrg in case <samp>--with-sysroot</samp> is not given an argument, is 1852 1.10 mrg <samp>${gcc_tooldir}/sys-root</samp>. If the specified directory is a 1853 1.10 mrg subdirectory of <samp>${exec_prefix}</samp>, then it will be found relative to 1854 1.1 mrg the GCC binaries if the installation tree is moved. 1855 1.10 mrg </p> 1856 1.10 mrg <p>This option affects the system root for the compiler used to build 1857 1.1 mrg target libraries (which runs on the build system) and the compiler newly 1858 1.1 mrg installed with <code>make install</code>; it does not affect the compiler which is 1859 1.1 mrg used to build GCC itself. 1860 1.10 mrg </p> 1861 1.10 mrg <p>If you specify the <samp>--with-native-system-header-dir=<var>dirname</var></samp> 1862 1.3 skrll option then the compiler will search that directory within <var>dirname</var> for 1863 1.10 mrg native system headers rather than the default <samp>/usr/include</samp>. 1864 1.10 mrg </p> 1865 1.10 mrg </dd> 1866 1.14 mrg <dt><span><code>--with-build-sysroot</code></span></dt> 1867 1.14 mrg <dt><span><code>--with-build-sysroot=<var>dir</var></code></span></dt> 1868 1.10 mrg <dd><p>Tells GCC to consider <var>dir</var> as the system root (see 1869 1.10 mrg <samp>--with-sysroot</samp>) while building target libraries, instead of 1870 1.10 mrg the directory specified with <samp>--with-sysroot</samp>. This option is 1871 1.10 mrg only useful when you are already using <samp>--with-sysroot</samp>. You 1872 1.10 mrg can use <samp>--with-build-sysroot</samp> when you are configuring with 1873 1.10 mrg <samp>--prefix</samp> set to a directory that is different from the one in 1874 1.1 mrg which you are installing GCC and your target libraries. 1875 1.10 mrg </p> 1876 1.10 mrg <p>This option affects the system root for the compiler used to build 1877 1.1 mrg target libraries (which runs on the build system); it does not affect 1878 1.1 mrg the compiler which is used to build GCC itself. 1879 1.10 mrg </p> 1880 1.10 mrg <p>If you specify the <samp>--with-native-system-header-dir=<var>dirname</var></samp> 1881 1.3 skrll option then the compiler will search that directory within <var>dirname</var> for 1882 1.10 mrg native system headers rather than the default <samp>/usr/include</samp>. 1883 1.10 mrg </p> 1884 1.10 mrg </dd> 1885 1.14 mrg <dt><span><code>--with-headers</code></span></dt> 1886 1.14 mrg <dt><span><code>--with-headers=<var>dir</var></code></span></dt> 1887 1.10 mrg <dd><p>Deprecated in favor of <samp>--with-sysroot</samp>. 1888 1.10 mrg Specifies that target headers are available when building a cross compiler. 1889 1.1 mrg The <var>dir</var> argument specifies a directory which has the target include 1890 1.10 mrg files. These include files will be copied into the <samp>gcc</samp> install 1891 1.10 mrg directory. <em>This option with the <var>dir</var> argument is required</em> when 1892 1.10 mrg building a cross compiler, if <samp><var>prefix</var>/<var>target</var>/sys-include</samp> 1893 1.10 mrg doesn’t pre-exist. If <samp><var>prefix</var>/<var>target</var>/sys-include</samp> does 1894 1.10 mrg pre-exist, the <var>dir</var> argument may be omitted. <code>fixincludes</code> 1895 1.1 mrg will be run on these files to make them compatible with GCC. 1896 1.10 mrg </p> 1897 1.10 mrg </dd> 1898 1.14 mrg <dt><span><code>--without-headers</code></span></dt> 1899 1.10 mrg <dd><p>Tells GCC not use any target headers from a libc when building a cross 1900 1.1 mrg compiler. When crossing to GNU/Linux, you need the headers so GCC 1901 1.1 mrg can build the exception handling for libgcc. 1902 1.10 mrg </p> 1903 1.10 mrg </dd> 1904 1.14 mrg <dt><span><code>--with-libs</code></span></dt> 1905 1.14 mrg <dt><span><code>--with-libs="<var>dir1</var> <var>dir2</var> … <var>dirN</var>"</code></span></dt> 1906 1.10 mrg <dd><p>Deprecated in favor of <samp>--with-sysroot</samp>. 1907 1.1 mrg Specifies a list of directories which contain the target runtime 1908 1.10 mrg libraries. These libraries will be copied into the <samp>gcc</samp> install 1909 1.1 mrg directory. If the directory list is omitted, this option has no 1910 1.1 mrg effect. 1911 1.10 mrg </p> 1912 1.10 mrg </dd> 1913 1.14 mrg <dt><span><code>--with-newlib</code></span></dt> 1914 1.10 mrg <dd><p>Specifies that ‘<samp>newlib</samp>’ is 1915 1.1 mrg being used as the target C library. This causes <code>__eprintf</code> to be 1916 1.10 mrg omitted from <samp>libgcc.a</samp> on the assumption that it will be provided by 1917 1.10 mrg ‘<samp>newlib</samp>’. 1918 1.10 mrg </p> 1919 1.13 mrg <a name="avr"></a> 1920 1.10 mrg </dd> 1921 1.14 mrg <dt><span><code>--with-avrlibc</code></span></dt> 1922 1.13 mrg <dd><p>Only supported for the AVR target. Specifies that ‘<samp>AVR-Libc</samp>’ is 1923 1.13 mrg being used as the target C library. This causes float support 1924 1.10 mrg functions like <code>__addsf3</code> to be omitted from <samp>libgcc.a</samp> on 1925 1.10 mrg the assumption that it will be provided by <samp>libm.a</samp>. For more 1926 1.10 mrg technical details, cf. <a href="http://gcc.gnu.org/PR54461">PR54461</a>. 1927 1.13 mrg It is not supported for 1928 1.3 skrll RTEMS configurations, which currently use newlib. The option is 1929 1.3 skrll supported since version 4.7.2 and is the default in 4.8.0 and newer. 1930 1.10 mrg </p> 1931 1.10 mrg </dd> 1932 1.14 mrg <dt><span><code>--with-double={32|64|32,64|64,32}</code></span></dt> 1933 1.14 mrg <dt><span><code>--with-long-double={32|64|32,64|64,32|double}</code></span></dt> 1934 1.13 mrg <dd><p>Only supported for the AVR target since version 10. 1935 1.13 mrg Specify the default layout available for the C/C++ ‘<samp>double</samp>’ 1936 1.13 mrg and ‘<samp>long double</samp>’ type, respectively. The following rules apply: 1937 1.13 mrg </p><ul> 1938 1.13 mrg <li> The first value after the ‘<samp>=</samp>’ specifies the default layout (in bits) 1939 1.13 mrg of the type and also the default for the <samp>-mdouble=</samp> resp. 1940 1.13 mrg <samp>-mlong-double=</samp> compiler option. 1941 1.13 mrg </li><li> If more than one value is specified, respective multilib variants are 1942 1.13 mrg available, and <samp>-mdouble=</samp> resp. <samp>-mlong-double=</samp> acts 1943 1.13 mrg as a multilib option. 1944 1.13 mrg </li><li> If <samp>--with-long-double=double</samp> is specified, ‘<samp>double</samp>’ and 1945 1.13 mrg ‘<samp>long double</samp>’ will have the same layout. 1946 1.13 mrg </li><li> The defaults are <samp>--with-long-double=64,32</samp> and 1947 1.13 mrg <samp>--with-double=32,64</samp>. The default ‘<samp>double</samp>’ layout imposed by 1948 1.13 mrg the latter is compatible with older versions of the compiler that implement 1949 1.13 mrg ‘<samp>double</samp>’ as a 32-bit type, which does not comply to the language standard. 1950 1.13 mrg </li></ul> 1951 1.13 mrg <p>Not all combinations of <samp>--with-double=</samp> and 1952 1.13 mrg <samp>--with-long-double=</samp> are valid. For example, the combination 1953 1.13 mrg <samp>--with-double=32,64</samp> <samp>--with-long-double=32</samp> will be 1954 1.13 mrg rejected because the first option specifies the availability of 1955 1.13 mrg multilibs for ‘<samp>double</samp>’, whereas the second option implies 1956 1.13 mrg that ‘<samp>long double</samp>’ — and hence also ‘<samp>double</samp>’ — is always 1957 1.13 mrg 32 bits wide. 1958 1.13 mrg </p> 1959 1.13 mrg </dd> 1960 1.14 mrg <dt><span><code>--with-double-comparison={tristate|bool|libf7}</code></span></dt> 1961 1.13 mrg <dd><p>Only supported for the AVR target since version 10. 1962 1.13 mrg Specify what result format is returned by library functions that 1963 1.13 mrg compare 64-bit floating point values (<code>DFmode</code>). 1964 1.13 mrg The GCC default is ‘<samp>tristate</samp>’. If the floating point 1965 1.13 mrg implementation returns a boolean instead, set it to ‘<samp>bool</samp>’. 1966 1.13 mrg </p> 1967 1.13 mrg </dd> 1968 1.14 mrg <dt><span><code>--with-libf7={libgcc|math|math-symbols|no}</code></span></dt> 1969 1.13 mrg <dd><p>Only supported for the AVR target since version 10. 1970 1.13 mrg Specify to which degree code from LibF7 is included in libgcc. 1971 1.13 mrg LibF7 is an ad-hoc, AVR-specific, 64-bit floating point emulation 1972 1.13 mrg written in C and (inline) assembly. ‘<samp>libgcc</samp>’ adds support 1973 1.13 mrg for functions that one would usually expect in libgcc like double addition, 1974 1.13 mrg double comparisons and double conversions. ‘<samp>math</samp>’ also adds routines 1975 1.13 mrg that one would expect in <samp>libm.a</samp>, but with <code>__</code> (two underscores) 1976 1.13 mrg prepended to the symbol names as specified by <samp>math.h</samp>. 1977 1.13 mrg ‘<samp>math-symbols</samp>’ also defines weak aliases for the functions 1978 1.13 mrg declared in <samp>math.h</samp>. However, <code>--with-libf7</code> won’t 1979 1.13 mrg install no <samp>math.h</samp> header file whatsoever, this file must come 1980 1.13 mrg from elsewhere. This option sets <samp>--with-double-comparison</samp> 1981 1.13 mrg to ‘<samp>bool</samp>’. 1982 1.13 mrg </p> 1983 1.13 mrg </dd> 1984 1.14 mrg <dt><span><code>--with-nds32-lib=<var>library</var></code></span></dt> 1985 1.10 mrg <dd><p>Specifies that <var>library</var> setting is used for building <samp>libgcc.a</samp>. 1986 1.10 mrg Currently, the valid <var>library</var> is ‘<samp>newlib</samp>’ or ‘<samp>mculib</samp>’. 1987 1.5 mrg This option is only supported for the NDS32 target. 1988 1.10 mrg </p> 1989 1.10 mrg </dd> 1990 1.14 mrg <dt><span><code>--with-build-time-tools=<var>dir</var></code></span></dt> 1991 1.10 mrg <dd><p>Specifies where to find the set of target tools (assembler, linker, etc.) 1992 1.1 mrg that will be used while building GCC itself. This option can be useful 1993 1.1 mrg if the directory layouts are different between the system you are building 1994 1.1 mrg GCC on, and the system where you will deploy it. 1995 1.10 mrg </p> 1996 1.10 mrg <p>For example, on an ‘<samp>ia64-hp-hpux</samp>’ system, you may have the GNU 1997 1.10 mrg assembler and linker in <samp>/usr/bin</samp>, and the native tools in a 1998 1.6 mrg different path, and build a toolchain that expects to find the 1999 1.10 mrg native tools in <samp>/usr/bin</samp>. 2000 1.10 mrg </p> 2001 1.10 mrg <p>When you use this option, you should ensure that <var>dir</var> includes 2002 1.10 mrg <code>ar</code>, <code>as</code>, <code>ld</code>, <code>nm</code>, 2003 1.10 mrg <code>ranlib</code> and <code>strip</code> if necessary, and possibly 2004 1.10 mrg <code>objdump</code>. Otherwise, GCC may use an inconsistent set of 2005 1.10 mrg tools. 2006 1.10 mrg </p></dd> 2007 1.6 mrg </dl> 2008 1.1 mrg 2009 1.14 mrg <span id="Overriding-configure-test-results"></span><h4 class="subsubheading">Overriding <code>configure</code> test results</h4> 2010 1.1 mrg 2011 1.6 mrg <p>Sometimes, it might be necessary to override the result of some 2012 1.10 mrg <code>configure</code> test, for example in order to ease porting to a new 2013 1.10 mrg system or work around a bug in a test. The toplevel <code>configure</code> 2014 1.6 mrg script provides three variables for this: 2015 1.10 mrg </p> 2016 1.10 mrg <dl compact="compact"> 2017 1.14 mrg <dt id='index-build_005fconfigargs'><span><code>build_configargs</code><a href='#index-build_005fconfigargs' class='copiable-anchor'> ¶</a></span></dt> 2018 1.14 mrg <dd><p>The contents of this variable is passed to all build <code>configure</code> 2019 1.6 mrg scripts. 2020 1.10 mrg </p> 2021 1.10 mrg </dd> 2022 1.14 mrg <dt id='index-host_005fconfigargs'><span><code>host_configargs</code><a href='#index-host_005fconfigargs' class='copiable-anchor'> ¶</a></span></dt> 2023 1.14 mrg <dd><p>The contents of this variable is passed to all host <code>configure</code> 2024 1.6 mrg scripts. 2025 1.10 mrg </p> 2026 1.10 mrg </dd> 2027 1.14 mrg <dt id='index-target_005fconfigargs'><span><code>target_configargs</code><a href='#index-target_005fconfigargs' class='copiable-anchor'> ¶</a></span></dt> 2028 1.14 mrg <dd><p>The contents of this variable is passed to all target <code>configure</code> 2029 1.6 mrg scripts. 2030 1.10 mrg </p> 2031 1.10 mrg </dd> 2032 1.10 mrg </dl> 2033 1.1 mrg 2034 1.10 mrg <p>In order to avoid shell and <code>make</code> quoting issues for complex 2035 1.10 mrg overrides, you can pass a setting for <code>CONFIG_SITE</code> and set 2036 1.6 mrg variables in the site file. 2037 1.10 mrg </p> 2038 1.14 mrg <span id="Objective-C-Specific-Options"></span><h4 class="subheading">Objective-C-Specific Options</h4> 2039 1.7 mrg 2040 1.9 mrg <p>The following options apply to the build of the Objective-C runtime library. 2041 1.10 mrg </p> 2042 1.10 mrg <dl compact="compact"> 2043 1.14 mrg <dt><span><code>--enable-objc-gc</code></span></dt> 2044 1.10 mrg <dd><p>Specify that an additional variant of the GNU Objective-C runtime library 2045 1.9 mrg is built, using an external build of the Boehm-Demers-Weiser garbage 2046 1.13 mrg collector (<a href="https://www.hboehm.info/gc/">https://www.hboehm.info/gc/</a>). This library needs to be 2047 1.9 mrg available for each multilib variant, unless configured with 2048 1.10 mrg <samp>--enable-objc-gc=‘<samp>auto</samp>’</samp> in which case the build of the 2049 1.9 mrg additional runtime library is skipped when not available and the build 2050 1.9 mrg continues. 2051 1.10 mrg </p> 2052 1.10 mrg </dd> 2053 1.14 mrg <dt><span><code>--with-target-bdw-gc=<var>list</var></code></span></dt> 2054 1.14 mrg <dt><span><code>--with-target-bdw-gc-include=<var>list</var></code></span></dt> 2055 1.14 mrg <dt><span><code>--with-target-bdw-gc-lib=<var>list</var></code></span></dt> 2056 1.10 mrg <dd><p>Specify search directories for the garbage collector header files and 2057 1.9 mrg libraries. <var>list</var> is a comma separated list of key value pairs of the 2058 1.10 mrg form ‘<samp><var>multilibdir</var>=<var>path</var></samp>’, where the default multilib key 2059 1.10 mrg is named as ‘<samp>.</samp>’ (dot), or is omitted (e.g. 2060 1.10 mrg ‘<samp>--with-target-bdw-gc=/opt/bdw-gc,32=/opt-bdw-gc32</samp>’). 2061 1.10 mrg </p> 2062 1.10 mrg <p>The options <samp>--with-target-bdw-gc-include</samp> and 2063 1.10 mrg <samp>--with-target-bdw-gc-lib</samp> must always be specified together 2064 1.9 mrg for each multilib variant and they take precedence over 2065 1.10 mrg <samp>--with-target-bdw-gc</samp>. If <samp>--with-target-bdw-gc-include</samp> 2066 1.9 mrg is missing values for a multilib, then the value for the default 2067 1.10 mrg multilib is used (e.g. ‘<samp>--with-target-bdw-gc-include=/opt/bdw-gc/include</samp>’ 2068 1.10 mrg ‘<samp>--with-target-bdw-gc-lib=/opt/bdw-gc/lib64,32=/opt-bdw-gc/lib32</samp>’). 2069 1.9 mrg If none of these options are specified, the library is assumed in 2070 1.10 mrg default locations. 2071 1.10 mrg </p></dd> 2072 1.6 mrg </dl> 2073 1.1 mrg 2074 1.14 mrg <span id="D-Specific-Options"></span><h4 class="subheading">D-Specific Options</h4> 2075 1.12 mrg 2076 1.12 mrg <p>The following options apply to the build of the D runtime library. 2077 1.12 mrg </p> 2078 1.12 mrg <dl compact="compact"> 2079 1.14 mrg <dt><span><code>--enable-libphobos-checking</code></span></dt> 2080 1.14 mrg <dt><span><code>--disable-libphobos-checking</code></span></dt> 2081 1.14 mrg <dt><span><code>--enable-libphobos-checking=<var>list</var></code></span></dt> 2082 1.13 mrg <dd><p>This option controls whether run-time checks and contracts are compiled into 2083 1.13 mrg the D runtime library. When the option is not specified, the library is built 2084 1.13 mrg with ‘<samp>release</samp>’ checking. When the option is specified without a 2085 1.13 mrg <var>list</var>, the result is the same as ‘<samp>--enable-libphobos-checking=yes</samp>’. 2086 1.13 mrg Likewise, ‘<samp>--disable-libphobos-checking</samp>’ is equivalent to 2087 1.13 mrg ‘<samp>--enable-libphobos-checking=no</samp>’. 2088 1.13 mrg </p> 2089 1.13 mrg <p>The categories of checks available in <var>list</var> are ‘<samp>yes</samp>’ (compiles 2090 1.13 mrg libphobos with <samp>-fno-release</samp>), ‘<samp>no</samp>’ (compiles libphobos with 2091 1.13 mrg <samp>-frelease</samp>), ‘<samp>all</samp>’ (same as ‘<samp>yes</samp>’), ‘<samp>none</samp>’ or 2092 1.13 mrg ‘<samp>release</samp>’ (same as ‘<samp>no</samp>’). 2093 1.13 mrg </p> 2094 1.13 mrg <p>Individual checks available in <var>list</var> are ‘<samp>assert</samp>’ (compiles libphobos 2095 1.13 mrg with an extra option <samp>-fassert</samp>). 2096 1.13 mrg </p> 2097 1.13 mrg </dd> 2098 1.14 mrg <dt><span><code>--with-libphobos-druntime-only</code></span></dt> 2099 1.14 mrg <dt><span><code>--with-libphobos-druntime-only=<var>choice</var></code></span></dt> 2100 1.13 mrg <dd><p>Specify whether to build only the core D runtime library (druntime), or both 2101 1.13 mrg the core and standard library (phobos) into libphobos. This is useful for 2102 1.13 mrg targets that have full support in druntime, but no or incomplete support 2103 1.13 mrg in phobos. <var>choice</var> can be one of ‘<samp>auto</samp>’, ‘<samp>yes</samp>’, and ‘<samp>no</samp>’ 2104 1.13 mrg where ‘<samp>auto</samp>’ is the default. 2105 1.13 mrg </p> 2106 1.13 mrg <p>When the option is not specified, the default choice ‘<samp>auto</samp>’ means that it 2107 1.13 mrg is inferred whether the target has support for the phobos standard library. 2108 1.13 mrg When the option is specified without a <var>choice</var>, the result is the same as 2109 1.13 mrg ‘<samp>--with-libphobos-druntime-only=yes</samp>’. 2110 1.13 mrg </p> 2111 1.13 mrg </dd> 2112 1.14 mrg <dt><span><code>--with-target-system-zlib</code></span></dt> 2113 1.12 mrg <dd><p>Use installed ‘<samp>zlib</samp>’ rather than that included with GCC. This needs 2114 1.12 mrg to be available for each multilib variant, unless configured with 2115 1.12 mrg <samp>--with-target-system-zlib=‘<samp>auto</samp>’</samp> in which case the GCC included 2116 1.12 mrg ‘<samp>zlib</samp>’ is only used when the system installed library is not available. 2117 1.12 mrg </p></dd> 2118 1.12 mrg </dl> 2119 1.12 mrg 2120 1.10 mrg <hr /> 2121 1.10 mrg <p> 2122 1.8 mrg <p><a href="./index.html">Return to the GCC Installation page</a> 2123 1.10 mrg </p> 2124 1.10 mrg 2125 1.10 mrg 2126 1.10 mrg 2127 1.10 mrg 2128 1.10 mrg 2129 1.10 mrg 2130 1.10 mrg 2131 1.10 mrg 2132 1.10 mrg 2133 1.1 mrg 2134 1.1 mrg 2135 1.10 mrg </body> 2136 1.10 mrg </html> 2137
Indexes created Thu Jul 16 00:26:27 UTC 2026