From: David Masterson <David.Masterson@synopsys.COM>
Cc: emacs-devel@gnu.org
Subject: Re: INSTALL-CVS
Date: Wed, 4 Jun 2003 10:26:06 -0700 [thread overview]
Message-ID: <16094.11182.414000.952773@gargle.gargle.HOWL> (raw)
In-Reply-To: <200306041442.h54EgTtL025689@rum.cs.yale.edu>
>>>>> Stefan Monnier writes:
>> David Masterson <David.Masterson@synopsys.com> writes:
>>
>> |> >>>>> Richard Stallman writes:
>> |>
>> |> > However, I guess it would be harmless now to change it so that
>> |> > top-level `make all' updates the Info files but does not generate
>> |> > the DVI files.
>> |>
>> |> Suggestion -- have the configure script 'touch' the Info files as the
>> |> last thing it does if and only if they exist at the time of the
>> |> 'configure'.
>>
>> This is counter-productive, because then if you rerun configure when the
>> info files are out-of-date they won't be rebuilt.
Is there a configure output file that could be checked for existence
(config.log) and don't do the 'touch' in that case?
> Agreed.
> I think we should simply add `man' to the default target and live
> with it. If that means that `makeinfo' is sometimes called when a
> user installs Emacs, what's the big deal ? If the problem is that
> the user might not have a working `makeinfo', how about running it
> with a leading "-" so that an error from `makeinfo' is ignored by
> make ?
Ignoring the error in 'man' would cause 'install-man' to fail.
Perhaps configure should test for a working 'makeinfo' (if it doesn't
already) and default to (say) '/bin/true' if no working makeinfo is
found?
--
David Masterson David DOT Masterson AT synopsys DOT com
Sr. R&D Engineer Synopsys, Inc.
Software Engineering Sunnyvale, CA
next prev parent reply other threads:[~2003-06-04 17:26 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-29 21:31 INSTALL-CVS Nick Roberts
2003-06-01 15:24 ` INSTALL-CVS Eli Zaretskii
2003-06-01 20:51 ` INSTALL-CVS Nick Roberts
2003-06-02 4:06 ` INSTALL-CVS Eli Zaretskii
2003-06-02 16:56 ` INSTALL-CVS Stefan Monnier
2003-06-02 22:34 ` INSTALL-CVS Nick Roberts
2003-06-02 22:35 ` INSTALL-CVS Nick Roberts
2003-06-03 4:06 ` INSTALL-CVS Richard Stallman
2003-06-03 6:54 ` INSTALL-CVS David Masterson
2003-06-04 11:38 ` INSTALL-CVS Andreas Schwab
2003-06-04 14:42 ` INSTALL-CVS Stefan Monnier
2003-06-04 17:26 ` David Masterson [this message]
2003-06-04 17:27 ` INSTALL-CVS Stefan Monnier
2003-06-04 17:52 ` INSTALL-CVS David Masterson
2003-06-04 17:55 ` INSTALL-CVS Stefan Monnier
2003-06-05 10:58 ` INSTALL-CVS Richard Stallman
2003-06-05 14:02 ` INSTALL-CVS Stefan Monnier
2003-06-05 19:02 ` INSTALL-CVS Nick Roberts
2003-06-06 17:02 ` INSTALL-CVS Richard Stallman
2003-06-04 17:38 ` INSTALL-CVS David Masterson
2003-06-04 18:06 ` INSTALL-CVS Stefan Monnier
2003-06-04 20:54 ` INSTALL-CVS David Masterson
2003-06-04 21:00 ` INSTALL-CVS Stefan Monnier
2003-06-04 23:01 ` INSTALL-CVS David Masterson
2003-06-05 21:46 ` INSTALL-CVS Richard Stallman
2003-06-05 23:38 ` INSTALL-CVS David Masterson
2003-06-05 12:49 ` INSTALL-CVS Andreas Schwab
-- strict thread matches above, loose matches on Subject: below --
2002-06-16 18:41 INSTALL-CVS D. Goel
2002-06-16 19:02 ` INSTALL-CVS Simon Josefsson
2002-06-17 6:07 ` INSTALL-CVS Eli Zaretskii
2002-06-18 16:29 ` INSTALL-CVS D. Goel
2002-06-19 5:15 ` INSTALL-CVS Eli Zaretskii
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=16094.11182.414000.952773@gargle.gargle.HOWL \
--to=david.masterson@synopsys.com \
--cc=emacs-devel@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.