Mail Archives: djgpp-workers/2003/02/08/07:40:50
Richard Dawe wrote:
>>Very interesting, given that the first thing __solve_symlink does is to
>>copy __symlink_path to __real_path. I don't see how this patch could
>>make any difference, and it doesn't at my sandbox. The testcase gives
>>correct results both ways. I strongly suspect that we are testing two
>>different versions of __solve_symlinks... Maybe you could try copy
>>somewhere the directory with testsuite sources, copy here up to the date
>>CVS version of __solve_symlinks and add it to makefile ?
> I've just tried building with another CVS that has _no_ source changes and
> only changes to the Cygnus test suite (C++ build fixes). I just did a 'cvs
> update -dA', so it has your latest check-in for xsymlink.c ("Rearrange symlink
> loop detection"). This is my "reference" read-only tree. The test fails there
I've created separate clean DJGPP installation with CVS libc and binaries
from clio.rice.edu dated 2003-02-01 and symlink testsuite still does not
fail here. Frankly, I think I've done everything I could at this point.
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
unable to debug it here, so I won't for now until someone gives a clue.
- Raw text -