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] |
Yes, my "xterm" goes away when an error occur. E.g. if I add "-nounpack" to my "demo-x.sh" file, and there is no unpacked files present on the system already, the window immediately disappears after launching the script...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?You mean your window goes away?
I've only tried with bash running in cygwin, that is...
Most possible then... Let's leave it there - I'll turn away from cygwin now, anyway - towards fc2. I experienced some new "Illegal instruction" failures when using the libgcj.so from cygwin, and these went away when I used the one from my RH system...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.
Regards, Martin
------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |