HACKING: update with "gmake" in examples

Most GNU users already know their "make" is GNU make but it may
not be obvious to non-GNU users.

1 files changed, 8 insertions, 5 deletions

diff --git a/HACKING b/HACKING
index 08aa76d..119b6b7 100644
--- a/HACKING
+++ b/HACKING
@@ -16,6 +16,9 @@ Tests are good, but slow tests make development slow, so we make tests
 faster (in parallel) with GNU make (instead of Rake) and avoiding
 Rubygems.
 
+Users of GNU-based systems (such as GNU/Linux) usually have GNU make installed
+as "make" instead of "gmake".
+
 Since we don't load RubyGems by default, loading Rack properly requires
 setting up RUBYLIB to point to where Rack is located.  Not loading
 Rubygems drastically lowers the time to run the full test suite.  You
@@ -25,15 +28,15 @@ file is provided for reference.
 
 Running the entire test suite with 4 tests in parallel:
 
-  make -j4 test
+  gmake -j4 test
 
 Running just one unit test:
 
-  make test/unit/test_http_parser.rb
+  gmake test/unit/test_http_parser.rb
 
 Running just one test case in a unit test:
 
-  make test/unit/test_http_parser.rb--test_parse_simple.n
+  gmake test/unit/test_http_parser.rb--test_parse_simple.n
 
 === HttpServer
 
@@ -103,11 +106,11 @@ It is easy to install the contents of your git working directory:
 
 Via RubyGems (RubyGems 1.3.5+ recommended for prerelease versions):
 
-  make install-gem
+  gmake install-gem
 
 Without RubyGems (via setup.rb):
 
-  make install
+  gmake install
 
 It is not at all recommended to mix a RubyGems installation with an
 installation done without RubyGems, however.