On 11/7/19 11:21 AM, Szabolcs Nagy wrote: >> Or just giving up and telling users they can't just directly include >> both libc headers and kernel headers? > > including both libc and linux headers is fragile and > will break differently across the different linux > libc implementations. We saw this all the time working in embedded. There ends up being a rather tight version coupling that happens, and that's unfortunate, but a function of cost. Fixing this so it works in the various cases is costly. -- Cheers, Carlos.
