Re: m4 error at startup

On Sat 15 Feb 2020 at 18:26:25 -0600, Matthew D. Fuller wrote:
> So, maybe the m4 process is inheriting our SIG_IGN there, and isn't
> prepared for that to be the case?  You could try commenting out the

I suspect you have something there: my manual page for sigaction(2)
says:

                    The execve(2) system call reinstates the default action
                    for all signals which were caught and resets all signals
                    to be caught on the user stack.  Ignored signals remain
                    ignored; the signal mask remains the same; signals that
                    restart pending system calls continue to do so.

-Olaf.
-- 
Olaf 'Rhialto' Seibert -- rhialto at falu dot nl
___  Anyone who is capable of getting themselves made President should on
\X/  no account be allowed to do the job.       --Douglas Adams, "THGTTG"

-----BEGIN PGP SIGNATURE-----

iQEcBAEBAgAGBQJeSbTbAAoJEJmJxkVhw/vTZiEH/2C0A2MaIn+E/idpqhVQqI6M
FCNtzJi1cSXMS7jcl0KXU5DsQivu9G2j+E3RsAw4QGNxYXTU+2I7obW5UjOIlfsi
ARx4xrAVCepdGqSnbQc/6iZKRgdVVlcF8MRx3R7N7gcXaVgFYYpfjRMN0Jp5vgMC
UooKWtbDa8xEmfmcP3+2L4XlGQ2mzZNdMIKSXQakUuDpkZlgjvkZfTyaYmVChoxZ
toySxYfMPi3J3OkW00FsY+J24Qc7pDq679YSmXJVW+g3aOEQrbA6BgHfAnjaRxRw
mkbRHPUTUSXgosgMSR/jpqOK8DeAAdWOpzasRriFVBhvyAxndJcjrj75S9FL12I=
=CJmw
-----END PGP SIGNATURE-----