You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You'll notice that the line you point to need_dh=yes is in there. The change in the commit you are reviewing here is one that I reverted because I re-imported the autoconf-macros project into NRPE in an earlier commit/merge. While I was doing so, I was unfamiliar with the need to uncomment that. When running with that line set to no, or commented, you'll notice that the dh.h is NEVER generated.
In fact, if you checkout the above commit and run autoconf, the same behavior you are suggesting existed then as well. The only way to disable dh truthfully is with --disable-ssl (since adh is necessary when compiling with SSL).
(notice the same behavior as the current version).
So you tell me, is there an enhancement that needs to occur where --with-need-dh=no needs to override that value even if SSL is enabled? Because otherwise, this is not a bug.
The sole purpose of the --with-need-dh configure option is to set the need_dh value to no to prevent the openssl call which generates the dh.h file.
In the case of the Debian package, the dh.h file is created outside of the configure process to make the package build reproducible. See the linked Debian bugreport.
If you want configure to always generate the dh file, the --with-need-dh option needs to be removed because it doesn't do anything any more.
I'm still confused. Partly because of the lack of documentation in the autoconf-macros. You are correct, but I'm unsure why the commit I checked after I updated the autoconf-macros subtree looks exactly how it looked in your reference. I'm also unsure why the commented line exists # need dh should only be set for NRPE. Regardless, the fix is here: c339ba2
Commit 1715dcd#diff-67e997bcfdac55191033d57a16d1408a sets
need_dh=yes
discarding the value of the configure option.Generating the
include/dh.h
header as part of the configure process causes the build to become unreproducible. See: Debian Bug #834857.The text was updated successfully, but these errors were encountered: