This is the mail archive of the
cygwin
mailing list for the Cygwin project.
RE: cygwin1.dll crash
- From: "Dave Korn" <dave dot korn at artimi dot com>
- To: <cygwin at cygwin dot com>
- Date: Tue, 8 Feb 2005 15:48:41 -0000
- Subject: RE: cygwin1.dll crash
> -----Original Message-----
> From: cygwin-owner On Behalf Of Lannoye Xavier
> Sent: 08 February 2005 14:50
> here you have the output for dir /w
> its quite huge
Directory of C:\oracle\ora90\Apache\Perl\5.00503\bin\mswin32-x86
[.] [..] a2p.exe perl.dll
perl.exe perl5.00503.exe perl95.exe perlglob.exe
6 File(s) 987.136 bytes
This is ActiveState perl, so I was wrong in my first guess. I'm still
suspicious that it's the root cause of the trouble though; if any of the
setup.exe post-install scripts rely on perl, they are liable to invoke active
state perl instead of cygwin perl, and break when it fails to understand
cygwin-style POSIX paths.
> I've put the cygwin path in top of my PATH var. but still the
> same problem
Hmm, peculiar. May need some more thinking time over this. Precisely how did
you set it? If you do it using the PATH command in a DOS prompt, that wouldn't
affect a copy of setup.exe that you launched from explorer, you do need to set
it in Start Menu / Settings / Control Panel / System / Advanced / Environment
Variables. Try setting your PATH to nothing but these entries:
C:\cygwin\bin
C:\WINDOWS\system32
C:\WINDOWS
C:\WINDOWS\System32\Wbem
and see if that helps any.
cheers,
DaveK
--
Can't think of a witty .sigline today....
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/