This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.

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: Crosstool: Quiting shell when compilation fails?

From: Dan Kegel <dank at kegel dot com>
To: Martin Egholm Nielsen <martin at egholm-nielsen dot dk>
Cc: crossgcc at sources dot redhat dot com
Date: Wed, 23 Jun 2004 07:39:03 -0700
Subject: Re: Crosstool: Quiting shell when compilation fails?
References: <cbc0bf$cl$1@sea.gmane.org>

Martin Egholm Nielsen wrote:

In the recent crosstool versions - 0.28rc23 at least - the all.sh script exit the running shell if a compilation error occur - is that right? Or has it always been like that? I've only tried with bash running in cygwin, that is...


You mean your window goes away?
I think that's a cygwin bug.  To work around it, always
redirect stdout and stderr to a log file.  Then you can
see the error.
- Dan

--
My technical stuff: http://kegel.com
My politics: see http://www.misleader.org for examples of why I'm for regime change

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com

Follow-Ups:
- Re: Crosstool: Quiting shell when compilation fails?
  - From: Martin Egholm Nielsen

References:
- Crosstool: Quiting shell when compilation fails?
  - From: Martin Egholm Nielsen

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