zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@ibmth.df.unipi.it>
To: zsh-workers@sunsite.auc.dk (Zsh hackers list)
Subject: Re: Couldn't Build 3.1.6 on Nextstep 3.3 m68k System
Date: Mon, 02 Aug 1999 09:51:45 +0200	[thread overview]
Message-ID: <9908020751.AA41377@ibmth.df.unipi.it> (raw)
In-Reply-To: "Irving_Wolfe@Happy-Man.com"'s message of "Sun, 01 Aug 1999 23:52:17 DFT." <19990801235217.J13052@Happy-Man.com>

Irving_Wolfe@Happy-Man.com wrote:
> makeinfo ./zsh.texi; exit 0
> Making info file `zsh.info' from `./zsh.texi'.
> ./zsh.texi:19: Unknown info command `dircategory'.
> ./zsh.texi:20: Unknown info command `direntry'.
> ./zsh.texi:23: Bad argument to `end', `direntry', using `ifinfo'.
> ./zsh.texi:23: Unmatched `@end'.
> *** Exit 2
> *** `zsh.info' removed
> Stop.
> *** Exit 1
> 
> If there is anything after that info step,
> I wonder if it should fail more gracefully,
> since even FSF's efforts haven't gotten me
> to read info files very often.

...and the info files aren't installed by default, either.  But that's
presumably the reason why the `exit 0' was added.  Why is it being
interpreted as `exit 2'?  Is make working too hard and intercepting the
intermediate exit status?  Should that be `makeinfo ./zsh.texi || exit 0'?

-- 
Peter Stephenson <pws@ibmth.df.unipi.it>       Tel: +39 050 844536
WWW:  http://www.ifh.de/~pws/
Dipartimento di Fisica, Via Buonarroti 2, 56127 Pisa, Italy


  reply	other threads:[~1999-08-02  8:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-08-02  4:45 Irving Wolfe
1999-08-02  4:51 ` Timothy J Luoma
1999-08-02  5:57   ` Irving_Wolfe
1999-08-02  6:06 ` Geoff Wing
1999-08-02  6:52   ` Irving_Wolfe
1999-08-02  7:51     ` Peter Stephenson [this message]
1999-08-02  9:29       ` Bart Schaefer
1999-08-02  9:01         ` Peter Stephenson
1999-08-05  5:48     ` Andrej Borsenkow

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=9908020751.AA41377@ibmth.df.unipi.it \
    --to=pws@ibmth.df.unipi.it \
    --cc=zsh-workers@sunsite.auc.dk \
    /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.vuxu.org/mirror/zsh/

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).