X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.6 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: References: Date: Wed, 9 Dec 2009 11:05:15 +0100 Message-ID: <1ef5a52f0912090205v2b8bb67cgcca943b8e64061f1@mail.gmail.com> Subject: Re: 1.5.25-15: Problem running rpmbuild from a bash script From: Csaba Raduly To: cygwin@cygwin.com, citrusmoose@hotmail.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Tue, Dec 8, 2009 at 8:16 PM, Matt Rice wrote: > I'm having problems running rpmbuild from a bash script. =A0The problem > occurs when I run the script outside an interactive bash prompt. (snip) > =A0According to the bash manual, the 128 status code means it > terminated on a signal of 0. According to the Perl documentation (perldoc perlvar, $CHILD_ERROR), the 128 status code from a child process (in fact any status code which contains the 0x80 bit) means there was a core dump. --=20 Life is complex, with real and imaginary parts -- 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