This is the mail archive of the
mailing list for the Cygwin project.
Re: [1.7.0-46] cygcheck and alternatives both exit with status 127
- From: Andrew Schulman <schulman dot andrew at epamail dot epa dot gov>
- To: cygwin at cygwin dot com
- Date: Mon, 04 May 2009 12:34:38 -0400
- Subject: Re: [1.7.0-46] cygcheck and alternatives both exit with status 127
- References: <firstname.lastname@example.org> <20090504093901.GF21324@calimero.vinschen.de>
> On Apr 30 13:45, Andrew Schulman wrote:
> > Cygwin 1.7.0-46. I try to use alternatives, but every time I do it does nothing
> > except to exit with status 127.
> > So I started to file a bug report, and ran cygcheck -svr. To my surprise,
> > cygcheck also exits part of the way through with status 127. It does give some
> > output first-- attached here.
> > I reverted to Cygwin 1.7.0-45, and alternatives now works, but cygcheck still
> > stops at the same place, with exit status 127.
> I can reproduce this with cygcheck 1.113 from 1.7.0-45 which stumbles
> over the new UTF-16 style symlinks, but that has been fixed in cygcheck
> before -46 has been released and, consequentially, I can not reproduce
> it with that version of cygcheck (1.114) anymore.
OK. Unfortunately my installation is totally borked ATM with a 1.5 vs. 1.7
conflict, so I can't even tell you which package versions I have installed
in 1.7. So that may actually be the problem-- my cygcheck and/or cygwin
versions may be out of date.
So I guess let's put this report on ice for now, until or unless I can
reproduce it in a sane installation.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html