This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: cygport: broken vs. autotools by "set -e"


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]