>>>> -#include <bits/libc-lock.h> >>> >>> I guess this is required for STDIO_FUTEXES, or am I wrong ? >> >> Not needed. If STDIO_FUTEXES is defined, the file includes >> later on bits/stdio-lock.h which ends up including the >> libc-lock.h. >> > ok, that's fine.
Not wanting to interfere, but shouldn't including an unneeded .h file be totally harmless? Shouldn't .h files be independent, self-contained entities that declare certain symbol and macros and don't break, just declare too much, if you include more than is necessary? Or should this only be guaranteed only for "public" .h files designed to be used by applications, while "internal" libc headers can do some black voodoo? Sounds kinda brittle and hard to maintain if it's the case. -- Laurent _______________________________________________ uClibc mailing list [email protected] http://lists.busybox.net/mailman/listinfo/uclibc
