ovsdb: bond_active_salve column's value should be durable when database restarts

[cascardo/ovs.git] / INSTALL

diff --git a/INSTALL b/INSTALL
index f43c65b..65009a8 100644 (file)
--- a/INSTALL
+++ b/INSTALL
@@ -85,7 +85,7 @@ If you are working from a Git tree or snapshot (instead of from a
 distribution tarball), or if you modify the Open vSwitch build system
 or the database schema, you will also need the following software:
 
-    - Autoconf version 2.64 or later.
+    - Autoconf version 2.63 or later.
 
     - Automake version 1.10 or later.
 
@@ -149,9 +149,8 @@ Prerequisites section, follow the procedure below to build.
 
       % ./boot.sh
 
-2. In the top source directory, configure the package by running the
-   configure script.  You can usually invoke configure without any
-   arguments:
+2. Configure the package by running the configure script.  You can
+   usually invoke configure without any arguments.  For example:
 
       % ./configure
 
@@ -177,6 +176,10 @@ Prerequisites section, follow the procedure below to build.
 
       % ./configure --with-linux=/lib/modules/`uname -r`/build
 
+   If --with-linux requests building for an unsupported version of
+   Linux, then "configure" will fail with an error message.  Please
+   refer to the FAQ for advice in that case.
+
    If you wish to build the kernel module for an architecture other
    than the architecture of the machine used for the build, you may
    specify the kernel architecture string using the KARCH variable
@@ -199,7 +202,16 @@ Prerequisites section, follow the procedure below to build.
    additional environment variables.  For a full list, invoke
    configure with the --help option.
 
-3. Run GNU make in the top source directory, e.g.:
+   You can also run configure from a separate build directory.  This
+   is helpful if you want to build Open vSwitch in more than one way
+   from a single source directory, e.g. to try out both GCC and Clang
+   builds, or to build kernel modules for more than one Linux version.
+   Here is an example:
+
+      % mkdir _gcc && (cd _gcc && ../configure CC=gcc)
+      % mkdir _clang && (cd _clang && ../configure CC=clang)
+
+3. Run GNU make in the build directory, e.g.:
 
       % make
 
@@ -207,6 +219,12 @@ Prerequisites section, follow the procedure below to build.
 
       % gmake
 
+   If you used a separate build directory, run make or gmake from that
+   directory, e.g.:
+
+      % make -C _gcc
+      % make -C _clang
+
    For improved warnings if you installed "sparse" (see
    "Prerequisites"), add C=1 to the command line.