Right after installing with nothing but the default packages and options,
when launching cygwin, bash flashes an error message for half a second and
goes away.
This is a first time install on vista 64 ultimate using 1.7 with setup
version 2.637.
I restarted, deleted cygwin directories and
Update: This looks like the same error as Edward Lam posted on 7/2/2009 in
response to a bash update announcement. Attached is my cygcheck output.
- Ian Kelling
Cygwin Configuration Diagnostics
Current System Time: Sat Jul 04 23:26:58 2009
Windows Vista Ultimate Ver 6.0 Build 6001 Service
Moving to this thread:
Vincent R. wrote:
I backed down on bash version which required install of libreadline6.
bash still fails. This is on NT4.
Maybe I need a different combination of binutils, libreadline, and bash.
I
will play with this for a bit.
Jerry
I have installed new
Jerry DeLisle wrote:
Moving to this thread:
Vincent R. wrote:
I backed down on bash version which required install of libreadline6.
bash still fails. This is on NT4.
Maybe I need a different combination of binutils, libreadline, and bash.
I
will play with this for a bit.
Jerry
I have
Post cygcheck output, both of you, and let's compare.
$ cygcheck -c
Cygwin Package Information
Package VersionStatus
_update-info-dir 00826-1OK
alternatives 1.3.30c-10 OK
ash 20040127-4 OK
On Sun, Jul 05, 2009 at 10:49:10AM -0700, Jerry DeLisle wrote:
Moving to this thread:
Vincent R. wrote:
I backed down on bash version which required install of libreadline6.
bash still fails. This is on NT4.
Maybe I need a different combination of binutils, libreadline, and
bash.
I
will play
See attached file.
Regards,
Jerry
Cygwin Configuration Diagnostics
Current System Time: Sun Jul 05 12:28:58 2009
Windows NT 4 Workstation Ver 4.0 Build 1381 Service Pack 6
Path: C:\WINNT\system32
C:\WINNT
D:\cygwin-1.7\bin
SysDir: C:\WINNT\System32
WinDir: C:\WINNT
PWD =
Vincent R. wrote:
bash 3.2.49-22 OK
libreadline6 5.2.14-12 OK
libreadline7 6.0.3-1OK
Jerry DeLisle wrote:
bash 3.2.49-22
libreadline6 5.2.14-12
libreadline7 6.0.3-1
Err, ok. So
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Jerry DeLisle on 7/5/2009 1:35 PM:
Warning: There are multiple cygwin1.dlls on your path
That's probably your culprit.
- --
Don't work too hard, make some time for fun as well!
Eric Blake e...@byu.net
-BEGIN PGP
Eric Blake wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Jerry DeLisle on 7/5/2009 1:35 PM:
Warning: There are multiple cygwin1.dlls on your path
That's probably your culprit.
I saw that too and did a full search of the disk and there is only one
cygwin1.dll
I am
Dave Korn wrote:
Vincent R. wrote:
bash 3.2.49-22 OK
libreadline6 5.2.14-12 OK
libreadline7 6.0.3-1OK
Jerry DeLisle wrote:
bash 3.2.49-22
libreadline6 5.2.14-12
libreadline7 6.0.3-1
Here is some more information:
bash-3.2$ ./cygcheck -s jerrycheck
741 [main] id 85 _cygtls::handle_exceptions: Exception:
STATUS_STACK_OVERFLO
W
3209 [main] id 85 open_stackdumpfile: Dumping stack trace to
id.exe.stackdump
garbled output from 'id' command - no uid= found
1206 [main]
On Sun, Jul 05, 2009 at 07:34:24PM -0700, Jerry DeLisle wrote:
Eric Blake wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Jerry DeLisle on 7/5/2009 1:35 PM:
Warning: There are multiple cygwin1.dlls on your path
That's probably your culprit.
I saw that too and did a
On Sun, July 5, 2009 13:49, Jerry DeLisle wrote:
Fresh install still broken with backing down one rev on bash and using
libreadline6.
I ran into this Friday as others have noted. The thing that caught me was
that the postinstall scripts in the installer rely on a working bash. Once
I had a
Jerry DeLisle wrote:
I am very happy to accept that this problem is something else. Vincent
sent a note that it is working for him. I am not sure what working
means. I have a bash prompt, but none of the default environment
variables such as prompts and paths and setting up the home
Christopher Faylor wrote:
It sounds like you are conflating a serious STATUS_ACCESS_VIOLATION which
is known to occur on Windows 7 with your not-so-serious Bash
initialization w/cygwin-1.7.
not-so-serious? Cygwin 1.7 install is very broken because of this bug. Seems
serious to me. Is anyone
On Sun, Jul 05, 2009 at 10:04:42PM -0700, Ian Kelling wrote:
Christopher Faylor wrote:
It sounds like you are conflating a serious STATUS_ACCESS_VIOLATION
which is known to occur on Windows 7 with your not-so-serious Bash
initialization w/cygwin-1.7.
not-so-serious? Cygwin 1.7 install is very
17 matches
Mail list logo
