X-Spam-Check-By: sourceware.org Message-ID: <10845a340604260701g2026a64fx5dac7fb5351b224a@mail.gmail.com> Date: Wed, 26 Apr 2006 15:01:29 +0100 From: "Richard Quadling" Reply-To: RQuadling AT googlemail DOT com To: cygwin AT cygwin DOT com Subject: How do I detect a failure in Make? MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Disposition: inline Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by delorie.com id k3QE1jqk017347 Hi. I have the following bash script ... #!/bin/shcvs up 2> $HOME/cvs1.log > $HOME/cvs2.logcd phpdocautoconf -v -d --warnings=all &> $HOME/autoconf.log./configure --with-source=./../php-src --with-pear-source=./../pear--with-chm=yes --with-treesaving > $HOME/configure.logmake test > $HOME/make_test.logmake test_xml > $HOME/make_test_xml.logmake chm_xsl > $HOME/make_chm_xsl.log Is there a way of stopping the makes if there was a problem. There are more things after these makes but I don't want them to rununless the makes worked. I'm used to MS-DOS errorlevels. I assume there is a way of accessingthe errorlevel from a program (assuming it generates one) or any otherway. The make is failing with ... make: *** [test_xml] Segmentation fault (core dumped) I always thought a core dump was a bad thing, but it is what happens. Any ideas? Regards, Richard Quadling.-------Fight back spam! Download the Blue Frog.http://www.bluesecurity.com/register/s?user=UlF1YWRsaW5n