[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Why does sh in the build environment ignore SIGINT and SIGQUIT?
From: |
Foo Chuan Wei |
Subject: |
Why does sh in the build environment ignore SIGINT and SIGQUIT? |
Date: |
Sun, 22 May 2022 08:00:15 +0000 |
The shell in the environment where packages are built ignores SIGINT and
SIGQUIT. If I add `(invoke "sh" "-c" "trap")` to a custom build phase,
this output is produced during the build:
trap -- '' INT
trap -- '' QUIT
Why does the shell in the build environment need to ignore these two
signals?
For context, this affects the build of the smlnj package
(gnu/packages/sml.scm). The resulting executable seems to inherit the
signal dispositions of the shell where the executable is built, with the
result that CTRL-C is ignored at the sml REPL.