From: Wayne Davison <wayned@users.sourceforge.net>
To: goetz fischer <g.fischer@ah-online.com>
Cc: Zsh hackers list <zsh-workers@sunsite.dk>
Subject: Re: zsh 4.3.2 bug
Date: Tue, 14 Mar 2006 15:56:29 -0800 [thread overview]
Message-ID: <20060314235629.GA25908@dot.blorf.net> (raw)
In-Reply-To: <441753CD.4ACAF943@ah-online.com>
On Wed, Mar 15, 2006 at 12:37:49AM +0100, goetz fischer wrote:
> okay so i'll give 4.3.1 a try.
I doubt that will make a difference. What you need to figure out is why
the building of the signames.c file failed. The make rules are this
(taken from Makemod.in):
signames.c: signames1.awk signames2.awk ../config.h @SIGNAL_H@
$(AWK) -f $(sdir)/signames1.awk @SIGNAL_H@ >sigtmp.c
$(CPP) sigtmp.c >sigtmp.out
$(AWK) -f $(sdir)/signames2.awk sigtmp.out > $@
rm -f sigtmp.c sigtmp.out
sigcount.h: signames.c
grep 'define.*SIGCOUNT' signames.c > $@
My generated Makemod file has "/usr/include/bits/signum.h" in place of
the @SIGNAL_H@ value. Those awk and cpp commands should generate a file
named signames.c that should have a define for SIGCOUNT in it, e.g.:
#define SIGCOUNT 31
It should also define an array named sigs[], e.g.:
char *sigs[SIGCOUNT+4] = {
"EXIT",
"HUP",
"INT",
[...]
Perhaps your awk didn't work right? Or perhaps the SIGNAL_H file wasn't
chosen correctly?
Once the signames.c file gets built right, then the sigcount.h file
should end up with two lines in it. Mine is this:
#define SIGCOUNT 31
#define sigmsg(sig) ((sig) <= SIGCOUNT ? sig_msg[sig] : "unknown signal")
At that point, the build errors you cited should go away.
..wayne..
next prev parent reply other threads:[~2006-03-14 23:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-12 0:52 g.fischer
2006-03-13 10:42 ` Peter Stephenson
2006-03-14 23:37 ` goetz fischer
2006-03-14 23:56 ` Wayne Davison [this message]
2006-03-15 3:07 ` g.fischer
2006-03-17 10:08 François-Xavier Coudert
2006-03-17 17:18 ` goetz fischer
2006-03-17 17:45 ` François-Xavier Coudert
2006-03-17 18:46 ` Wayne Davison
2006-03-17 23:09 ` FX Coudert
2006-03-17 23:02 ` goetz fischer
2006-03-19 5:09 ` g.fischer
2006-03-19 21:54 ` Peter Stephenson
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=20060314235629.GA25908@dot.blorf.net \
--to=wayned@users.sourceforge.net \
--cc=g.fischer@ah-online.com \
--cc=zsh-workers@sunsite.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).