From f6bfbb2b0936a5f23534d3d63a6163d22a49317a Mon Sep 17 00:00:00 2001 From: Hollow Man Date: Fri, 27 Nov 2020 19:32:24 +0000 Subject: [PATCH] 8257208: Fix typo in doc/building.md Reviewed-by: ihse --- doc/building.html | 6 +++--- doc/building.md | 6 +++--- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/doc/building.html b/doc/building.html index 318a24aa840..20adf7e3037 100644 --- a/doc/building.html +++ b/doc/building.html @@ -400,7 +400,7 @@
  • --enable-jvm-feature-<feature> or --disable-jvm-feature-<feature> - Include (or exclude) <feature> as a JVM feature in Hotspot. You can also specify a list of features to be enabled, separated by space or comma, as --with-jvm-features=<feature>[,<feature>...]. If you prefix <feature> with a -, it will be disabled. These options will modify the default list of features for the JVM variant(s) you are building. For the custom JVM variant, the default list is empty. A complete list of valid JVM features can be found using bash configure --help.
  • --with-target-bits=<bits> - Create a target binary suitable for running on a <bits> platform. Use this to create 32-bit output on a 64-bit build platform, instead of doing a full cross-compile. (This is known as a reduced build.)
  • -

    On Linux, BSD and AIX, it is possible to override where Java by default searches for runtime/JNI libraries. This can be useful in situations where there is a special shared directory for system JNI libraries. This setting can in turn be overriden at runtime by setting the java.library.path property.

    +

    On Linux, BSD and AIX, it is possible to override where Java by default searches for runtime/JNI libraries. This can be useful in situations where there is a special shared directory for system JNI libraries. This setting can in turn be overridden at runtime by setting the java.library.path property.

    @@ -439,7 +439,7 @@

    Configure Control Variables

    It is possible to control certain aspects of configure by overriding the value of configure variables, either on the command line or in the environment.

    Normally, this is not recommended. If used improperly, it can lead to a broken configuration. Unless you're well versed in the build system, this is hard to use properly. Therefore, configure will print a warning if this is detected.

    -

    However, there are a few configure variables, known as control variables that are supposed to be overriden on the command line. These are variables that describe the location of tools needed by the build, like MAKE or GREP. If any such variable is specified, configure will use that value instead of trying to autodetect the tool. For instance, bash configure MAKE=/opt/gnumake4.0/bin/make.

    +

    However, there are a few configure variables, known as control variables that are supposed to be overridden on the command line. These are variables that describe the location of tools needed by the build, like MAKE or GREP. If any such variable is specified, configure will use that value instead of trying to autodetect the tool. For instance, bash configure MAKE=/opt/gnumake4.0/bin/make.

    If a configure argument exists, use that instead, e.g. use --with-jtreg instead of setting JTREGEXE.

    Also note that, despite what autoconf claims, setting CFLAGS will not accomplish anything. Instead use --with-extra-cflags (and similar for cxxflags and ldflags).

    Running Make

    @@ -476,7 +476,7 @@

    Make Control Variables

    It is possible to control make behavior by overriding the value of make variables, either on the command line or in the environment.

    Normally, this is not recommended. If used improperly, it can lead to a broken build. Unless you're well versed in the build system, this is hard to use properly. Therefore, make will print a warning if this is detected.

    -

    However, there are a few make variables, known as control variables that are supposed to be overriden on the command line. These make up the "make time" configuration, as opposed to the "configure time" configuration.

    +

    However, there are a few make variables, known as control variables that are supposed to be overridden on the command line. These make up the "make time" configuration, as opposed to the "configure time" configuration.

    General Make Control Variables