Re: [software] Cygwin Errors
Martin Dorey
> Error: couldn't read Cygwin Rubyw (Ruby
> with no console window) from
> "C:\cygwin\bin\rubyw.exe"
I don't remember ever seeing that message when Cygwin Ruby was installed. But we do say:
> The rest of this message is only relevant if
> you have Cygwin and Cygwin
> Ruby installed.
So I have to assume it is installed. Why, then, can't we read it? Have we looked in the wrong directory? Perhaps there are multiple Cygwin installations on this machine and we've chosen the "wrong" one. Is there a permission issue?
----- Original Message -----
From: Jonathan Daniels <etc....@gmail.com>
To: soft...@jessies.org <soft...@jessies.org>
Sent: Fri Jan 01 07:21:25 2010
Subject: [software] Cygwin Errors
---------------------------
Cygwin Launcher
---------------------------
This program requires Cygwin and Cygwin Ruby.
http://software.jessies.org/salma-hayek/cygwin-setup.html might help.
The rest of this message is only relevant if you have Cygwin and Cygwin
Ruby installed.
Error: couldn't read Cygwin Rubyw (Ruby with no console window) from
"C:\cygwin\bin\rubyw.exe"
Usage: C:\Program
Files\software.jessies.org\terminator\Resources\salma-hayek\.generated\i386_Cygwin\bin\cygwin-launcher.exe
<Cygwin program name> <arguments>...
arguments [
"C:\Program
Files\software.jessies.org\terminator\Resources\salma-hayek\.generated\i386_Cygwin\bin\cygwin-launcher.exe"
"C:\Program
Files\software.jessies.org\terminator\Resources\terminator\bin\terminator"
] arguments
Please copy this message to the clipboard with Ctrl-C and mail it to
soft...@jessies.org.
(Windows won't let you select the text but Ctrl-C works anyway.)
---------------------------
OK
---------------------------
--
Electronic mail (email) is not a confidential form of communication.
In order to ensure confidentiality and to protect your privacy, please
use discretion when sending information that is sensitive in nature.
Martin Dorey
(I haven't yet heard anything further.)
-----Original Message-----
From: Jonathan Daniels [mailto:etc....@gmail.com]
Sent: Friday, January 01, 2010 10:00
To: Martin Dorey
Subject: Re: [software] Cygwin Errors
updating cygwin files, and will retry later.
the rubyw.exe was no where it should have been (not sure why).
Jon
Martin Dorey
Sounds like a quite the setup you have there.
> Aborts clean but without a message.
I thought we'd escaped from such. :(
Running from a Cygwin bash window can sometimes be enlightening, with eg:
DEBUGGING_TERMINATOR=y /cygdrive/c/Program\ Files/software.jessies.org/terminator/Resources/terminator/bin/terminator
Hopefully that'll also fail but with some output.
-----Original Message-----
From: Jonathan Daniels [mailto:etc....@gmail.com]
Sent: Monday, January 04, 2010 14:04
To: Martin Dorey
Subject: Re: [software] Cygwin Errors
there were multiple problems.
permission issue, in a sense, existed. there was a glitch that was
blocking the use of the files by the process that was attempting to use
them.
folder originally in wrong place.
I fixed the folder issue.
Retried.
Noticed something odd, so I ran it with more detailed logging in place,
to watch exactly what was happening.
Asked a friend to glance over the log.
Found the permission type issue.
Fixed that.
Still will not run. Aborts clean but without a message.
Jon
On 1/4/2010 5:00 PM, Audra Owens wrote:
> me neither.
>
> audi
>
> On 1/4/2010 1:54 PM, Martin Dorey wrote:
>> +list again
>>
>> (I haven't yet heard anything further.)
>>
>> -----Original Message-----
>> From: Jonathan Daniels [mailto:etc....@gmail.com]
>> Sent: Friday, January 01, 2010 10:00
>> To: Martin Dorey
>> Subject: Re: [software] Cygwin Errors
>>
>> updating cygwin files, and will retry later.
>>
>> the rubyw.exe was no where it should have been (not sure why).
>>
>> Jon
>>
>> On Fri, Jan 1, 2010 at 11:21 AM, Martin Dorey <mdo...@bluearc.com> wrote:
>>> +public list
>>>
>>>> Error: couldn't read Cygwin Rubyw (Ruby
>>>> with no console window) from
>>>> "C:\cygwin\bin\rubyw.exe"
>>>
>>> I don't remember ever seeing that message when Cygwin Ruby was installed. But we do say:
>>>
>>>> The rest of this message is only relevant if
>>>> you have Cygwin and Cygwin
>>>> Ruby installed.
>>>
>>> So I have to assume it is installed. Why, then, can't we read it? Have we looked in the wrong directory? Perhaps there are multiple Cygwin installations on this machine and we've chosen the "wrong" one. Is there a permission issue?
>>>
>>> ----- Original Message -----
>>> From: Jonathan Daniels <etc....@gmail.com>
>>> To: software@jessies.org <software@jessies.org>
>>> Sent: Fri Jan 01 07:21:25 2010
>>> Subject: [software] Cygwin Errors
>>>
>>> ---------------------------
>>> Cygwin Launcher
>>> ---------------------------
>>> This program requires Cygwin and Cygwin Ruby.
>>> http://software.jessies.org/salma-hayek/cygwin-setup.html might help.
>>>
>>> The rest of this message is only relevant if you have Cygwin and Cygwin
>>> Ruby installed.
>>>
>>> Error: couldn't read Cygwin Rubyw (Ruby with no console window) from
>>> "C:\cygwin\bin\rubyw.exe"
>>> Usage: C:\Program
>>> Files\software.jessies.org\terminator\Resources\salma-hayek\.generated\i386_Cygwin\bin\cygwin-launcher.exe
>>> <Cygwin program name> <arguments>...
>>>
>>> arguments [
>>> "C:\Program
>>> Files\software.jessies.org\terminator\Resources\salma-hayek\.generated\i386_Cygwin\bin\cygwin-launcher.exe"
>>> "C:\Program
>>> Files\software.jessies.org\terminator\Resources\terminator\bin\terminator"
>>> ] arguments
>>>
>>> Please copy this message to the clipboard with Ctrl-C and mail it to
>>> software@jessies.org.
Martin Dorey
> better when it produced a verbose
error message before aborting
Absolutely. I've been to some trouble over the years to make the Cygwin Terminator fail noisily. Part of the problem is generating an error message that gets seen when a user double-clicks on a Desktop shortcut. stderr just gets lost in that case. It's possible that might be happening here, which is why I'd suggest, when you have a little time, that you try this from a Cygwin bash window:
DEBUGGING_TERMINATOR=y /cygdrive/c/Program\ Files/software.jessies.org/terminator/Resources/terminator/bin/terminator
Hopefully any error will be more forthcoming when you can see stderr. (Although, if you're following the recent cygpath saga, you'll know not to get too hopeful.)
----- Original Message -----
From: Jonathan Daniels <etc....@gmail.com>
To: Martin Dorey
Sent: Wed Jan 06 14:29:34 2010
Subject: Re: [software] Cygwin Errors
confused by this. It actually worked better when it produced a verbose
error message before aborting. Having fixed all the known issues, he
somehow made it so that it aborts without an error and yet does not run.
I'm fairly good at gnu/linux and freebsd issues but this one has me a
bit lost as well.
When we get more time to assault this we will.
Audra
>>>> Sent: Fri Jan 01 07:21:25 2010
>
>>>> Subject: [software] Cygwin Errors
>
>>>>
>
>>>> ---------------------------
>
>>>> Cygwin Launcher
>
>>>> ---------------------------
>
>>>> This program requires Cygwin and Cygwin Ruby.
>
>>>> http://software.jessies.org/salma-hayek/cygwin-setup.html might help.
>
>>>>
>
>>>> The rest of this message is only relevant if you have Cygwin and Cygwin
>
>>>> Ruby installed.
>
>>>>
>
>>>> Error: couldn't read Cygwin Rubyw (Ruby with no console window) from
>
>>>> "C:\cygwin\bin\rubyw.exe"
>
>>>> Usage: C:\Program
>
>>>> Files\software.jessies.org\terminator\Resources\salma-hayek\.generated\i386_Cygwin\bin\cygwin-launcher.exe
>
>>>> <Cygwin program name> <arguments>...
>
>>>>
>
>>>> arguments [
>
>>>> "C:\Program
>
>>>> Files\software.jessies.org\terminator\Resources\salma-hayek\.generated\i386_Cygwin\bin\cygwin-launcher.exe"
>
>>>> "C:\Program
>
>>>> Files\software.jessies.org\terminator\Resources\terminator\bin\terminator"
>
>>>> ] arguments
>
>>>>
>
>>>> Please copy this message to the clipboard with Ctrl-C and mail it to
>