This is the mail archive of the cygwin@sourceware.cygnus.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: Sort of solved (was: Re: What are these cd errors?)


At 02:52 PM 10/1/99 +0200, Kai Henningsen wrote:
>Solved! See below.
>
>On 1 Oct 99, at 11:13, Kai Henningsen wrote:
>
>> Huh?!
>> 
>> The *same* bash cannot do this cd when called as sh?!
>> 
>> Here's  cygcheck -s -v -r output - essentially, this is a fresh install 
>> of B20.1 plus the cygwin1-19990115 DLL:
>
>I also tried this with the original DLL, and with the one from the 
>19990929 snapshot, and both show the exact same problem.
>
>Mounting the drive it's happening on (so the pathname becomes 
>/f/... instead of //f/...) does not change anything, either.
>
>Nor does ash have less trouble.
>
>
>HAH! Found it. Neither bash-called-as-sh nor ash can cope with 
>the CDPATH. They cannot even cope with a CDPATH set to "."!  
>This sure doesn't happen under Linux.
>
>Regards - Kai Henningsen
>

Huh?  I've used CDPATH under cygwin for *years* and I've never seen any
problems cding anywhere.  Perhaps it would be best if you passed along
your environment with a description of what you are doing since it seems
there are some definite environment issues here.


Larry Hall                              lhall@rfk.com
RFK Partners, Inc.                      http://www.rfk.com
118 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX
                                        (508) 560-1285 - cell phone

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]