X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:reply-to:subject:to:references:from:message-id :date:mime-version:in-reply-to:content-type :content-transfer-encoding; q=dns; s=default; b=yahW8qIeEU0/BqbA KuOP9RhIHj6m0DJ25LR6BmPpUh/BVrJsujgACufOQIlFuJ+1y9wJVuf1R0zLhFPY s5eQoSwdmlcQXbfDvY8TNzlRJPRLsTnNKuljQulv8zbulZcA9iQaFw7/NE4Hg91e 6C4eKl0TTHasWvuVZQTCqKKvrs0= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:reply-to:subject:to:references:from:message-id :date:mime-version:in-reply-to:content-type :content-transfer-encoding; s=default; bh=ELKfu/3Mbvlqm0dnG+BPSE OgEX8=; b=j0SohlIH9T27yuziKRXoWHqVXzCQ0kU/TCaBqnZtTxGrNzvKyLdfcJ UCBoAjC1fAFcB178e0noLiMBe2lebWZUNLIKR3R2TMPdY0x6Lu9PlRUDh29USFtM kOI2f0lbUYbV4ImgsTMx/rUAHk97H8BzdJg7pVGo5DmeEoP2j/MbU= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-3.2 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 spammy=UD:htm, msys, endings X-HELO: smtp-out-no.shaw.ca Reply-To: Brian DOT Inglis AT SystematicSw DOT ab DOT ca Subject: Re: Problem with mksh-56c-1 mksh and DOS path names ( CYGWIN 3.0.7(0.338/5/3)) To: cygwin AT cygwin DOT com References: <000001d50a65$b3da71f0$1b8f55d0$@pinky.co.uk> From: Brian Inglis Openpgp: preference=signencrypt Message-ID: <520125af-099d-fc0c-b460-9c588fb64234@SystematicSw.ab.ca> Date: Tue, 14 May 2019 20:10:19 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <000001d50a65$b3da71f0$1b8f55d0$@pinky.co.uk> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-IsSubscribed: yes On 2019-05-14 08:59, chris DOT day AT pinky DOT co DOT 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 AT edmund:chrisd > cd E:/temp > /usr/bin/mksh: cd: /home/chrisd/E:/temp: No such file or directory > Running an older version > chrisd AT edmund:chrisd > cd E:/temp > chrisd AT 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