On Mon, Feb 05, 2007 at 06:23:11AM -0700, Eric Blake wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> According to Eric Blake on 2/4/2007 9:45 PM:
> >
> > I'm thinking that I'll just change the test to use SIGKILL only, since we
> > have proven that SIGPIPE is risky to rely on portabl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Eric Blake on 2/4/2007 9:45 PM:
>
> I'm thinking that I'll just change the test to use SIGKILL only, since we
> have proven that SIGPIPE is risky to rely on portably. M4 doesn't have a
> bug, so much as the testsuite.
Like so:
2007-02-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Eric Blake on 2/4/2007 9:26 PM:
> Probably something to do with inherited signal handling and python's
> choice of what signals to ignore. I don't know whether the bug is in
> python for ignoring a signal that the child process expects to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Albert Chin on 2/4/2007 7:55 AM:
> 'make check' works fine when run from a shell. It works fine when run
> from system() under Perl. However, when run under Python (2.2.3,
> 2.3.4, 2.4.2), "os.system('make check')" fails with:
> Checking
