On Sun, Jul 05, 2020 at 12:33:38AM +0200, Mark Wielaard wrote:
> library code really shouldn't assert and for utilities a proper
> error message is better than crashing with an assert.
Pushed to master.
In theory an fwrite can fail, if so, signal it by calling issue ().
Signed-off-by: Mark Wielaard
---
src/ChangeLog | 4
src/elfclassify.c | 3 ++-
2 files changed, 6 insertions(+), 1 deletion(-)
diff --git a/src/ChangeLog b/src/ChangeLog
index 0129b8bf..fa7411fd 100644
--- a/src/Change
Since commit 287a18452 libasm.h defines an opague Ebl handle.
This is fine, except for (internal) code that also includes libebl.h.
Since C11 having multiple typedefs for the same thing is fine, but we
do build using GNU/C99. This also allows multiple same typedefs, except
for (very) old GCCs.
Thi