[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [patch] fix "broken pipe" message from lseek test

From: Ben Pfaff
Subject: Re: [patch] fix "broken pipe" message from lseek test
Date: Sat, 20 Feb 2010 12:44:50 -0800
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux)

Bruno Haible <address@hidden> writes:

>> I noticed that (sometimes?) the lseek check prints a "broken
>> pipe" message in the middle of "configure" output, e.g.
>>         checking whether lseek detects pipes... ../configure: line 30326: 
>> echo: write error: Broken pipe
>> as reported here under step 19:
>>         http://benpfaff.org/~blp/pspp-master/20100220040512/
> Below is a proposed fix (untested).

I tested it, but I still see the "broken pipe" error with it.  I
verified that "configure" was updated from your patch:

  if test -s conftest$ac_exeext \
             && ./conftest$ac_exeext < conftest.$ac_ext \
             && { : "Avoid error message from bash."; \
                  : "See func_reset_sigpipe in gnulib-tool."; \
                  if test -n "$BASH_VERSION"; then trap - SIGPIPE; fi; \
                  echo hi | ./conftest$ac_exeext; \
                  test $? = 1; \
                }; then

Could the test program, instead, just call pipe() itself and try
to seek on it?  Then there would be no need for the shell to
create the pipe or to try to write to it.  If this would work I'd
be happy to write up a patch.
"Let others praise ancient times; I am glad I was born in these."
--Ovid (43 BC-18 AD)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]