From: "Arnon" <arnon@microtal.com>
To: <zsh-workers@sunsite.auc.dk>
Subject: zsh 3.1.9 configuration problem
Date: Tue, 19 Dec 2000 02:26:13 -0500 [thread overview]
Message-ID: <NDBBIOJAMKEKHLKCFJPNKEGICCAA.arnon@microtal.com> (raw)
Hi,
I have ancounterd the following problem while running zsh 3.1.9 on RH 7.0.
zsh will compile and run but will lack proper singal names. So when a child
process crash it returns "unknown signal" instead of "segmentation fault"
(the same proble will happen with other signals). i have traced the problem
to signames.c haveing 0 signals. The reson for that is the configure wrongly
picks /usr/include/bits/siginfo.h as the "signal.h" file while the real file
is /usr/include/bits/signum.h. To the best of my understanding this is
caused by finding a pattern which contains "SIG" in that file. My quick and
dirty solution was to manually override config.cache zsh_cv_path_signal_h
and running confiure and then make again. There should be a better way
however.
Arnon
reply other threads:[~2000-12-19 7:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=NDBBIOJAMKEKHLKCFJPNKEGICCAA.arnon@microtal.com \
--to=arnon@microtal.com \
--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).