Changeset df15e9f for general/prog/openjdk.xml
- Timestamp:
- 05/09/2015 02:18:12 PM (9 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 7.10, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
- Children:
- d9d5a5f
- Parents:
- b5c1d05
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
general/prog/openjdk.xml
rb5c1d05 rdf15e9f 248 248 <listitem> 249 249 <para> 250 Optionaltest harness: <ulink url="&jtreg-download;"/>250 Recommended test harness: <ulink url="&jtreg-download;"/> 251 251 </para> 252 252 </listitem> … … 305 305 306 306 <para> 307 If you have downloaded the test harness, unpack it too:307 If you have downloaded the recommended test harness, unpack it too: 308 308 </para> 309 309 … … 361 361 </userinput></screen> 362 362 363 <para> 364 It seems that the test infrastructure of OpenJDK is a work in 365 progress, so that testing the newly built JVM involves several steps. 363 <warning> 364 <para> 365 Although the test infrastructure of <application>OpenJDK</application> 366 is not easy to use, it is recommended to run the tests in order to 367 make sure that the JVM runs fine. A malfunctionning JVM may have 368 catastrophic consequences in term of security. 369 </para> 370 </warning> 371 <note> 372 <para> 373 Testing will involve the interplay of pairs of JVMs using the 374 networking interface, so networking must be started. If it 375 isn't, not only will these tests fail, but the test cleanup 376 will leave orphaned JVMs running. There will be many of 377 them. Rebooting may be the easiest recovery. 378 </para> 379 </note> 380 381 <para> 382 Testing the newly built JVM involves several steps. 366 383 First, it is better to run the test suite in a frame buffer on a 367 384 different display, using Xvfb: … … 440 457 <ulink url="http://download.java.net/openjdk/testresults/8/">these 441 458 results</ulink>, although they usually are run on a newer version. 442 There are a few failures, the number of which depends on various459 Some failures can be expected, the number of which depends on various 443 460 conditions, like whether the computer is connected to network. Also, some 444 461 tests may timeout if the machine is under load. … … 557 574 558 575 <para> 559 <option>--with-jobs=N</option>: Allows to setthe number576 <option>--with-jobs=N</option>: Allows setting the number 560 577 of jobs for <command>make</command> equal to N. The default is the 561 578 result of a calculation involving the available memory and the number … … 567 584 <para> 568 585 <option>--with-cacerts-file=...</option>: Specifies where to find a 569 <filename>cacerts</filename> file. Otherwise, an empty one is created. 586 <filename>cacerts</filename> file, typically <filename> 587 /opt/jdk/jre/lib/security</filename>. Otherwise, an empty one is created. 570 588 You can get it from an earlier version of the package, or use the 571 589 script below to generate one. 572 590 </para> 591 573 592 <para> 574 593 <command>make DEBUG_BINARIES=true all</command>: The build fails … … 577 596 578 597 <para> 579 <command>find ... -iname '*.jar' -exec chmod a+r {} \;</command> 580 and following line: Fix permission in some library files, in order to 581 allow all users to access them. 582 </para> 583 584 <para> 585 <command>find ... -iname '*.diz' -delete</command>: This command and the 586 the next one remove redundant files. 598 <command>find ... -iname '*.diz' -delete</command>: This command 599 removes redundant files. 587 600 </para> 588 601 … … 613 626 614 627 <para> 615 Use the following procedure to install the 616 <filename>cacerts</filename> or to generate a new one if 617 <xref linkend="cacerts"/> have been updated. First, if it is not 618 already present, generate the <command>mkcacerts</command> script 628 <application>OpenJDK</application> uses its own format for the 629 CA certificates. Those certificates are located in a file named <filename> 630 /opt/jdk/jre/lib/security/cacerts</filename>. That file may be generated 631 from the one installed using the instructions on the <xref 632 linkend="cacerts"/> page, using the following procedure. 633 First, generate the <command>mkcacerts</command> script 619 634 as the <systemitem class="username">root</systemitem> user: 620 635 </para> … … 846 861 </note> 847 862 848 <para>If you need to generate a <filename>cacerts</filename> file, 849 and there is already one in 850 <filename class="directory">/opt/jdk/jre/lib/security</filename>, it 851 is better to make a backup. Then, you can create a new one, as the 852 <systemitem class="username">root</systemitem> user:</para> 853 854 <screen role="root"><userinput>/opt/jdk/bin/mkcacerts \ 855 -d "/etc/ssl/certs/" \ 856 -k "/opt/jdk/bin/keytool" \ 857 -s "/usr/bin/openssl" \ 863 <para> 864 Generate the <application>OpenJDK</application> <filename>cacerts</filename> 865 file as the <systemitem class="username">root</systemitem> user: 866 </para> 867 868 <screen role="root"><userinput>if [ -f /opt/jdk/jre/lib/security/cacerts ]; then 869 mv /opt/jdk/jre/lib/security/cacerts \ 870 /opt/jdk/jre/lib/security/cacerts.bak 871 fi && 872 /opt/jdk/bin/mkcacerts \ 873 -d "/etc/ssl/certs/" \ 874 -k "/opt/jdk/bin/keytool" \ 875 -s "/usr/bin/openssl" \ 858 876 -o "/opt/jdk/jre/lib/security/cacerts"</userinput></screen> 859 877
Note:
See TracChangeset
for help on using the changeset viewer.