X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-0.5 required=5.0 tests=AWL,BAYES_00,DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED,RCVD_NUMERIC_HELO,SPF_HELO_PASS,TW_YG,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Andy Moreton Subject: Re: cygport: broken vs. autotools by "set -e" Date: Fri, 20 Jan 2012 12:50:27 +0000 Lines: 17 Message-ID: References: <4F18AB1B DOT 7020207 AT gmail DOT com> Mime-Version: 1.0 Content-Type: text/plain User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.92 (windows-nt) X-IsSubscribed: yes 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 On Thu 19 Jan 2012, Dave Korn wrote: > Commenting-out the "set -e;" line at the start of /usr/bin/cygport > has fixed this problem, and my builds now run just fine, but huh? I > checked in git; that line has been there since like forever, so why is > it giving me trouble now? Is there something I could have changed in > my environment or startup scripts that is causing this -e to propagate > to subshells that it didn't used to, or did there used to be a > mechanism in cygport that would have had the effect of turning it off > for subshells that has now been removed for some reason? Hi Dave, As a WAG it could be that you have differences in behaviour from updating bash - check the docs for 'set -e' changes in bash 4.x AndyM -- 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