zsh-workers
 help / color / mirror / code / Atom feed
From: Thorsten Meinecke <kaefer@aglaia.snafu.de>
To: zsh-workers@math.gatech.edu
Subject: signames.h broken under Linux 1.3.0 and later
Date: Tue, 11 Jul 1995 18:16:14 +0200 (MET DST)	[thread overview]
Message-ID: <m0sVhyp-00007AC@aglaia.snafu.DE> (raw)

As of Linux kernel release 1.3.0, the machine-dependent signal
macro definitions were moved from /usr/include/linux/signal.h to
/usr/include/asm/signal.h, where asm is actually a link to the
appropriate architecture's subdirectory (named asm-alpha, asm-i386,
asm-m68k and so on). 

If compiled right away, zsh does have funny hangs in strlen() -
I discovered this with a debugger -, because printjobs() in jobs.c
doesn't guard against out-of-bounds access to the sigmsg[] array.

Maybe there is some relation to the signalling problems reported
under HP-UX and other OS. Can someone experiencing these problems
confirm that signames.h was generated properly?

Anyway, the fix for configure.in is included below. I added the
grep test because the file /usr/include/asm/signal.h did exist
under older Linux releases too.

This is for zsh-2.6-beta10.


*** configure.in.orig	Sat Jul  1 00:05:02 1995
--- configure.in	Tue Jul 11 16:57:34 1995
***************
*** 355,365 ****
  dnl Where is <signal.h> located?  Needed as input for signals.awk
  AC_MSG_CHECKING(where signal.h is located)
  for SIGNAL_H in /usr/include/bsd/sys/signal.h   dnl Next
!                 /usr/include/linux/signal.h     dnl Linux
                  /usr/include/sys/signal.h       dnl Almost everybody else
                  /dev/null;                      dnl Just in case we fall through
  do
!   test -f $SIGNAL_H && break
  done
  AC_MSG_RESULT($SIGNAL_H)
  AC_SUBST(SIGNAL_H)dnl
--- 355,368 ----
  dnl Where is <signal.h> located?  Needed as input for signals.awk
  AC_MSG_CHECKING(where signal.h is located)
  for SIGNAL_H in /usr/include/bsd/sys/signal.h   dnl Next
!                 /usr/include/asm/signal.h       dnl Linux 1.3.0 and above
!                 /usr/include/linux/signal.h     dnl Linux up to 1.2.11
                  /usr/include/sys/signal.h       dnl Almost everybody else
                  /dev/null;                      dnl Just in case we fall through
  do
!   test -f $SIGNAL_H && \
!   grep -q '#[ 	]*define[ 	][ 	]*SIG[0-9A-Z]*[ 	]*[0-9][0-9]*' $SIGNAL_H && \
!   break
  done
  AC_MSG_RESULT($SIGNAL_H)
  AC_SUBST(SIGNAL_H)dnl

-- 
Thorsten Meinecke
<kaefer@aglaia.snafu.de>


                 reply	other threads:[~1995-07-11 16:25 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=m0sVhyp-00007AC@aglaia.snafu.DE \
    --to=kaefer@aglaia.snafu.de \
    --cc=zsh-workers@math.gatech.edu \
    /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).