All,
I recently committed some changes to OpenDMARC's makefile.ac in order to
fix compatibility with 2.70
However, as a result of those changes, our current autoconf setup (2.69,
FreeBSD), fails to properly initialize ac_conf_aux_dir and find our code
in build-aux. (I'm not clear on which macro is introducing which code).
The resulting configure script yields:
root@poudriere:~dmahoney/opendmarc # ./configure
configure: error: cannot find install-sh, install.sh, or shtool in "."
"./.." "./../.."
(All those files are in build-aux).
If I move the CONFIG_AC_AUX_DIR([build-aux]) further up in the file, I
get about ten lines of configure script, and then:
configure: error: cannot run /bin/sh /config.sub
The only way to get a working build seems to be to declare it twice:
AC_CONFIG_AUX_DIR([build-aux])
AC_PREREQ(2.61)
#
# Package version
#
m4_define([VERSION_RELEASE], 1)
m4_define([VERSION_MAJOR_REV], 4)
m4_define([VERSION_MINOR_REV], 0)
m4_define([VERSION_PATCH], 0)
#
# Library version
# - bump "current" and reset "revision" with API changes
# - bump "revision" with internal source code changes
#
m4_define([LIBVERSION_CURRENT], 2)
m4_define([LIBVERSION_REVISION], 2)
m4_define([LIBVERSION_AGE], 0)
#
# Autotools setup
#
AC_INIT([OpenDMARC],
[VERSION_RELEASE.VERSION_MAJOR_REV.VERSION_MINOR_REV],
[bcx+libdmarc@xxxxxxx])
AC_CONFIG_AUX_DIR([build-aux])
Is this normal?
-Dan
--
--------Dan Mahoney--------
Techie, Sysadmin, WebGeek
Gushi on efnet/undernet IRC
FB: fb.com/DanielMahoneyIV
LI: linkedin.com/in/gushi
Site: http://www.gushi.org
---------------------------
