activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Rocha (JIRA)" <>
Subject [jira] [Commented] (AMQCPP-469) Remove linkage to APR-Util
Date Fri, 28 Jun 2013 16:47:20 GMT


John Rocha commented on AMQCPP-469:


I think the fix might not be complete. I have a Linux RH 5.8 system where apr-util isn't installed
and AMQ CPP Client 3.7.0 won't compile on it. It fails with the message:

{panel}libtool: compile:  g++ \-DHAVE_CONFIG_H \-I. \-I../.. \-ansi \-pedantic \-DLINUX=2
\-D_REENTRANT \-D_GNU_SOURCE \-D_LARGEFILE64_SOURCE \-I/views/LU\-7.2\-AMQ\-3.7.1/server/gpl/apr\-1.4.2\-src/BUILD_DIR_RhatFive0206\-i686\-gnu0401/include/apr\-1
\-I/usr/kerberos/include \-W \-Wall \-Wextra \-Wconversion \-fPIC \-fstrict\-aliasing \-Wstrict\-aliasing=2
\-Wno\-long\-long \-g \-O2 \-pthread \-MT decaf/internal/util/libactivemq_cpp_la\-HexStringParser.lo
\-MD \-MP \-MF decaf/internal/util/.deps/libactivemq_cpp_la\-HexStringParser.Tpo \-c decaf/internal/util/HexStringParser.cpp
 \-fPIC \-DPIC \-o decaf/internal/util/.libs/libactivemq_cpp_la\-HexStringParser.o
decaf/internal/util/{color:red}HexStringParser.cpp:28:26: error: apr_strmatch.h: No such file
or directory{color}
make\[3]: \*\*\* \[decaf/internal/util/libactivemq_cpp_la\-HexStringParser.lo] Error 1
make\[2]: \*\*\* \[all\-recursive] Error 1
make\[1]: \*\*\* \[all] Error 2
make: \*\*\* \[os_release] Error 2

The file it cannot find, {{apr_strmatch.h}}, comes from apr-util.
> Remove linkage to APR-Util
> --------------------------
>                 Key: AMQCPP-469
>                 URL:
>             Project: ActiveMQ C++ Client
>          Issue Type: Improvement
>          Components: Decaf
>    Affects Versions: 3.6.0
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>            Priority: Minor
>             Fix For: 3.7.0
> Next release won't need APR-Util, update the scripts and dev projects to remove the linkage.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message