[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Trapping SIGINT?

From: Stepan Kasal
Subject: Trapping SIGINT?
Date: Fri, 14 Apr 2006 10:01:11 +0200
User-agent: Mutt/1.4.1i

  the Autoconf calls m4 with std input redirected from /dev/null:

2001-09-07  Akim Demaille
        * bin/autom4te.in (&handle_m4): `< /dev/null' so that GNU M4 1.5
        doesn't neutralize SIGINT, making autoconf etc. non interruptible.

Is this concern still valid?  Is it true that otherwise the command

m4 --nesting-limit=1024 --include=/usr/local/share/autoconf \
   --debug=aflq --fatal-warning --error-output=/tmp/am4tq25545/traces.0t \
   --trace=_m4_warn --trace=include --trace=m4_include \
   --trace=m4_pattern_allow --trace=m4_pattern_forbid \
   --reload-state=/usr/local/share/autoconf/m4sugar/m4sh.m4f \
   a.in >/tmp/am4tq25545/output.0t

would not be interruptible when run with m4 2.0?

(Do I understand correctly that m4-1.5 will probably never happen?)

Thank you in advance,
        Stepan Kasal

reply via email to

[Prev in Thread] Current Thread [Next in Thread]