public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Sam Edge <sam.edge@gmx.com>
To: cygwin@cygwin.com
Subject: Re: Unable to execute Cygwin application within UDF format
Date: Fri, 27 May 2022 18:41:49 +0100	[thread overview]
Message-ID: <2f867d27-b135-2af8-9dbb-458812b20b7c@gmx.com> (raw)
In-Reply-To: <20220527181849.6baaa5d9e8446f3e7d23cbee@nifty.ne.jp>

On 27/05/2022 10:18, Takashi Yano wrote:

> On Fri, 27 May 2022 16:47:09 +0800
> Sam Lin wrote:
>> I have also successfully executed that is to move cygwin1.dll to the root
>> directory to execute.
>>
>> Will cygwin1.dll be supported to execute in UDF format in the future?
> As I wrote earlier, it doesn't matter that the file system
> is UDF. cygwin1.dll 3.2.0 and later seems to cause problems
> if it is placed in the root directory.
>
> Even with UDF format, the problem does not occur if hello.exe
> and cygwin1.dll are placed in any directory other than root
> directory.

Perhaps the Cygwin DLL is trying to identify the Cygwin root directory
as one higher than its own location so that it can locate /etc/fstab
etc. If it's in the root of a drive maybe it's getting confused. Create
an x:\bin\ directory (where x is the drive letter of the UDF device)
into which to place cygwin1.dll and the executable.

--
Sam Edge



      parent reply	other threads:[~2022-05-27 17:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-27  3:36 Sam Lin
2022-05-27  4:31 ` Takashi Yano
2022-05-27  8:43   ` Takashi Yano
2022-05-27  8:47   ` Sam Lin
2022-05-27  9:18     ` Takashi Yano
2022-05-27 10:51       ` Takashi Yano
2022-05-27 12:28         ` Takashi Yano
2022-05-27 12:36           ` Takashi Yano
2022-05-28 13:22             ` Ken Brown
2022-05-28 14:25               ` Takashi Yano
2022-05-27 17:41       ` Sam Edge [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=2f867d27-b135-2af8-9dbb-458812b20b7c@gmx.com \
    --to=sam.edge@gmx.com \
    --cc=cygwin@cygwin.com \
    --cc=sam.edge@noreply \
    /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).