Hmm, I don't quite follow you here. The PATH variable is not set by me, it's set by cygwin, right?
The PATH contains the entry /cygdrive/c/WINDOWS/system32 but that makes no sense if "check_case:strict" is present in the CYGWIN variable initialising cygwin, right? So, in some way, there's a clash here, regardless of my specific issue here with running the binutils testsuite for ld, right? Cheers, /ChJ -----Original Message----- From: Larry Hall (RFK Partners, Inc) [mailto:[EMAIL PROTECTED]] Sent: Friday, October 11, 2002 2:43 PM To: Christian Jönsson; 'cygwin' Subject: RE: binutils 20021009 cvs trunk on cygwin: ld failuers At 03:12 AM 10/11/2002, Christian Jönsson wrote: >Hmm, looking at PATH, I get this: > >$ printenv PATH >/usr/local/gcc-binutils/bin:/usr/local/bin:/usr/bin:/bin:/cygdrive/c/Pr >o >gram/Microsoft Visual Studio/Common/Tools:/cygdrive/c/Program/Microsoft >Visual Studio/Common/Msdev98/BIN:/cygdrive/c/Program/Microsoft Visual >Studio/DF98/BIN:/cygdrive/c/Program/Microsoft Visual >Studio/VC98/BIN:/cygdrive/c/WINDOWS/system32:/cygdrive/c/WINDOWS:/cygdr i >ve/c/WINDOWS/System32/Wbem:/cygdrive/c/Program/DELADE~1/MGISHA~1/Video: / >cygdrive/c/Program/Delade filer/Adaptec >Shared/System:/cygdrive/c/program/matlab6p5/bin/win32:/cygdrive/c/Progr a >m/Microsoft Visual >Studio/Common/Tools/WinNT:/cygdrive/c/Program/Microsoft Visual >Studio/Common/MSDev98/Bin:/cygdrive/c/Program/Microsoft Visual >Studio/Common/Tools:/cygdrive/c/Program/Microsoft Visual >Studio/VC98/bin:/usr/X11R6/bin > >chj@D90V2D0J /usr/local/src/gcc-binutils/trunk/objdir-binutils/ld >$ > >And from testing /cygdrive/c/WINDOWS/system32 >$ ls /cygdrive/c/WINDOWS/system32 >ls: /cygdrive/c/WINDOWS/system32: No such file or directory > >chj@D90V2D0J /usr/local/src/gcc-binutils/trunk/objdir-binutils/ld >$ > >But testing /cygdrive/c/WINDOWS/SYSTEM32 > >$ ls /cygdrive/c/WINDOWS/SYSTEM32/user32.dll >/cygdrive/c/WINDOWS/SYSTEM32/user32.dll > >chj@D90V2D0J /usr/local/src/gcc-binutils/trunk/objdir-binutils/ld >$ > >So, I still guess this is a cse issue... OK, now I understand what you mean by a "case issue". But let's turn this around. Why *wouldn't* there be a "case issue"? You've specified in your CYGWIN environment variable "check_case:strict". If you want the case- preserving files but case-insensitive file comparisons, remove this from your CYGWIN environment variable and reload the Cygwin DLL. You'll get the standard Windows behavior then. Larry Hall [EMAIL PROTECTED] RFK Partners, Inc. http://www.rfk.com 838 Washington Street (508) 893-9779 - RFK Office Holliston, MA 01746 (508) 893-9889 - FAX -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
