Building Kea-DHCP 2.2.0 on Raspberry Pi 4 (Debian Bullseye) fails
name: Bug report
about: Building Kea-DHCP on Debian Bullseye (ARM)
Describe the bug Trying to build Kea-DHCP 2.2.0 on a Raspberry Pi 4 with Debian Bullseye the following error is shown during build process:
Making all in d2 make[4]: Verzeichnis „/home/user/kea/src/bin/d2“ wird betreten Making all in . make[5]: Verzeichnis „/home/user/kea/src/bin/d2“ wird betreten CXX parser_context.lo In file included from ../../../src/lib/d2srv/d2_log.h:11, from parser_context.cc:11: parser_context.cc: In member function ‘void isc::d2::D2ParserContext::warning(const isc::d2::location&, const string&)’: parser_context.cc:211:32: error: ‘DHCP_DDNS_CONFIG_SYNTAX_WARNING’ was not declared in this scope; did you mean ‘DHCP_DDNS_CONFIG_CHECK_FAIL’? 211 | LOG_WARN(d2_to_dns_logger, DHCP_DDNS_CONFIG_SYNTAX_WARNING) | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ../../../src/lib/log/macros.h:29:24: note: in definition of macro ‘LOG_WARN’ 29 | (LOGGER).warn((MESSAGE)) | ^~~~~~~ make[5]: *** [Makefile:677: parser_context.lo] Fehler 1 make[5]: Verzeichnis „/home/user/kea/src/bin/d2“ wird verlassen make[4]: *** [Makefile:699: all-recursive] Fehler 1 make[4]: Verzeichnis „/home/user/kea/src/bin/d2“ wird verlassen make[3]: *** [Makefile:440: all-recursive] Fehler 1 make[3]: Verzeichnis „/home/user/kea/src/bin“ wird verlassen make[2]: *** [Makefile:438: all-recursive] Fehler 1 make[2]: Verzeichnis „/home/user/kea/src“ wird verlassen make[1]: *** [Makefile:605: all-recursive] Fehler 1 make[1]: Verzeichnis „/home/user/kea“ wird verlassen make: *** [Makefile:493: all] Fehler 2
Is there a dependency missing from my end?
To Reproduce Steps to reproduce the behavior:
- Try to build Kea-DHCP on a Raspberry Pi 4 with Debian Bullseye and MYSQL extension enabled
Expected behavior Build process should finish successfully
Environment:
- Kea 2.2.0
- Debian Bullseye ARM
- Redis Backend, MySQL support
Additional Information
Make sure you anonymize your config files (at the very lease make sure you obfuscate your database credentials, but you may also replace your actual IP addresses and host names with example.com and 10.0.0.0/8 or 2001:db8::/32).
Contacting you