From: Justin Sheehy <dworkin@ccs.neu.edu>
Subject: Re: problems formatting the Gnus manual
Date: 22 Jan 1997 11:40:57 -0500 [thread overview]
Message-ID: <vndbuahirxi.fsf@everest.ccs.neu.edu> (raw)
In-Reply-To: Steinar Bang's message of 22 Jan 1997 09:02:13 +0100
>>>>> "Steinar" == Steinar Bang <sb@metis.no> writes:
Steinar> Hm... on an UltraSPARC, Solaris 2.5.1:
Steinar> /fox/sb/src/install/rgnus-0.82/texi% make dvi make: Fatal
Steinar> error: Don't know how to make target `gnus.dvi'
Steinar> /fox/sb/src/install/rgnus-0.82/texi% which make
Steinar> /usr/ccs/bin/make /fox/sb/src/install/rgnus-0.82/texi%
Steinar> It *did* work with GNU make (installed as "gmake"), though.
Gnu make is the only version of make that I know of that knows to do
the implicit steps between targets. (without them being specified in
the Makefile, of course...) I have not yet found a situation when any
other make is superior to the Gnu make.
Use it. Love it.
I recommend aliasing make to gmake in your shell.
-Justin
prev parent reply other threads:[~1997-01-22 16:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-01-21 16:33 Steinar Bang
1997-01-21 22:55 ` Lars Magne Ingebrigtsen
1997-01-22 8:02 ` Steinar Bang
1997-01-22 16:40 ` Justin Sheehy [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=vndbuahirxi.fsf@everest.ccs.neu.edu \
--to=dworkin@ccs.neu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).