On 8/13/20 1:37 PM, Bruno Haible wrote:
I don't object to adding '#include ' in the two *.m4 files. It's
redundant, but it won't hurt either.
Thanks for explaining; let's leave it alone then.
Paul Eggert wrote:
> Should those changes to m4/getrandom.m4 and m4/sys_random_h.m4 also have
> "#include " lines inserted after the newly-modified C comments?
> That
> way, these .m4 files would match the change to lib/sys_random.in.h.
>From the error message, we can see that uClibc's merely
Should those changes to m4/getrandom.m4 and m4/sys_random_h.m4 also have
"#include " lines inserted after the newly-modified C comments? That
way, these .m4 files would match the change to lib/sys_random.in.h.
Bruno Haible writes:
> When a system - in this case, uClibc - provides a header file that cannot
> be included on its own, it's a bug in that system.
>
> Gnulib can only provide a workaround.
Thanks for the workaround.
Maybe akater could report this to the uClibc developers.
Best regards,
Stef
Hi,
Stefan Kangas wrote:
> Please see the below bug report regarding Gnulib compatibility with
> x86_64-pc-linux-uclibc.
When a system - in this case, uClibc - provides a header file that cannot
be included on its own, it's a bug in that system.
Gnulib can only provide a workaround.
2020-08-13
