On 12/16/06, Eric Blake <[EMAIL PROTECTED]> wrote:
According to Christopher Tate on 12/16/2006 7:51 PM:
>
> First, I should point out that having run setup.exe has now left
> cygwin in an unusable state; i can't launch a bash shell in order to
> run the commands specified.
Why not? Your ls resu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Christopher Tate on 12/16/2006 7:51 PM:
>
> First, I should point out that having run setup.exe has now left
> cygwin in an unusable state; i can't launch a bash shell in order to
> run the commands specified.
Why not? Your ls results s
On 12/16/06, Eric Blake <[EMAIL PROTECTED]> wrote:
According to Christopher Tate on 12/16/2006 5:07 PM:
> Eric Blake wrote, on the cygwin mailing list:
>>
>> Phooey - now that you have gotten rid of the problem, I can't do any more
>> debugging via your system. I'm still trying to reproduce the
Eric Blake wrote:
> I'm starting to wonder if cygcheck chokes on the fact that
> cygreadline6.dll exists, but is missing the hook that /bin/sh version
> 3.0.x depended on. Hmm, based on digging up an older build of bash from
> my archives, it looks like cygcheck is just fine with it, but trying t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
http://cygwin.com/acronyms/#PPIOSPE - redirected to the list, accordingly.
According to Christopher Tate on 12/16/2006 5:07 PM:
> Eric Blake wrote, on the cygwin mailing list:
>>
>> Phooey - now that you have gotten rid of the problem, I can't do any
On Tue, 12 Dec 2006, Dave Korn wrote:
> On 12 December 2006 03:24, Eric Blake wrote:
>
> Hey Eric,
>
> > Phooey - now that you have gotten rid of the problem, I can't do any
> > more debugging via your system. I'm still trying to reproduce the
> > failure, by manually sourcing /etc/profile.d/00
On 12 December 2006 03:24, Eric Blake wrote:
Hey Eric,
> Phooey - now that you have gotten rid of the problem, I can't do any more
> debugging via your system. I'm still trying to reproduce the failure, by
> manually sourcing /etc/profile.d/00bash.sh, but so far it seems I am just
> catching l
I could probably restore my Cygwin directory from a backup and try again.
-Ken
-Original Message-
From: Eric Blake [mailto:[EMAIL PROTECTED]
Sent: Monday, December 11, 2006 9:24 PM
To: Kenneth Evans, Jr.
Cc: cygwin@cygwin.com
Subject: Re: Postinstall Problem with 01bash.bat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Kenneth Evans, Jr. on 12/11/2006 8:52 AM:
> Hi,
>
>> What do the following say?
>
>> $ ls -l /bin/sh.exe /bin/bash.exe
>> $ bash --version
>> $ sh --version
>
> C:\Documents and Settings\evans>ls -l /bin/sh.exe /bin/bash.exe
> -rwxrwxrw
Hi,
> What do the following say?
> $ ls -l /bin/sh.exe /bin/bash.exe
> $ bash --version
> $ sh --version
C:\Documents and Settings\evans>ls -l /bin/sh.exe /bin/bash.exe
-rwxrwxrwx 1 evans Users 484352 Dec 6 08:17 /bin/bash.exe
-rwxrwxrwx 1 evans None 451072 Feb 26 2006 /bin/sh.exe
C:\Documen
On Sun, 10 Dec 2006, Eric Blake wrote:
> According to Kenneth Evans, Jr. on 12/10/2006 1:27 PM:
> [snip]
> > setup.full.log from the last run (which was from the local directory and
> > cancelled) is:
>
> Please attach, rather than sending files inline, to avoid false positives
> when searching ma
11 matches
Mail list logo
