On Wed, May 11, 2005 at 04:49:52PM -0700, David Rothenberger wrote: >On 5/11/2005 3:41 PM, Michael Schaap wrote: >>The patch as-is doesn't compile for me, though, I presume because >> char **envp = (char **) cygwin_internal (CW_ENVP); >>uses a not-yet-released Cygwin enhancement. But when I change it to the >>simpler and more standard >> char **envp = environ; >>it compiles and works fine, both under mount -X and normally. > >Doh! I didn't read Chris' last comment carefully enough. Yes, copying >from environ is much more reasonable. > >>(At first I was a bit suspicious of the logic - it only sets those >>Windows variables that are not currently set, so what about variables >>that were changed or deleted within Cygwin? - but it looks like the >>Windows environment isn't the standard pre-Cygwin user environment, but >>a minimal one with only PATH and SYSTEMROOT set, so it actually does >>behave optimally this way - it sets all other variables when running >>under mount -X, and sets nothing otherwise.) > >Right. The main reason I did that, though, was because copying the >Cygwin PATH to the Windows environment caused lots of core dumps.
You're going to have to convert the PATH to windows form before adding it to the environment. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
