FTBFS on armfh - implicit-function-declaration

[Miriam España Acebal]

src/main.c:164:17: error: implicit declaration of function ‘LOG’ [-Werror=implicit-function-declaration]
  164 | LOG( RAMOND_CRITICAL "! socket recvmsg error: '%s'\n",
      | ^~~
src/main.c: In function ‘executeActions’:
src/main.c:570:17: warning: argument 2 null where non-null expected [-Wnonnull]
  570 | setenv("PREFIX", NULL, 1);
      | ^~~~~~
In file included from src/main.h:1,
                 from src/main.c:1:
/usr/include/stdlib.h:792:12: note: in a call to function ‘setenv’ declared ‘nonnull’
  792 | extern int setenv (const char *__name, const char *__value, int __replace)
      | ^~~~~~
src/main.c:571:17: warning: argument 2 null where non-null expected [-Wnonnull]
  571 | setenv("PREFIX_LEN", NULL, 1);
      | ^~~~~~
/usr/include/stdlib.h:792:12: note: in a call to function ‘setenv’ declared ‘nonnull’
  792 | extern int setenv (const char *__name, const char *__value, int __replace)
      | ^~~~~~
src/main.c: In function ‘daemonize’:
src/main.c:844:9: error: implicit declaration of function ‘umask’ [-Werror=implicit-function-declaration]
  844 | umask(027);
      | ^~~~~
src/main.c:874:12: error: implicit declaration of function ‘flock’; did you mean ‘clock’? [-Werror=implicit-function-declaration]
  874 | if(flock(pidfile, F_TLOCK, 0) < 0)
      | ^~~~~
      | clock
cc1: some warnings being treated as errors

from https://launchpadlibrarian.net/724118903/buildlog_ubuntu-noble-armhf.ramond_0.5-4.2build2_BUILDING.txt.gz

[Launchpad Janitor (janitor)]

This bug was fixed in the package ramond - 0.5-4.2ubuntu1

---------------
ramond (0.5-4.2ubuntu1) noble; urgency=medium

  * debian/patches/no-implicit-declarations.patch: add prototype for the
    LOG() function. Closes: #1066551, LP: #2061024.
  * debian/patches/0001-Daemonize-ramond-by-default.patch: fix wrong usage
    of flock(), from the arguments this was supposed to be lockf()!

 -- Steve Langasek <email address hidden> Sat, 13 Apr 2024 16:50:06 +0000