public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Chris Faylor <cgf@cygnus.com>
To: "Larry Hall (RFK Partners, Inc)" <lhall@rfk.com>
Cc: "cygwin@sourceware.cygnus.com" <cygwin@hotpop.com>
Subject: Re: No such file or directory
Date: Sun, 26 Mar 2000 09:06:00 -0000	[thread overview]
Message-ID: <20000326120537.A13807@cygnus.com> (raw)
In-Reply-To: <4.3.2.20000325225920.00d3c7b0@pop.ma.ultranet.com>

On Sat, Mar 25, 2000 at 11:07:27PM -0500, Larry Hall (RFK Partners, Inc) wrote:
>At 10:48 PM 3/25/00, Chris Faylor wrote:
>>On Sat, Mar 25, 2000 at 10:40:13PM -0500, Larry Hall (RFK Partners, Inc) wrote:
>> >Looks to me like your big problem is the install program which assumes the 
>> >UNIX convention of executables without extensions (.exe).  It looks for
>> >remind and not remind.exe, which is what exists.
>>
>>I wonder if it would really be a big deal if cygwin, by default, found a
>>file "foo.exe" if there was no existing file "foo".
>>
>>We keep running into this problem and I wonder if implementing this in
>>cygwin would solve more problems than it causes.
>
>Its been a while but isn't there already something in there that does the
>reverse for executables in general?  I should go looking.  My guess is what
>I'm remembering is a related but different topic.

The stat() function call will locate a file with no extension and one
with a .exe extension.  Obviously, the spawn() and exec() calls do
something similar.

The problem is that if you do a stat("ls", &st) it will succeed but
open("ls", whatever) will fail.

>But I agree with you.  This is a common "problem" of the
>configure/make/ install sequence of GNU packages on Cygwin and,
>although its not a big deal to work with once you understand it, it
>does generate list traffic regularly.  I guess I'm wondering why the
>alternate install script solution that has been "floated" in the past
>is not something Cygwin uses now.  I admit I never looked that closely
>at it.  If it does the right job, the thing that I think is good about
>it is that it targets the problem in the context of installs, which
>seems to be where the problem lies...

install.exe in the next version of cygwin will be ".exe" aware.

It hasn't been done before now because, ah, we haven't had an official
net release in a long time.  The Cygwin CD version does use this version
of install, however.

cgf


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

  reply	other threads:[~2000-03-26  9:06 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-24 14:41 Eric Goforth
2000-03-25 13:07 ` Terry Lincoln
2000-03-25 19:44 ` Larry Hall (RFK Partners, Inc)
2000-03-25 19:50   ` Chris Faylor
2000-03-25 20:11     ` Larry Hall (RFK Partners, Inc)
2000-03-26  9:06       ` Chris Faylor [this message]
2000-03-27  7:25         ` Larry Hall (RFK Partners, Inc)
  -- strict thread matches above, loose matches on Subject: below --
2020-07-06 12:57 Billie Healy
2020-07-06 16:41 ` ASSI
2020-07-06 16:59   ` Eliot Moss
2008-06-26  9:07 pirracas77
2008-06-26  9:35 ` Dave Korn
2008-06-26 15:37   ` pirracas77
     [not found] <f9dce6b30707120418yc2bea1axa699bea2d824e176@mail.gmail.com>
2007-07-12 12:38 ` Larry Hall (Cygwin)
2004-12-06 23:49 no " Kevin Smith
2002-12-13 16:03 No " ganglio
2000-03-27  6:01 Earnie Boyd
2000-03-27  7:56 ` Chris Faylor
2000-03-27  5:56 Earnie Boyd
2000-03-27  7:51 ` Chris Faylor
2000-03-26 16:11 Rick Rankin
2000-03-26 15:02 Rick Rankin
2000-03-26 15:09 ` Chris Faylor
2000-03-25 20:13 Rick Rankin
2000-03-26  9:13 ` Chris Faylor
2000-03-27 14:23   ` Michael Hirmke
2000-01-15  4:50 Slate
2000-01-15  8:00 ` Heinz-Juergen Oertel

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=20000326120537.A13807@cygnus.com \
    --to=cgf@cygnus.com \
    --cc=cygwin@hotpop.com \
    --cc=lhall@rfk.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).