Hi Collin,
> $ gnulib-tool --create-testdir --dir testdir1
> ^C
> $
It does not print any diagnostic. While gnulib-tool.sh and
subprocesses do print a diagnostic:
$ rm -rf ../testdir1; ./gnulib-tool.sh --create-testdir --dir=../testdir1
--single-configure stdbit-h
Module list with included dependencies (indented):
c99
extern-inline
gen-header
std-gnu11
stdbit-h
stdbit-h-tests
stdbool
stdbool-tests
File list:
lib/dummy.c
lib/stdbit.c
lib/stdbit.in.h
m4/00gnulib.m4
m4/c-bool.m4
m4/extern-inline.m4
m4/gnulib-common.m4
m4/std-gnu11.m4
m4/stdbit_h.m4
m4/zzgnulib.m4
tests/macros.h
tests/test-stdbit-h.c
tests/test-stdbool.c
executing aclocal -I glm4
^Cautom4te: error: /usr/bin/m4 terminated by signal: 2
caught signal SIGINT
$ rm -rf ../testdir1; ./gnulib-tool.py --create-testdir --dir=../testdir1
--single-configure stdbit-h
Module list with included dependencies (indented):
c99
extern-inline
gen-header
std-gnu11
stdbit-h
stdbit-h-tests
stdbool
stdbool-tests
File list:
lib/dummy.c
lib/stdbit.c
lib/stdbit.in.h
m4/00gnulib.m4
m4/c-bool.m4
m4/extern-inline.m4
m4/gnulib-common.m4
m4/std-gnu11.m4
m4/stdbit_h.m4
m4/zzgnulib.m4
tests/macros.h
tests/test-stdbit-h.c
tests/test-stdbool.c
executing aclocal -I glm4
executing autoconf
executing autoheader
^Cautom4te: error: /usr/bin/m4 terminated by signal: 2
autoheader: error: '/usr/bin/autom4te' terminated by signal: 2
Can you make gnulib-tool.py print a diagnostic in this case as well?
It does not need to be exactly "caught signal SIGINT", like bash does.
Just an indication that
- gnulib-tool.py
- is being terminated
- due to a signal 2.
Preferrably formatted in the same way as the other fatal errors, i.e.
starting with
'%s: *** ' % APP['name']
The exit code is nonzero (128 + 2); this is good.
Bruno
