On Mon, Oct 22, 2001 at 11:43:32AM +0200, Pavel Tsekov wrote: >Ok, here is what I've found about the execvp problem I mentiond in an >earlier post: > >Assuming the simple execvp invocation and the path at the end of the >message we have a problem. The problem is introduced by the newlib >execvp implementation. > >Before searching the path for the executable specified, execvp checks >if the path is posix or win32 style, which involves checking the >content of the PATH environment variable for the semicolon character >and also checking if the contents of the PATH starts with a single >letter followed by a semicolon (dos style drive) - >cygwin_posix_path_list_p. > >Based on the result of cygwin_posix_path_list_p execvp decides which >symbol to use as a path separator - semi- colon for win32 style path or >colon for posix style path. > >Now assume the following PATH string converted to posix - since on >application startup, if the user hasnt modified the PATH by himself, >the PATH is posix style: > >PATH=c:/jdk1.3.1/bin:/usr/local/bin:...:c:/usr/local/emacs/bin
I am not entirely sure what you're saying here, but this isn't a POSIX PATH. Cygwin always converts a Windows path to a POSIX path on startup. A getenv() will return a posix path. However, if you change a PATH to a windows path inside an application, then you will confuse cygwin quite a bit. cgf -- 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/
