zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@ibmth.df.unipi.it>
To: Bernd Eggink <eggink@uni-hamburg.de>,
	zsh-workers@sunsite.auc.dk (Zsh hackers list)
Subject: Re: signames problem
Date: Wed, 24 Feb 1999 14:00:56 +0100	[thread overview]
Message-ID: <9902241301.AA16501@ibmth.df.unipi.it> (raw)
In-Reply-To: "Bernd Eggink"'s message of "Wed, 24 Feb 1999 12:37:43 NFT." <36D3E487.7B42C369@uni-hamburg.de>

> In SuSE Linux 6.0, zsh-3.1.5-pws-9 doesn't know any signames.
> 
> Possibly because the former /usr/include/asm/signal.h has moved to
> /usr/include/signum.h !?

configure has changed so it's now supposed to work it out from the files
that `#include <signal.h>' actually includes.  Anything with `sig' in it is
tested. Is zsh_cv_path_signal_h set to /dev/null in config.cache?  What
does the new code (I've replaced $CPP with gcc -E, $AWK with awk assuming
that's what's used):

echo "#include <signal.h>" > nametmp.c
sigfile_list="`gcc -E nametmp.c |
sed -n 's/^#[ 	].*\"\(.*\)\"/\1/p' |
sed 's/\\\\\\\\/\//g' |
awk '{ if (\$1 ~ \"sig\") files[\$1] = \$1 }
  END { for (var in files) print var }'`"

produce for $sigfile_list?  (There's a space and a tab in the empty [ ]
which does funny things if you paste it into zsh.)

I can add /usr/include/signum.h to the fallback list anyway, but I'd like
to find out why it can't find it.

-- 
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-02-24 13:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-24 11:37 Bernd Eggink
1999-02-24 13:00 ` Peter Stephenson [this message]
1999-02-24 14:41   ` Bernd Eggink
1999-02-24 15:01     ` 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=9902241301.AA16501@ibmth.df.unipi.it \
    --to=pws@ibmth.df.unipi.it \
    --cc=eggink@uni-hamburg.de \
    --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).