-
-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
runstatedir is not defined in autoconf version 2.69 #6
Comments
I'm just realizing the autoconf project has not made an official release since 2012 ... 😳 I'm using Ubuntu and Debian, where this seems to be supported. The sysklogd patch idea originally came fro Gentoo. So what system are you using? Not sure how I should approach this bug report atm. |
As a background. The change in sysklogd configure.ac came about due to Gentoo using Original report is here https://bugs.gentoo.org/701048 |
As far as I can see gentoo solves the problem in the above bug-report differently and not by using --runstatedir because they don't use a autoconf with --runstatedir added. My suggestion would be to revert the change or at least use $localstatedir/run for the PID location if runstatedir is not defined/used. |
Thanks for the feedback, will look into it as soon as possible! |
Should be fixed on master now, please let me know otherwise so we can reopen this issue. Thanks again for the report! |
Yep, that works. Thanks a lot! |
Great, thank you for verifying! 😃 |
latest released version of autoconf is 2.69 and does not define "runstatedir" which was added with commit
http://git.savannah.gnu.org/gitweb/?p=autoconf.git;a=commit;h=a197431414088a417b407b9b20583b2e8f7363bd
to autoconf after the 2.69 release. Running autoreconf on the sysklogd sources gives a broken source tree therefore.
Thanks.
The text was updated successfully, but these errors were encountered: