X-Spam-Check-By: sourceware.org X-ExtLoop1: 1 X-IronPort-AV: i="4.09,471,1157353200"; d="scan'208"; a="151393352:sNHT1353350285" Message-ID: <456CA471.6070206@tapil.com> Date: Tue, 28 Nov 2006 16:04:49 -0500 From: Michael Adler User-Agent: Thunderbird 1.5.0.8 (Windows/20061025) MIME-Version: 1.0 To: Yitzchak Scott-Thoennes CC: cygwin AT cygwin DOT com Subject: Re: Perl output dropped when invoking itself References: <4559F85D DOT 50404 AT tapil DOT com> <20061128184649 DOT GB3972 AT efn DOT org> In-Reply-To: <20061128184649.GB3972@efn.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Yitzchak Scott-Thoennes wrote: > On Tue, Nov 14, 2006 at 12:09:49PM -0500, Michael Adler wrote: > >> I'm having Perl I/O problems on one machine that keep me from getting >> CPAN installations to work. On this machine if I execte: >> >> perl -e 'print `perl -e "require 5; print qq{VER_OK\n}"`;' >> >> from bash there is no output. On all my other machines it prints >> VER_OK. ExtUtils::MM_Unix does this test and fails. >> >> I've looked at all environment variables I can think of, especially >> CYGWIN, and it is identical on a machine that works and one that fails. >> Cygwin is up to date on both and Perl version is 5.8.7. I've tried >> multiple values of the PERLIO variable with no success. Replacing the >> inner invocation of perl with some other command, like cat of a file, >> works on both machines! I tried blowing away the entire perl >> environment and reinstalling. >> >> I assume I'm missing something simple. Hints would be appreciated. >> > > What do these do: > perl -e 'print `perl -v`' > perl -e 'print `perl -f -e "require 5; print qq{VER_OK\n}"`;' > perl -e 'print `perl -f -e "print qq{VER_OK\n}"`;' > Thank you for the reply. I did finally figure it out. Some post-install script had apparently failed in the past and /bin/sh was old -- it wasn't bash. -Michael -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/