[doughera@lafcol.lafayette.edu: Re: Perl 5.001/Linux ELF pipe.t error test 7]

Frank Bennett (fbennett@rumple.soas.ac.uk)
Mon, 17 Jul 95 23:43 GMT

Return-Path: <doughera@lafcol.lafayette.edu>
Date: Mon, 17 Jul 1995 14:07:34 -0400 (EDT)
From: Andy Dougherty <doughera@lafcol.lafayette.edu>
Sender: Andy Dougherty <doughera@lafcol.lafayette.edu>
Reply-To: Andy Dougherty <doughera@lafcol.lafayette.edu>
Subject: Re: Perl 5.001/Linux ELF pipe.t error test 7
To: Frank Bennett <fbennett@rumple.soas.ac.uk>
Cc: lwall@netlabs.com
In-Reply-To: <m0sXq7i-0006MhC@rumple.soas.ac.uk>
Mime-Version: 1.0

On Mon, 17 Jul 1995, Frank Bennett wrote:

> The subject line says most of it. I hope this is not an
> intrusion; I am a novice at C, and can't offer a solution to the
> problem that I've come across.
> I've just compiled Perl 5.001 under Linux 1.3.8, using GCC 2.7.0
> and version 5.0.9 of libc.
> The compilation went smoothly, but I get one failed test, the 7th
> test in pipe.t. (It looks like maybe this tests whether Perl will
> be able to provide error handling for a broken pipe condition
> (?).)

The problem is (apparently) that Linux uses more than one signal name for
a specific signal number. I don't know if this is just for the 1.3.x
series of kernels or not, but it appears to be a recent change. I'm also
not sure if this will continue to be the case for new kernels or if it will
go away, so I don't know if it's worth it to work hard in Configure &
perl to compensate.

For now, I'm not certain offhand if there's a graceful way to handle this
in perl itself, though it seems there ought to be.

Anyway, you can just change manually change the names in config.sh (e.g.
change IOT to ABRT) and to compensate for whatever duplicates are in

Hope this helps,