X-Git-Url: http://git.onelab.eu/?a=blobdiff_plain;f=INSTALL;h=18e8532912b8a93373d2179f7eb2e1b7870a3173;hb=f40869bdf6feca4d3ff7c59a1fb1f7ac101bc967;hp=a96f774c54a6602cd960f99092c527df443633d4;hpb=380b39f729a8ebcf1c31e8c08bc721000e7ff89e;p=sliver-openvswitch.git

diff --git a/INSTALL b/INSTALL
index a96f774c5..18e853291 100644
--- a/INSTALL
+++ b/INSTALL
@@ -21,8 +21,6 @@ you will need the following software:
     - The GNU C compiler.  We generally test with version 4.1, 4.2, or
       4.3.
 
-    - pkg-config.  We test with version 0.22.
-
     - libssl, from OpenSSL, is optional but recommended if you plan to
       connect the Open vSwitch to an OpenFlow controller.  libssl is
       required to establish confidentiality and authenticity in the
@@ -391,7 +389,7 @@ check".  All the same options are available via TESTSUITEFLAGS.  When
 you do this, the "valgrind" results for test <N> are reported in files
 named tests/testsuite.dir/<N>/valgrind.*.  You may find that the
 valgrind results are easier to interpret if you put "-q" in
-~/.valgrindrc, since that reduces the amount of
+~/.valgrindrc, since that reduces the amount of output.
 
 Sometimes a few tests may fail on some runs but not others.  This is
 usually a bug in the testsuite, not a bug in Open vSwitch itself.  If