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: <4F1915D6.80900@gmail.com> Date: Fri, 20 Jan 2012 08:20:54 +0100 From: marco atzeri User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 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> In-Reply-To: <4F18AB1B.7020207@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 1/20/2012 12:45 AM, Dave Korn wrote: > > Hi list, > > I just updated my Cygwin installation for the first time since Oct 26 last > year, and now I'm unable to successfully run cygport builds any more. The > builds fail because of the spontaneous exiting of one or other of the scripts > that cygport invokes - I've had autoconf-2.68 spontaneously exiting during the > autoreconf stage, and if I skip over that the configure scripts do the same thing. > > On closer inspection, it turns out that they were exiting first time they > executed subcommands that failed. I added 'set -o' to my cygport script, both > inline so it would be executed when the script gets sourced, and inside my > override of src_compile so I could see what was happening just before the > configure call, and sure enough it showed me that errexit was off at the start > of the run but had been set on by the time execution reached src_compile. > > 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? > > cheers, > DaveK > > FYI, I have see no particular issue running latest cygport and autoconf autoconf 10-1 autoconf2.1 2.13-10 autoconf2.5 2.68-1 cygport 0.10.7-1 on latest cygwin snapshot CYGWIN_NT-6.1-WOW64 1.7.10s(0.259/5/3) 20120111 22:39:26 I just finished the build of octave and it is usually a good crash test. Regards Marco -- 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