Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Wed, 20 Jul 2005 18:54:13 -0700 (PDT) From: Andrew Ho X-X-Sender: andrew AT shell02 DOT corp DOT tellme DOT com To: Michael G Schwern Cc: Scott Bolte , "Gerrit P. Haase" , cygwin AT cygwin DOT com, makemaker AT perl DOT org, perl5-porters AT perl DOT org, petdance AT cpan DOT org Subject: Re: [perl-5.8.7] Perl regression tests fail when lib directory is present In-Reply-To: <20050720180419.GA16999@windhund.schwern.org> Message-ID: References: <200507200216 DOT j6K2G3IL011560 AT crag DOT niss DOT com> <20050720180419 DOT GA16999 AT windhund DOT schwern DOT org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Hello, MS>I would suggest working backwards though the CPAN versions of Test::Harness MS>until it works. Then we can better spot the change which caused this bug. MS>http://search.cpan.org/dist/Test-Harness/ I tested stepping down through versions of Test::Harness from CPAN. Version 2.42 is the latest version which passes "make test" for my simple test case at http://www.zeuscat.com/andrew/src/TestModule.tar.gz. Here are the diffs between 2.42 and 2.44, the next most recent version: http://www.zeuscat.com/tmp/test_harness_diff.txt http://www.zeuscat.com/tmp/test_harness_diff.html (colorized) I haven't peeked through the diff yet to figure out what the cuplrit is. Thanks for all the quick responses on this! Humbly, Andrew ---------------------------------------------------------------- Andrew Ho andrew AT tellme DOT com Staff Engineer 650-930-9062 Tellme Networks, Inc. http://www.tellme.com/ ---------------------------------------------------------------- -- 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/