X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <4A50D5A3.80806@gmail.com> Date: Sun, 05 Jul 2009 17:32:35 +0100 From: Dave Korn User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: [ANNOUNCEMENT] [1.7] Updated: binutils-2.19.51-1 References: <4A5067EB DOT 5080203 AT bonhard DOT uklinux DOT net> <4A50A6D2 DOT 4030109 AT gmail DOT com> <4A50D055 DOT 2010309 AT verizon DOT net> In-Reply-To: <4A50D055.2010309@verizon.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Jerry DeLisle wrote: > Maybe I need a different combination of binutils, libreadline, and bash. Binutils can't possibly be causing shell startup failures, it's not remotely involved(*). It's going to be between libreadline and bash. cheers, DaveK -- (*) - Unless you have something very unusual in your startup scripts, but that doesn't seem likely... -- 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