[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #42704] mkoctfile returns 0 if compile failed
|
From: |
Mike Miller |
|
Subject: |
[Octave-bug-tracker] [bug #42704] mkoctfile returns 0 if compile failed but linking succeeded |
|
Date: |
Tue, 08 Jul 2014 16:38:16 +0000 |
|
User-agent: |
Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Firefox/24.0 |
Follow-up Comment #4, bug #42704 (project octave):
Oh I read this too quickly, this is a subtle difference from the earlier bug
#42549. My mistake for forgetting that was already reported and taken care
of.
Andy reports here that mkoctfile returns success if the compilation stage
fails but it is able to link a previously-existing object file into an
oct-file. I can confirm that with 3.8.1, no default to test with at the
moment.
The previous shell script version of mkoctfile used to stop at the compilation
error and exit with failure, leaving the old object file and oct-file around.
So still a regression from 3.8.0.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?42704>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/