Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <435EE3A9.4050907@byu.net>
Date: Tue, 25 Oct 2005 20:02:17 -0600
From: Eric Blake <ebb9 AT byu DOT net>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: another manifestation of the .. bug
References: <435E2E2B DOT 9090306 AT byu DOT net> <20051025132731 DOT GX27476 AT calimero DOT vinschen DOT de>
In-Reply-To: <20051025132731.GX27476@calimero.vinschen.de>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Corinna Vinschen on 10/25/2005 7:27 AM:
>>I would much rather see a fix in cygwin so that coreutils would work out
>>of the box in this case.
>>
> 
> And I really can't see how "one testcase fails because Cygwin allows
> something which should fail according to POSIX" qualifies for "coreutils
> doesn't work out of the box on Cygwin".  Does the coreutils testsuite
> not allow per-target XFAILs?

Coreutils already won't pass the testsuite out of the box on cygwin due to
other problems, where I am also maintaining cygwin-specific patches; my
point was that if cygwin is ever fixed, it is one less workaround needing
my maintainence.  As for the coreutils testsuite, it does not have
per-target XFAILs, but does have the ability to SKIP tests that are known
to be invalid if various pre-screening tests show that a platform won't
support the feature being tested.  However, among all the platforms that
coreutils is currently ported to, my understanding is that cygwin is the
only platform that would need such an exemption to skip such tests due to
the lack of POSIX semantics.

Also, it is possible to write a wrapper around stat() that will give POSIX
semantics to .., using intermediate stat() and readlink() calls if the
string contains "/..".  Someday, I might attempt that task, to see what
sort of impact POSIX semantics has when done at the application layer
instead of the cygwin layer.

- --
Life is short - so eat dessert first!

Eric Blake             ebb9 AT byu DOT net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDXuOp84KuGfSFAYARAruMAJ9af2HA4inDT4sd3nFnNaTjOp7G4ACgzWnb
may3d4cT0QydA5/aJuRR9X8=
=lcMw
-----END PGP SIGNATURE-----

--
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/