On 05. 08. 19 21:13, Ondrej Zajicek wrote:
On Mon, Aug 05, 2019 at 07:57:49PM +0200, Robert Scheck wrote:
On Fri, 29 Mar 2019, Ondrej Zajicek wrote:
On Fri, Mar 29, 2019 at 01:08:18AM +0100, Robert Scheck wrote:
+ ./configure --build=x86_64-redhat-linux-gnu --host=x86_64-redhat-linux-gnu --program-prefix= --disable-dependency-tracking --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib64 --libexecdir=/usr/libexec --localstatedir=/var --sharedstatedir=/var/lib --mandir=/usr/share/man --infodir=/usr/share/info --runstatedir=/run/bird BUILDSTDERR: configure: error: unrecognized option: `--runstatedir=/run/bird'
Yes, you are right. Thanks for notifying us. Seems like releases 1.6.6 and 2.0.4 have configure scripts that were inadvertently generated with older autoconf without 'runstatedir' option support.
Workaround is either to regenerate configure using 'autoreconf' from proper autoconf tool, or just use older 'with-runtimedir' option.
I just wanted to let you know that this issue hasn't been fixed for 2.0.5, unfortunately.
Yes, i just noticed that after the release. Sorry, we missed that. Unfortunately it is something that we cannot fix in advance in git (as configure script is generated during release by autoconf), autoconf developers cannot make a new release in 7 years, so in some distros there is a patched autoconf (supporting runstatedir option) and in others there is the original one. When the release is generated on such system, it does not have this option.
This is my fault. I am sorry, working with too much machines that do no have this new version of autoconf. I promise to fix it in the next release. Ondrej