From: <ams AT ludd DOT luth DOT se>
Message-Id: <200302081513.h18FD6b24583@speedy.ludd.luth.se>
Subject: Re: Take on __solve_symlinks()
In-Reply-To: <200302081446.h18EkiQ24457@speedy.ludd.luth.se> "from ams@ludd.luth.se
 at Feb 8, 2003 03:46:44 pm"
To: djgpp-workers AT delorie DOT com
Date: Sat, 8 Feb 2003 16:13:06 +0100 (CET)
X-Mailer: ELM [version 2.4ME+ PL78 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII
X-MailScanner: Found to be clean
X-MailScanner-Information: Please contact the ISP for more information
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
Precedence: bulk

According to ams AT ludd DOT luth DOT se:
> According to Laurynas Biveinis:
> > Maybe it's W98 vs W2K thing? Could somebody else with W98/W2K test
> > tests/libc/compat/unistd/xsymlink.c to see if it fails? In any case, I'm
> 3. It fails here:
> Running __solve_symlinks() and readlink() testsuite:
> Tests that check __solve_symlinks() works:
> Test 1 passed
> Test 2 passed
> Test 3 passed
> Test 4 passed
> Test 5 passed
> Test 6 passed
> Test 7 passed
> Test 8 passed
> Test 9 passed
> Test 10 passed
> Test 11 passed
> Test 12 passed
> Test 13 passed
> Tests that check __solve_symlinks() based on current directory:
> Test 1: Solving e:/djgpp/tests/libc/compat/unistd/../../../../../djgpp/tests/libc/compat/unistd/test1
> Test 1 passed
> 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).

I need to correct myself. CVS of today plus DXE patches from Charles,
restrict hacks in headers, a small personal djasm hack and
CBFalconer's malloc. I deem that none of those affect symlink tests.

bash 2.04.7(1)-release, gcc 2.953 (shouldn't it say 2.95.3?) and
as and ld 2.12.1.


Right,

						MartinS