Luke, I think the fundamental point that you're missing here is that
Cygwin is intended to be a subspecies of Unix, not a subspecies of Windows.
I'm not familiar with Ici, but if it currently has both Windows and Unix
versions, you should expect the Unix version, not the Windows version,
to be
2008/4/18, Luke Kendall:
> I'm afraid I may still be misunderstanding, sorry. Do you mean, move the
> ici directory to some place away from where the ici.exe lives?
Move it to /usr/lib/ici/ or /opt/lib/ici/ where it belongs to. As in
every other distro.
/opt/bin/ici/ is just plain stupid.
--
Rei
Luke Kendall wrote:
Larry Hall (Cygwin) wrote:
Luke Kendall wrote:
So I still think I asked for /opt/bin/ici to be executed by bash.
I'd be interested to know if I've misunderstood.
I think you did as well. And so does bash. But it's not going to allow
you to execute a directory, which is
I still don't get why you want the Cygwin version of ici to work like
the native Windows version. You have a Unix port - that's what the
Cygwin version should use as a model. The whole point of Cygwin is to
get Unixy behavior...
On 4/18/08, Corinna Vinschen <[EMAIL PROTECTED]> wrote:
> On Apr
On Apr 18 13:02, Luke Kendall wrote:
> Corinna Vinschen wrote:
>> On Apr 16 16:42, Luke Kendall wrote:
>>
>>> Suppose that when it does a stat() on "fred", before it decides that
>>> it's found the right file to exec, it should check that "fred" isn't a
>>>
>>
>> A stat() call can't know fo
Larry Hall (Cygwin) wrote:
Luke Kendall wrote:
Larry Hall (Cygwin) wrote:
On 04/18/2008, Luke Kendall wrote:
It looks like something has stat()ed /opt/bin/ici and then decided
it's been asked to execute that, and refusing (which makes a kind
of sense), and bailing out with an error (*that* st
Luke Kendall wrote:
Larry Hall (Cygwin) wrote:
On 04/18/2008, Luke Kendall wrote:
It looks like something has stat()ed /opt/bin/ici and then decided
it's been asked to execute that, and refusing (which makes a kind of
sense), and bailing out with an error (*that* step seems wrong to me).
Wel
Larry Hall (Cygwin) wrote:
On 04/18/2008, Luke Kendall wrote:
Larry Hall (Cygwin) wrote: What do you mean by Cygwin, in this case?
Bash? Cygwin's implementation of exec()?
In this case, bash. Try it from, say, csh, and you'll see something a
bit different.
$ /opt/bin/ici -help
CORRECT>/op
On 04/18/2008, Luke Kendall wrote:
Larry Hall (Cygwin) wrote: What do you mean by Cygwin, in this case?
Bash? Cygwin's implementation of exec()?
In this case, bash. Try it from, say, csh, and you'll see something a
bit different.
It uses stat() to find out what type of thing "foo" is. Then
Larry Hall (Cygwin) wrote:
On 04/17/2008, Luke Kendall wrote:
Mark J. Reed wrote:
> I still don't understand why you would put the ici dir in the same
> place as the ici script. You can't do that on Unix, so why do it on
> Cygwin?
>
> The creator did this because simply it seemed a convenient
Igor Peshansky wrote:
On Wed, 16 Apr 2008, Luke Kendall wrote:
We have the Ici scripting language installed on Windows. Ici expects a
directory called "ici" to exist alongside, where various libraries are
installedd to provide extra functionality.
Unfortunately, under Cygwin, if w try to r
On 04/17/2008, Luke Kendall wrote:
Mark J. Reed wrote:
> I still don't understand why you would put the ici dir in the same
> place as the ici script. You can't do that on Unix, so why do it on
> Cygwin?
>
>
The creator did this because simply it seemed a convenient way to keep all
the ici c
consider that "not found"
and the logic would flow through into the checking for ".exe" and
whatever other arcane Windows executable-file suffixes make sense.
But having not looked at the source, I confess I'm just guessing.
Thanks,
luke
-Original Message---
Corinna Vinschen wrote:
On Apr 16 16:42, Luke Kendall wrote:
Suppose that when it does a stat() on "fred", before it decides that
it's found the right file to exec, it should check that "fred" isn't a
A stat() call can't know for what purpose it has been called. Calling
stat on "foo",
On Wed, 16 Apr 2008, Luke Kendall wrote:
> We have the Ici scripting language installed on Windows. Ici expects a
> directory called "ici" to exist alongside, where various libraries are
> installedd to provide extra functionality.
>
> Unfortunately, under Cygwin, if w try to run the command "ici
On Apr 16 16:42, Luke Kendall wrote:
> Suppose that when it does a stat() on "fred", before it decides that
> it's found the right file to exec, it should check that "fred" isn't a
A stat() call can't know for what purpose it has been called. Calling
stat on "foo", it will return the information
should check that "fred" isn't a
> directory. If it is a directory, it should consider that "not found"
> and the logic would flow through into the checking for ".exe" and
> whatever other arcane Windows executable-file suffixes make sense.
>
> But h
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED] On Behalf Of Luke Kendall
> > Sent: Tuesday, April 15, 2008 9:44 PM
> > To: cygwin@cygwin.com
> > Subject: Directory existence prevents .exe execution
> >
> > We have the Ici scripting language
We have the Ici scripting language installed on Windows. Ici expects a
directory called "ici" to exist alongside, where various libraries are
installedd to provide extra functionality.
Unfortunately, under Cygwin, if w try to run the command "ici" we get
the error "ici: command not found", be
19 matches
Mail list logo
