X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.5 required=5.0	tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,TW_YG
X-Spam-Check-By: sourceware.org
Message-ID: <4F197F21.8050407@gmail.com>
Date: Fri, 20 Jan 2012 14:50:09 +0000
From: Dave Korn <dave DOT korn DOT cygwin AT gmail DOT com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: cygport: broken vs. autotools by "set -e"
References: <4F18AB1B DOT 7020207 AT gmail DOT com> <vz1d3aea67g DOT fsf AT gmail DOT com>
In-Reply-To: <vz1d3aea67g.fsf@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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 20/01/2012 12:50, Andy Moreton wrote:
> 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

    Hi Andy,

  Bash wasn't one of the packages updated - we've been on bash 4 since
February last year, and I already had it installed last september when I was
successfully using cygport to build the gcc-4.5.3-1 release.  So I figure that
the 4.x set -e behaviour might be part of this problem, but there must have
been a change in cygport that's exposing it when it was previously hidden.

    cheers,
      DaveK


PS. Hope everything's well with you and happy new year!  We should arrange a
pub meet sometime soon on the pig list.

--
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