When building nagios against the musl C library, the type uint is undefined. This leads to a few errors, the tl;dr of which is
t-utils.c:139:21: error: unknown type name 'uint'; did you mean 'int'?
139 | int ok_uint(uint a, uint b, const char *name)
| ^~~~
| int
The root cause of this is that while uint is usually an alias for unsigned int, it actually isn't part of the C standard. Musl does have the uint typedef available in <sys/types.h>, but the simplest fix would be to find & replace uint with either unsigned or unsigned int. Then the header is not needed.
When building nagios against the musl C library, the type
uint
is undefined. This leads to a few errors, the tl;dr of which isThe root cause of this is that while
uint
is usually an alias forunsigned int
, it actually isn't part of the C standard. Musl does have theuint
typedef available in <sys/types.h>, but the simplest fix would be to find & replaceuint
with eitherunsigned
orunsigned int
. Then the header is not needed.