From: Rasmus Villemoes > Sent: 07 August 2023 20:32 ... > No, please. Let's have a separate header for the functions defined in > vsprintf.c. We really need to trim our headers down to something more > manageable, and stop including everything from everywhere just because > $this little macro needs $that little inline function. The problem I see isn't things like kernel.h defining a few 'library' functions, but deep nested includes that means that pretty much all of the headers get pulled into all the compiles. Some nested includes sequences can go through an "asm" header that you might expect to be architecture specific stuff and then include something like ioctl.h. Add something like #define IO_WR @@@ to the top a C file and then see where the compiler finds the duplicate definition. David - Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK Registration No: 1397386 (Wales)
