This is the mail archive of the
mailing list for the elfutils project.
[Bug general/21008] New: Incompatible with MUSL libc: error.h and error() not provided
- From: "luizluca at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: elfutils-devel at sourceware dot org
- Date: Fri, 30 Dec 2016 20:42:06 +0000
- Subject: [Bug general/21008] New: Incompatible with MUSL libc: error.h and error() not provided
- Auto-submitted: auto-generated
Bug ID: 21008
Summary: Incompatible with MUSL libc: error.h and error() not
Assignee: unassigned at sourceware dot org
Reporter: luizluca at gmail dot com
CC: elfutils-devel at sourceware dot org
Target Milestone: ---
>From original bug 21002:
- The idea of using system.h to define error () seems fine. But the current
replacement doesn't seem complete. error () also flushes stdout first. Which we
don't really seem to use, so might not be essential. But it also calls exit
(status) if status != 0. Which is essential to how error is used in elfutils.
Also error () updates error_message_count which is used in a couple of cases to
know what exit code a program should use (if error itself didn't exit).
The proposed solution would be to:
1) move error.h inclusion into system.h and conditionally include either
error.h or err.h
2) build a good replacement for error()
The only problem is #2.
This thread is about this problem:
The solution that was already present in OpenWRT/LEDE was simply to use:
#define error(status, errno, ...) err(status, __VA_ARGS__)
Which is not enough as error replacement. It always exits even when status is
0, it does not flush stdout and it does not increase the (absent)
I didn't noticed the missing error_message_count as a problem because, for
OpenWRT/LEDE, only elfutils libs where compiled (and they don't use
error_message_count). So, for my use case, this might be enough:
#define error(status, errno, ...) \
warn(__VA_ARGS__); \ // == err(status,...) without exit
if (errno) exit(errno);
There is a minor problem of ignoring errno, which might be considered an
For a full built, the problem is error_message_count. It is a global variable
and it must be initialized. Probably the best solution would be to create a
simplified error.h/error.c, which exports error and error_message_count and
gets optionally build and linked (autoconf) into the generated files when
error.h is absent.
Some existing approaches so far:
You are receiving this mail because:
You are on the CC list for the bug.