[
https://issues.apache.org/jira/browse/AMQCPP-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antonio L updated AMQCPP-684:
-----------------------------
Description:
I am having a hard time coercing ActiveMQ to reuse the OpenSSL installation
from .pc files.
PKG_CONFIG executable is in a different path, for this reason I am passing it
as an ENV VAR to the configure script. However I find that on my local
installation that complains about PKG_CONFIG_PATH not being set so I was
wondering if there was any way to pass that to ActiveMQ-cpp configure script?
I look at the build32/Makefile and I see that all the OpenSSL related variables
are empty, despite that the configure script reports OpenSSL as being "found".
I also tried passing manually the LIBS environment var (-lssl -lcrypto) but
despite that when I try building against that I get lot of missing SLL related
symbols despite being able to create the ActiveMQ-CPP static library. But that
is a separate problem.
I find this is solved by patching manually the generated .pc file:
*Libs: -L${libdir} -lactivemq-cpp -lpthread -ldl -luuid -lssl -lcrypto*
Also another problem: at my company we tend to have 2 binaries for apr-1-config
with the bitness suffix: apr-1-config-32 apr-1-config-64. ActiveMQ has a hard
time parsing the --with-apr flag as it creates the corresponding .pc file with
the full path of apr-1-config instead of "apr-1" dependency name which is the
name of the corresponding .pc file.
Can you advise on those ./configure glitches I found?
was:
I am having a hard time coercing ActiveMQ to reuse the OpenSSL installation
from .pc files.
PKG_CONFIG executable is in a different path, for this reason I am passing it
as an ENV VAR to the configure script. However I find that on my local
installation that complains about PKG_CONFIG_PATH not being set so I was
wondering if there was any way to pass that to ActiveMQ-cpp configure script?
I look at the build32/Makefile and I see that all the OpenSSL related variables
are empty, despite that the configure script reports OpenSSL as being "found".
I also tried passing manually the LIBS environment var (-lssl -lcrypto) but
despite that when I try building against that I get lot of missing SLL related
symbols despite being able to create the ActiveMQ-CPP static library. But that
is a separate problem.
I find this is solved by patching manually the generated .pc file:
*Libs: -L${libdir} -lactivemq-cpp -lpthread -ldl -luuid -lssl -lcrypto*
Also another problem: at my company we tend to have 2 binaries for apr-1-config
with the bitness suffix: apr-1-config-32 apr-1-config-64. ActiveMQ has a hard
time parsing the --with-apr flag as it creates the corresponding .pc file with
the
Can you advise on those ./configure glitches I found?
> Allow supplying of PKG_CONFIG_PATH
> ----------------------------------
>
> Key: AMQCPP-684
> URL: https://issues.apache.org/jira/browse/AMQCPP-684
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Affects Versions: 3.9.5
> Reporter: Antonio L
> Assignee: Timothy A. Bish
> Priority: Major
>
> I am having a hard time coercing ActiveMQ to reuse the OpenSSL installation
> from .pc files.
> PKG_CONFIG executable is in a different path, for this reason I am passing it
> as an ENV VAR to the configure script. However I find that on my local
> installation that complains about PKG_CONFIG_PATH not being set so I was
> wondering if there was any way to pass that to ActiveMQ-cpp configure script?
> I look at the build32/Makefile and I see that all the OpenSSL related
> variables are empty, despite that the configure script reports OpenSSL as
> being "found".
> I also tried passing manually the LIBS environment var (-lssl -lcrypto) but
> despite that when I try building against that I get lot of missing SLL
> related symbols despite being able to create the ActiveMQ-CPP static library.
> But that is a separate problem.
> I find this is solved by patching manually the generated .pc file:
> *Libs: -L${libdir} -lactivemq-cpp -lpthread -ldl -luuid -lssl -lcrypto*
> Also another problem: at my company we tend to have 2 binaries for
> apr-1-config with the bitness suffix: apr-1-config-32 apr-1-config-64.
> ActiveMQ has a hard time parsing the --with-apr flag as it creates the
> corresponding .pc file with the full path of apr-1-config instead of "apr-1"
> dependency name which is the name of the corresponding .pc file.
> Can you advise on those ./configure glitches I found?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
