X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,TW_YG,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Andrew DeFaria Subject: Re: Unable to install coreutils 8.15-1(?) - error in coreutils.sh exit code 127 Date: Tue, 21 Feb 2012 07:34:54 -0800 Lines: 49 Message-ID: References: <4F42AE8E DOT 20109 AT redhat DOT com> <6BFA9AF2C7556E42AFF3F187ECAB07B802CD6AAC AT bespdc01 DOT mediaxim DOT local> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120202 Thunderbird/11.0 In-Reply-To: <6BFA9AF2C7556E42AFF3F187ECAB07B802CD6AAC@bespdc01.mediaxim.local> X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On 02/21/2012 05:18 AM, Michel Bardiaux wrote: >> On 2/20/2012 12:35 PM, Eric Blake wrote: >>> That link error is typically a sign of cygwin1.dll being too old >>> compared to what coreutils 8.15 is expecting. Are you sure your >>> cygwin1.dll comes from 1.7.10, and that it wasn't in-use when you >>> upgraded in such a manner that you are still running cygwin 1.7.9 in > memory? >> Interesting. uname -a is reporting 1.7.9. You might be right! I'll try > to find a time to reboot and> check this out. > > I had the same problem yesterday after trying to install "chere": cygwin > executables not doing anything, but cygcheck saying all packages OK. > After a lot of floundering, FAQing, web searches, trying to force > reinstall of coreutils 8.15, then forcing reinstall from local disk of > everything, still no cigar. Reading this thread this morning put me on > the right track: force downgrade of coreutils to 8.14-1. Then cygwin > works again, but that can only be a temporary fix, since every time one > runs setup, it upgrades coreutils to 8.15... > > Anyway, after reboot, uname -a says 1.7.9-1. And indeed, opening > cygwin1.dll in "dependency walker" (a Win32, not a cygwin, tool) shows > that sys_siglist is not defined. But cygcheck states that 1.7.10-1 is > installed! Hence I forced reinstall of pkg "cygwin" (while it upgrades > coreutils). Now everything is fine. > > I suppose we'll never know what began the problem. Still, cygcheck > should NOT have reported 1.7.10-1 as OK when it was not... > > Thanks to the whole cygwin community for help on this in particular, and > for a fine ware in general. > > Michel Bardiaux > --------------- > "As far as I can see all I see is C" > > To further report my progress... I did reboot and things were not good. Cygwin had problems. So I went to install coreutils-8.15-1 and things did not improve. I also saw uname reporting 1.7.9. But then what I did was set to reinstall both coreutils and cygwin base to make sure that cygwin1.dll got reinstalled. I also made sure all of my Cygwin services were stopped and that cygwin1.dll was not loaded (Process Explorer is great for that) and launched setup.exe from a Windows Explorer and set coreutils and cygwin base to reinstall. After that things were fine and uname reported 1.7.10. -- Andrew DeFaria Press any key... no, no, no, NOT THAT ONE! -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple