Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive:	<http://sourceware.cygnus.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help:	<mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID:	<38567DA3.2C5F1A76@veritas.com>
Date:	Tue, 14 Dec 1999 09:25:55 -0800
From:	Bob McGowan <Robert DOT McGowan AT veritas DOT com>
Organization:	VERITAS Software
X-Mailer:	Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language:	en
MIME-Version:	1.0
To:	Andre Oliveira da Costa <costa AT cade DOT com DOT br>
CC:	Cygwin <cygwin AT sourceware DOT cygnus DOT com>
Subject:	Re: fileutils 4.0
References:	<000001bf461e$4e958c10$8400000a AT costa DOT cadenet DOT com DOT br>

Andre,

Andre Oliveira da Costa wrote:
> 
> Hi,
> 
> has anybody out there compiled version 4.0 of fileutils for cygwin? The
> B20.1 version of cygwin that I installed came with version 3.16 of
> fileutils, and I downloaded the sources of version 4.0 to give it a try. The
> configure script ran with no noticeable problems, and so did the
> compilation. But, during the 'make check' phase, something bad happened:
> 
> [snip]
> Making check in cp
> /tmp/fileutils-4.0/tests/cp
> make  check-TESTS
> PASS: backup-1
> /tmp/fileutils-4.0/tests/cp/b
> PASS: no-deref-link1
> /tmp/fileutils-4.0/tests/cp/b
> PASS: no-deref-link2
> PASS: no-deref-link3
> PASS: backup-is-src
> FAIL: same-file

I'd guess that this is a case-sensitivity (or non-sensitivity, in this
case) issue.  The tests were made to work under UNIX so if any of the
filenames differ only in the case of the alpha characters, the test will
fail on any Windows system.

You could change the test scripts or simply ignore any errors relating
to "same-file" statements.  Ignoring the errors may be difficult if the
make exits for each error condition.  You could try using the -i to
ignore errors or a -k to abandon work on the current item but continue
with the next.  Check the man page for make for details on the options.

Good luck.

-- 
Bob McGowan
Staff Software Quality Engineer
VERITAS Software
rmcgowan AT veritas DOT com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -