[MacPorts] #54063: libzookeeper: update to 3.4.10
MacPorts
noreply at macports.org
Sun May 7 07:35:29 UTC 2017
#54063: libzookeeper: update to 3.4.10
---------------------------+-----------------
Reporter: JacksonIsaac | Owner:
Type: update | Status: new
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: | Keywords:
Port: libzookeeper |
---------------------------+-----------------
Comment (by ryandesign):
The cppunit build dependency is overriding the apache-ant build dependency
which is probably not what you wanted.
Why use autoreconf? It fails for me:
{{{
Executing: cd "/opt/local/var/macports/build
/_Users_rschmidt_macports_macports-
ports_devel_libzookeeper/libzookeeper/work/zookeeper-3.4.10/src/c" &&
autoreconf -fvi
DEBUG: system: cd "/opt/local/var/macports/build
/_Users_rschmidt_macports_macports-
ports_devel_libzookeeper/libzookeeper/work/zookeeper-3.4.10/src/c" &&
autoreconf -fvi
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: /opt/local/bin/aclocal --force
configure.ac:37: warning: macro 'AM_PATH_CPPUNIT' not found in library
autoreconf: configure.ac: tracing
autoreconf: running: /opt/local/bin/glibtoolize --copy --force
glibtoolize: putting auxiliary files in '.'.
glibtoolize: copying file './ltmain.sh'
glibtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.ac,
glibtoolize: and rerunning glibtoolize and aclocal.
glibtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
configure.ac:37: warning: macro 'AM_PATH_CPPUNIT' not found in library
autoreconf: running: /opt/local/bin/autoconf --force
configure.ac:37: error: possibly undefined macro: AM_PATH_CPPUNIT
If this token and others are legitimate, please use
m4_pattern_allow.
See the Autoconf documentation.
autoreconf: /opt/local/bin/autoconf failed with exit status: 1
}}}
Traditionally in MacPorts `--prefix=${prefix}` goes not in
`configure.args` but in `configure.pre_args`. It's there by default so you
don't need to add anything to the portfile to make that happen.
I'm confused that you're adding the flag `--without-cppunit`, which one
would think would tell the build system not to use cppunit, but then
you're also adding a cppunit dependency.
I'm also not sure why you're disabling dependency tracking. It builds fine
for me with it enabled.
--
Ticket URL: <https://trac.macports.org/ticket/54063#comment:1>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list