unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: emacs-devel@gnu.org
Subject: Re: Set the version number in the texinfo manuals using configure
Date: Sat, 30 Oct 2010 23:10:42 +0200	[thread overview]
Message-ID: <83ocab5qul.fsf@gnu.org> (raw)
In-Reply-To: <4CCC850F.1080102@gmx.at>

> Date: Sat, 30 Oct 2010 22:50:23 +0200
> From: martin rudalics <rudalics@gmx.at>
> CC: emacs-devel@gnu.org
> 
>  > So it's not like it succeeds the second time, it always fails for
>  > you.  It's just that the --force switch forces it to build the Info
>  > manual regardless of the error.
> 
> But it somehow stops after the error the first time and builds the
> remaining files only the second time (at least I think so).

Because makeinfo exits with an error status, and Make stops.  IOW,
using the --force switch to makeinfo prevents it from deleting the
produced Info file, but does not prevent it from returning an exit
status that indicates an error.

> make   -C ../doc/misc info
> make[1]: Entering directory `C:/emacs/trunk/doc/misc'
> makeinfo --force -I./../emacs faq.texi
> makeinfo --force calc.texi
> calc.texi:10: @include `emacsver.texi': No such file or directory.
> make[1]: *** [../../info/calc] Error 1

That's definitely an old makefile, from before the latest changes to
makefile.w32-in: the command for faq.texi includes the -I switch,
while the command for calc.texi does not.  Please show the full
doc/misc/makefile you have.  Also, please look into the doc/misc
directory and tell which files you have there that match the wildcard
"*make*" (e.g. "dir *make*" should show that).



  reply	other threads:[~2010-10-30 21:10 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-09  9:58 Set the version number in the texinfo manuals using configure Eli Zaretskii
2010-10-09 18:08 ` Glenn Morris
2010-10-09 21:48   ` Eli Zaretskii
2010-10-24 19:59 ` Jay Belanger
2010-10-24 21:38   ` Eli Zaretskii
2010-10-24 21:59     ` Jay Belanger
2010-10-30  8:30     ` martin rudalics
2010-10-30 13:16       ` Eli Zaretskii
2010-10-30 14:49         ` martin rudalics
2010-10-30 15:27           ` Eli Zaretskii
2010-10-30 17:01             ` martin rudalics
2010-10-30 17:15               ` Eli Zaretskii
2010-10-30 17:57                 ` martin rudalics
2010-10-30 19:42                   ` Eli Zaretskii
2010-10-30 20:50                     ` martin rudalics
2010-10-30 21:10                       ` Eli Zaretskii [this message]
2010-10-30 21:20                         ` Jay Belanger
2010-10-30 22:02                           ` Eli Zaretskii
     [not found]                         ` <4CCC9EF8.9040507@gmx.at>
2010-10-31  3:59                           ` Eli Zaretskii
2010-10-31  8:18                             ` martin rudalics
2010-10-31 11:04                               ` Eli Zaretskii
2010-10-31 11:26                                 ` martin rudalics
2010-10-31 11:56                                   ` Juanma Barranquero
2010-10-31 13:09                                     ` Eli Zaretskii
2010-10-31 13:27                                       ` Juanma Barranquero
2010-10-31 15:17                                         ` martin rudalics

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83ocab5qul.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rudalics@gmx.at \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).