Re: Minor problem using just made "make"

[Paul D. Smith]

%% leam <address@hidden> writes:

  l> Sorry, don't have the GNU Make Manual handy.

It comes with the distribution.

  l> There does seem to be two small issues in the making of
  l> "make". FYI, I am using a sparc/Linux box, with make 3.79 just
  l> downloaded from ftp.gnu.org.

Note this isn't the "freshest, purest "make" possible" :); the latest
version of make is 3.79.1 (available from ftp.gnu.org).

  l> Problem 1. I wanted to have the freshest, purest "make" possible,
  l> so just before I did "make install", I removed the older version of
  l> make that came, as an rpm, with the distribution. I used the
  l> "./make install" as suggested by the "INSTALL" doc. The script went
  l> into I18n and bombed. It was fixed by copying the new "make" into
  l> "/usr/bin".

You will have to send me details: what does "bombed" mean?  I just tried
this (removed my copies of make and ran "./make install") on my system
(Debian GNU/Linux) and it worked fine (with 3.79.1).

  l> Suggestion 1. Have the script set "make" to the absolute pathname of
  l> whatever is used to call the "./make install". 

This should not be necessary; make always uses the variable MAKE to
invoke submakes, and that's set to the invoking make.  As I said, it
works for me.

  l> Problem 2. Again, minor. "make check" is listed before "make install".
  l> My "make check" did not work until after the "make install" was done.

Again, it should have done so (well, you need to run "./make check", of
course).  If that doesn't work, again, please send me the errors.  It
works for me.

-- 
-------------------------------------------------------------------------------
 Paul D. Smith <address@hidden>          Find some GNU make tips at:
 http://www.gnu.org                      http://www.paulandlesley.org/gmake/
 "Please remain calm...I may be mad, but I am a professional." --Mad Scientist