From: Bastien <bzg@altern.org>
To: Glenn Morris <rgm@gnu.org>
Cc: 12411@debbugs.gnu.org
Subject: bug#12411: 24.2.50; No `make help' target?
Date: Tue, 11 Sep 2012 22:34:36 +0200 [thread overview]
Message-ID: <87pq5sfgdf.fsf@altern.org> (raw)
In-Reply-To: <2lpq5sjrsc.fsf@fencepost.gnu.org> (Glenn Morris's message of "Tue, 11 Sep 2012 15:14:27 -0400")
Glenn Morris <rgm@gnu.org> writes:
> Bastien wrote:
>
>> `make help' and `make targets' don't exist in last rev.
>
> In general, Emacs has the standard GNU Makefile targets:
>
> http://www.gnu.org/prep/standards/html_node/Standard-Targets.html
>
> Your proposed two are not in that list.
> Could you say what you want them to do?
My bad, I thought the `help' target was a GNU standard.
`make help' would display a one-line help about the various
available targets:
# make all
# make install
# make TAGS
# make clean (or make mostlyclean)
# make distclean
# make maintainer-clean
# make extraclean
# make bootstrap
(Taken from INSTALL, not from the actual Makefile.)
If I'm not confused, the last two targets are not in the
GNU standards (`bootstrap' and `extraclean').
Documenting `make extraclean' is not important IMO but
documenting `make bootstrap' could be: there are often
questions on emacs-devel which are answered by "You need
to `make bootstrap'."
I guess `make help' could give a better exposure to this
option?
--
Bastien
next prev parent reply other threads:[~2012-09-11 20:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-11 9:05 bug#12411: 24.2.50; No `make help' target? Bastien
2012-09-11 19:14 ` Glenn Morris
2012-09-11 20:34 ` Bastien [this message]
2012-09-12 7:52 ` Glenn Morris
2012-09-12 9:59 ` Bastien
2012-09-13 2:47 ` Glenn Morris
2012-09-13 12:43 ` Stefan Monnier
2012-09-13 3:23 ` Stefan Monnier
2019-08-20 23:09 ` Stefan Kangas
2019-08-21 16:57 ` Eli Zaretskii
2019-08-27 23:56 ` Stefan Kangas
2019-08-28 11:28 ` Eli Zaretskii
2019-08-29 10:01 ` Stefan Kangas
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=87pq5sfgdf.fsf@altern.org \
--to=bzg@altern.org \
--cc=12411@debbugs.gnu.org \
--cc=rgm@gnu.org \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.