Re: Binaries Don't Execute SOLVED (sort of)

Hi All, - Original Message - From: "Champ Mendis" <[EMAIL PROTECTED]> To: Sent: Monday, December 11, 2006 5:47 PM Subject: Re: Binaries Don't Execute SOLVED (sort of) - Original Message - From: "Eric Blake" <[EMAIL PROTECTED]> To:

Re: Binaries Don't Execute SOLVED (sort of)

- Original Message - From: "Eric Blake" <[EMAIL PROTECTED]> To: ; <[EMAIL PROTECTED]> Sent: Saturday, December 09, 2006 12:53 AM Subject: Re: Binaries Don't Execute SOLVED (sort of) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to tbrowder on 12/

RE: Binaries Don't Execute SOLVED (sort of)

> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Larry Hall (Cygwin) > Sent: Friday, December 08, 2006 07:20 > To: cygwin@cygwin.com > Subject: Re: Binaries Don't Execute SOLVED (sort of) ... > Unless you're referring t

RE: Binaries Don't Execute SOLVED (sort of)

> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Dave Korn > Sent: Friday, December 08, 2006 06:54 > To: cygwin@cygwin.com > Subject: RE: Binaries Don't Execute SOLVED (sort of) ... > It's worth mentioning that cygche

Re: Binaries Don't Execute SOLVED (sort of)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to tbrowder on 12/8/2006 3:51 AM: > > I removed the entire installtion and started anew. Everything works now, > but the command line response gives extra characters sometime. Perhaps the > latest bash update has something to do with that.

Re: Binaries Don't Execute SOLVED (sort of)

Dave Korn wrote: On 08 December 2006 10:51, tbrowder wrote: I removed the entire installtion and started anew. Everything works now, but the command line response gives extra characters sometime. Perhaps the latest bash update has something to do with that. Known bug in libreadline vs. p

RE: Binaries Don't Execute SOLVED (sort of)

On 08 December 2006 10:51, tbrowder wrote: > I removed the entire installtion and started anew. Everything works now, > but the command line response gives extra characters sometime. Perhaps the > latest bash update has something to do with that. Known bug in libreadline vs. prompts with non

RE: Binaries Don't Execute

> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Dave Korn > Sent: Wednesday, December 06, 2006 15:56 > To: cygwin@cygwin.com > Subject: RE: Binaries Don't Execute ... > WAG[*]: When setup.exe tells you that you have to r

RE: Binaries Don't Execute SOLVED (sort of)

> -Original Message- > From: Igor Peshansky [mailto:[EMAIL PROTECTED] > Sent: Tuesday, December 05, 2006 21:51 > To: tbrowder > Cc: cygwin@cygwin.com > Subject: Re: Binaries Don't Execute > > On Tue, 5 Dec 2006, tbrowder wrote: > > > I have upgrad

RE: Binaries Don't Execute

On 06 December 2006 03:05, tbrowder wrote: > I have upgraded my cygwin installation and now some bibaries don't execute. > The ones I've noticed so far are ssh and diff. > > When I execute ssh, the binary is found on my path, and it shows as > executable, but it responds with nothing. Same thing

Re: Binaries Don't Execute

On Tue, 5 Dec 2006, tbrowder wrote: > I have upgraded my cygwin installation and now some bibaries don't > execute. The ones I've noticed so far are ssh and diff. > > When I execute ssh, the binary is found on my path, and it shows as > executable, but it responds with nothing. Same thing with di

Binaries Don't Execute

I have upgraded my cygwin installation and now some bibaries don't execute. The ones I've noticed so far are ssh and diff. When I execute ssh, the binary is found on my path, and it shows as executable, but it responds with nothing. Same thing with diff and which. Any clues? Thanks. Tom Browde