On 2020-04-24 19:29:31+0100, Ramsay Jones <ramsay@xxxxxxxxxxxxxxxxxxxx> wrote: > > > On 24/04/2020 18:09, Danh Doan wrote: > > On 2020-04-24 17:56:46+0100, Ramsay Jones <ramsay@xxxxxxxxxxxxxxxxxxxx> wrote: > [snip] > > >> So, again I don't see a problem. I guess it is possible that the > >> version of sparse I am using (see above) has _also_ fixed this > >> problem, in addition to the prototype attribute placement fix. > >> > >> Another option is that the version of glibc also matters. (I am > >> on Linux Mint, which is based on Ubuntu 18.04 LTS) It would not > >> be the first time that I have seen errors in system header files > >> change from one release to the next ... > > > > I'm using a Linux distro with musl libc. > > Ah, OK. > > I just tried re-building v0.6.1 to see if any '<alloca.h>' related > errors/warnings show up for me, but they don't: > > $ sparse --version > v0.6.1 > $ > $ git checkout master > Switched to branch 'master' > Your branch is up-to-date with 'origin/master'. > $ > $ make clean > GIT_VERSION = 2.26.2.266.ge870325ee8 > ... > $ > $ make NO_REGEX=1 compat/regex/regex.sp > SP compat/regex/regex.c > compat/regex/regex_internal.c:925:1: error: symbol 're_string_context_at' redeclared with different type (originally declared at compat/regex/regex_internal.h:433) - different modifiers > $ > > > I guess it's the main culprit? > > Quite possible, I guess. What do the errors/warnings look like? OK, I've tried with my glibc box, it doesn't have that warning. On musl, it warns: $ make compat/regex/regex.sp GIT_VERSION = 2.26.2 * new build flags SP compat/regex/regex.c /usr/include/alloca.h:14:9: warning: preprocessor token alloca redefined compat/regex/regex.c:66:9: this was the original definition compat/regex/regex_internal.c:925:1: error: symbol 're_string_context_at' redeclared with different type (originally declared at compat/regex/regex_internal.h:433) - different modifiers -- Danh
