doc/building.html
branchdatagramsocketimpl-branch
changeset 58678 9cf78a70fa4f
parent 54999 98ed47cd114a
child 58679 9c3209ff7550
equal deleted inserted replaced
58677:13588c901957 58678:9cf78a70fa4f
   279 </tr>
   279 </tr>
   280 </thead>
   280 </thead>
   281 <tbody>
   281 <tbody>
   282 <tr class="odd">
   282 <tr class="odd">
   283 <td style="text-align: left;">Linux</td>
   283 <td style="text-align: left;">Linux</td>
   284 <td style="text-align: left;">gcc 8.2.0</td>
   284 <td style="text-align: left;">gcc 8.3.0</td>
   285 </tr>
   285 </tr>
   286 <tr class="even">
   286 <tr class="even">
   287 <td style="text-align: left;">macOS</td>
   287 <td style="text-align: left;">macOS</td>
   288 <td style="text-align: left;">Apple Xcode 10.1 (using clang 10.0.0)</td>
   288 <td style="text-align: left;">Apple Xcode 10.1 (using clang 10.0.0)</td>
   289 </tr>
   289 </tr>
   291 <td style="text-align: left;">Solaris</td>
   291 <td style="text-align: left;">Solaris</td>
   292 <td style="text-align: left;">Oracle Solaris Studio 12.6 (with compiler version 5.15)</td>
   292 <td style="text-align: left;">Oracle Solaris Studio 12.6 (with compiler version 5.15)</td>
   293 </tr>
   293 </tr>
   294 <tr class="even">
   294 <tr class="even">
   295 <td style="text-align: left;">Windows</td>
   295 <td style="text-align: left;">Windows</td>
   296 <td style="text-align: left;">Microsoft Visual Studio 2017 update 15.9.6</td>
   296 <td style="text-align: left;">Microsoft Visual Studio 2017 update 15.9.16</td>
   297 </tr>
   297 </tr>
   298 </tbody>
   298 </tbody>
   299 </table>
   299 </table>
   300 <p>All compilers are expected to be able to compile to the C99 language standard,
   300 <p>All compilers are expected to be able to compile to the C99 language standard, as some C99 features are used in the source code. Microsoft Visual Studio doesn't fully support C99 so in practice shared code is limited to using C99 features that it does support.</p>
   301 as some C99 features are used in the source code. Microsoft Visual Studio
       
   302 doesn't fully support C99 so in practice shared code is limited to using C99
       
   303 features that it does support.</p>
       
   304 <h3 id="gcc">gcc</h3>
   301 <h3 id="gcc">gcc</h3>
   305 <p>The minimum accepted version of gcc is 4.8. Older versions will generate a warning by <code>configure</code> and are unlikely to work.</p>
   302 <p>The minimum accepted version of gcc is 4.8. Older versions will generate a warning by <code>configure</code> and are unlikely to work.</p>
   306 <p>The JDK is currently known to be able to compile with at least version 7.4 of gcc.</p>
   303 <p>The JDK is currently known to be able to compile with at least version 8.3 of gcc.</p>
   307 <p>In general, any version between these two should be usable.</p>
   304 <p>In general, any version between these two should be usable.</p>
   308 <h3 id="clang">clang</h3>
   305 <h3 id="clang">clang</h3>
   309 <p>The minimum accepted version of clang is 3.2. Older versions will not be accepted by <code>configure</code>.</p>
   306 <p>The minimum accepted version of clang is 3.2. Older versions will not be accepted by <code>configure</code>.</p>
   310 <p>To use clang instead of gcc on Linux, use <code>--with-toolchain-type=clang</code>.</p>
   307 <p>To use clang instead of gcc on Linux, use <code>--with-toolchain-type=clang</code>.</p>
   311 <h3 id="apple-xcode">Apple Xcode</h3>
   308 <h3 id="apple-xcode">Apple Xcode</h3>
   573 <ul>
   570 <ul>
   574 <li><code>SPEC</code></li>
   571 <li><code>SPEC</code></li>
   575 <li><code>CONF_CHECK</code></li>
   572 <li><code>CONF_CHECK</code></li>
   576 <li><code>COMPARE_BUILD</code></li>
   573 <li><code>COMPARE_BUILD</code></li>
   577 <li><code>JDK_FILTER</code></li>
   574 <li><code>JDK_FILTER</code></li>
       
   575 <li><code>SPEC_FILTER</code></li>
   578 </ul>
   576 </ul>
   579 <h2 id="running-tests">Running Tests</h2>
   577 <h2 id="running-tests">Running Tests</h2>
   580 <p>Most of the JDK tests are using the <a href="http://openjdk.java.net/jtreg">JTReg</a> test framework. Make sure that your configuration knows where to find your installation of JTReg. If this is not picked up automatically, use the <code>--with-jtreg=&lt;path to jtreg home&gt;</code> option to point to the JTReg framework. Note that this option should point to the JTReg home, i.e. the top directory, containing <code>lib/jtreg.jar</code> etc.</p>
   578 <p>Most of the JDK tests are using the <a href="http://openjdk.java.net/jtreg">JTReg</a> test framework. Make sure that your configuration knows where to find your installation of JTReg. If this is not picked up automatically, use the <code>--with-jtreg=&lt;path to jtreg home&gt;</code> option to point to the JTReg framework. Note that this option should point to the JTReg home, i.e. the top directory, containing <code>lib/jtreg.jar</code> etc.</p>
   581 <p>The <a href="https://wiki.openjdk.java.net/display/Adoption">Adoption Group</a> provides recent builds of jtreg <a href="https://adopt-openjdk.ci.cloudbees.com/job/jtreg/lastSuccessfulBuild/artifact">here</a>. Download the latest <code>.tar.gz</code> file, unpack it, and point <code>--with-jtreg</code> to the <code>jtreg</code> directory that you just unpacked.</p>
   579 <p>The <a href="https://wiki.openjdk.java.net/display/Adoption">Adoption Group</a> provides recent builds of jtreg <a href="https://adopt-openjdk.ci.cloudbees.com/job/jtreg/lastSuccessfulBuild/artifact">here</a>. Download the latest <code>.tar.gz</code> file, unpack it, and point <code>--with-jtreg</code> to the <code>jtreg</code> directory that you just unpacked.</p>
   582 <p>To execute the most basic tests (tier 1), use:</p>
   580 <p>To execute the most basic tests (tier 1), use:</p>