Le 07/10/2013 00:33, Christopher Faylor a écrit :
On Sun, Oct 06, 2013 at 01:06:52PM +0200, Robert Klemme wrote:
On Sun, Oct 6, 2013 at 10:49 AM, Francis ANDRE <francis.an...@easynet.fr> wrote:
Hi Robert
The problem here is that the string of the target directory is computed by
another tool -- Mercurial in this case -- and that Mercurial returns a
absolute windows style path as
Z:/DEV/OpenJDK_7u40/hotspot
which seems to be relative in Unix world but which is absolute in the
Windows world.
Moreover, when using the bash shell, the command
FrancisANDRE@idefix /cygdrive/c/Cygwin
$ cd Z:/DEV/OpenJDK_7u40/hotspot
moves the cwd without error to
FrancisANDRE@idefix /cygdrive/z/DEV/OpenJDK_7u40/hotspot
So why the ksh cannot do the same?
That question ksh developers or cygwin package maintainers should be
able to answer. They might just use different syscalls which vary in
behavior on Cygwin. You could try to find that out with strace.
More likely it is just because ksh automatically prepends the current
working directory to something that it considers to be relative.
I know I'm a broken record on the subject but it is not a requirement that
Cygwin tools to be able to understand MS-DOS paths. It's possible that they
do, by coincidence, understand them but it is not a given that they will.
Can I have a official statement from Cygwin about this? ie that bash is
supporting MS-DOX path by accident and ksh won't and that is not a requirement
of Cygwin?
Or
Can Cygwin adds the understanding of absolute DOS path as a requirement and fix
the ksh stuff?
Francis
cgf
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
