lib/path-concat.c redefines mempcpy before including <string.h>, causing a parse error in the header file (GCC's context reporting isn't great here):

path-concat.c:25:29: error: expected identifier or '(' before 'void'
   25 | # define mempcpy(D, S, N) ((void *) ((char *) memcpy (D, S, N) + (N)))
      |                             ^~~~
path-concat.c:25:37: error: expected ')' before '(' token
   25 | # define mempcpy(D, S, N) ((void *) ((char *) memcpy (D, S, N) + (N)))
      |                                     ^

Overall, the package is in a very bad state.

There are also many implicit function declarations during the build, like this example later in the same file:

path-concat.c: In function 'path_concat':
path-concat.c:81:23: warning: implicit declaration of function 'malloc' [-Wimplicit-function-declaration]
   81 |   p_concat = (char *) malloc (dir_len + base_len + 2);
      |                       ^~~~~~

These will be hard build failures with future compilers, and also tend to cause crashes on 64-bit architectures (if pointers are truncated to int).

The gperf configure version test does not work because it cannot cope with multi-line output from gperf --version.

I'm not sure if it is worth fixing this package because it still does not support UTF-8.

Reproducible: Always