From:	sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id:	<10302090623.AA20746@clio.rice.edu>
Subject:	Re: Take on __solve_symlinks()
To:	djgpp-workers AT delorie DOT com
Date:	Sun, 9 Feb 2003 00:23:11 -0600 (CST)
In-Reply-To:	<200302081513.h18FD6b24583@speedy.ludd.luth.se> from "ams@ludd.luth.se" at Feb 08, 2003 04:13:06 PM
X-Mailer:	ELM [version 2.5 PL2]
Mime-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

OK, I'm guessing that we are talking about building and running
tests/libc/compat/unistd/xsymlink.exe

On my Win98 test box, I did a CVS update -d, did a make.
When I do this on Win98, I see failure just like test 3 below.  

> > Test 2: Solving e:../../../../../djgpp/tests/libc/compat/unistd/test1
> > Test 2 passed
> > Test 3: Solving e:../../../../../../djgpp/tests/libc/compat/unistd/test1
> > Test 3 failed - __solve_symlinks returns wrong resolved path
> > Returned path: e:/djgpp/tests/libc/compat/unistd/test1
> > Expected path: e:/djgpp/tests/libc/compat/unistd/file1
> > Tests that check __solve_symlinks() failure cases:
> > Test 1 passed
> > Test 2 passed
> > FAIL
> > I'm using WINDOZE 98, bash and CVS of today (030208).

(Except my path is c:/v204/djgpp/tests/libc/compat/unistd/ in the error msg).

However, on my Win2K box, doing the exact same thing, exact same directory
path, exact same file system type (FAT32):

Test 2 passed
Test 3: Solving c:../../../../../../../v204/djgpp/tests/libc/compat/unistd/test1
Test 3 passed
Tests that check __solve_symlinks() failure cases:
Test 1 passed
Test 2 passed
PASS

So, it definitely looks like a difference in OS behavior to me.

- Raw text -