From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Problem with mksh-56c-1 mksh and DOS path names ( CYGWIN 3.0.7(0.338/5/3))
Date: Wed, 15 May 2019 02:10:00 -0000 [thread overview]
Message-ID: <520125af-099d-fc0c-b460-9c588fb64234@SystematicSw.ab.ca> (raw)
In-Reply-To: <000001d50a65$b3da71f0$1b8f55d0$@pinky.co.uk>
On 2019-05-14 08:59, chris.day@pinky.co.uk wrote:
> I'm having some challenges with the latest version mksh (mksh-56c-1) and the
> support of DOS path names. Seems this is broken, although POSIX names work as
> expected.
> chrisd@edmund:chrisd > cd E:/temp
> /usr/bin/mksh: cd: /home/chrisd/E:/temp: No such file or directory
> Running an older version
> chrisd@edmund:chrisd > cd E:/temp
> chrisd@edmund:temp > pwd
> /cygdrive/e/temp
> I've noticed that the mksh Build.sh has moved the dospath handling to be OS/2
> specific, omitting Cygwin.
From the Changelog entries since the last Cygwin release 54, looks like all but
OS/2 now behave more like POSIX, using realpath, including Cygwin and Msys -
http://www.mirbsd.org/mksh.htm#clog
"R56c is a bugfix-only release everyone must upgrade to:
. [komh] Remove redundant OS/2-specific code, clean up others
. [komh, tg] Fix drive-qualified (absolute and relative) DOS-style path support
in realpath functionality, partially other places
. [tg] Don’t substitute ${ENV:-~/.mkshrc} result again
. [tg] Improve OS/2 $PATH (et al.) handling, drive-relative paths
...
R56 is a bugfix release with some experimental fixes:
...
. [komh] Exclude FAT/HPFS/NTFS-unsafe tests on OS/2 (and Cygwin/MSYS)
...
R55 is mostly a feature release with summary bugfixes:
...
. [tg] Add new standard variable PATHSEP (‘:’, ‘;’ on OS/2)
...
. [tg] Introduce build flag -T for enabling “textmode†on OS/2 (supporting CR+LF
line endings, but incompatible with mksh proper)
. [tg] Merge mksh-os2
..."
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
--
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
prev parent reply other threads:[~2019-05-15 2:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 15:00 chris.day
2019-05-15 2:10 ` Brian Inglis [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=520125af-099d-fc0c-b460-9c588fb64234@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).