Closed spirillen closed 4 months ago
To configure for systemd you would need to install pkg-config
.
For the Python error you would need to use PYTHON_VERSION=3.11 ./configure ....
to point to a specific Python interpreter if your system does not have a default one (i.e., /usr/bin/python).
I'll leave this open to see what can be done better in config; I see there should already be a suggestion for pkg-config when enabling systemd but maybe there is a bug somewhere.
Fixed the configure script to print more helpful information for both issues. For Python it would suggest the use of the PYTHON_VERSION environment value. For systemd it will complain about the absence of pkg-config.
Hi @gthess
Thanks for your feedback, regarding the comments for how to do this, nay I suggest you to add this to your documentation (compiling). Maybe even ensure that each components requirements? this could make it easier to prepare properly before running the ./configure -arg1 -arg2
Noone is properly prepared for the configure script! :)
I mean that is what the configure script is about; based on the arguments it would tell you if something is missing.
In https://github.com/NLnetLabs/unbound/commit/b67fbb69e75d80e24ec46a5ab9ab9cefb748f122 I added the missing hints for --enable-systemd
in ./configure --help
.
Describe the bug A clear and concise description of what the bug is.
To reproduce Steps to reproduce the behavior:
configure: error: systemd enabled but libsystemd not found
libsystemd0
+libsystemd-dev
--enable-systemd
from the config line, and gets a new error.configure: error: Cannot find python in your system path
libpython3.11-dev
+python3.11-dev
Expected behavior Uncertain....
System:
unbound -V
output: N/AAdditional information