Hi Duncan, >On Fri, Jul 12, 2024 at 12:38:59PM +0000, Joshua Lant wrote: >> Adding this configure option fixes compilation errors which occur when >> building with musl-libc. These are known issues with musl that cause structure >> redefinition errors in headers between linux/if_ether.h and >> netinet/ether.h. >> >> Signed-off-by: Joshua Lant joshualant@xxxxxxxxx >> --- >> INSTALL | 7 +++++++ >> configure.ac | 10 +++++++++- >> 2 files changed, 16 insertions(+), 1 deletion(-) >> >> diff --git a/INSTALL b/INSTALL >> index d62b428c..8095b0bb 100644 >> --- a/INSTALL >> +++ b/INSTALL >> @@ -63,6 +63,13 @@ Configuring and compiling >> optionally specify a search path to include anyway. This is >> probably only useful for development. >> >> +--enable-musl-build >> + >> + When compiling against musl-libc, you may encounter issues with >> + redefinitions of structures in headers between musl and the kernel. >> + This is a known issue with musl-libc, and setting this option >> + should fix your build. >> + >> If you want to enable debugging, use >> >> ./configure CFLAGS="-ggdb3 -O0" > >Niggle: Since at lease gdb 11.2, `info gdb` section >'4.1 Compiling for Debugging' says this: > >> | Older versions of the GNU C compiler permitted a variant option '-gg' >> |for debugging information. GDB no longer supports this format; if your >> |GNU C compiler has this option, do not use it. > >I suggest `-g3 -gdwarf-4`. This enables gdb commands like `info macro`. >There is also a `-Og` option. Personally, I'm not sure that I like it. > I have not actually added the portion about debugging in the INSTALL file, just the stuff above it, this is just included in the generated patch file... I added the new configuration option information above the debugging stuff rather than at the end of the list, because logically in my mind I would want to see all of the other build options, and then at the end see about debugging. Last resort if none of the normal build options are doing it for me kind of thing... Cheers, Josh
