[
https://issues.apache.org/jira/browse/THRIFT-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Duxbury updated THRIFT-1054:
----------------------------------
Description:
>From aclocal.m4:
{code}
# Note that if there is a possibility the first call to
# PKG_CHECK_MODULES might not happen, you should be sure to include an
# explicit call to PKG_PROG_PKG_CONFIG in your configure.ac
{code}
I believe the first call to PKG_CHECK_MODULE is the only one that is expanded
by m4 into the detection and setup of the pkg-config variables. Because this
call isn't always executed, future calls to PKG_CHECK_MODULE attempt to use
pkg-config and can't find it. aclocal.m4 warns against this situation and
proposes calling PKG_PROG_PKG_CONFIG.
The fix looks like an explicit PKG_PROG_PKG_CONFIG should be added to
configure.ac
was:
>From aclocal.m4:
# Note that if there is a possibility the first call to
# PKG_CHECK_MODULES might not happen, you should be sure to include an
# explicit call to PKG_PROG_PKG_CONFIG in your configure.ac
I believe the first call to PKG_CHECK_MODULE is the only one that is expanded
by m4 into the detection and setup of the pkg-config variables. Because this
call isn't always executed, future calls to PKG_CHECK_MODULE attempt to use
pkg-config and can't find it. aclocal.m4 warns against this situation and
proposes calling PKG_PROG_PKG_CONFIG.
The fix looks like an explicit PKG_PROG_PKG_CONFIG should be added to
configure.ac
> explicit call to PKG_PROG_PKG_CONFIG is missing and first use of
> PKG_CHECK_MODULES may not happen, causes mono detection to fail
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: THRIFT-1054
> URL: https://issues.apache.org/jira/browse/THRIFT-1054
> Project: Thrift
> Issue Type: Bug
> Affects Versions: 0.7
> Environment: Kubuntu 10.10 (Maverick)
> Reporter: Chris Morgan
> Assignee: Bryan Duxbury
> Attachments: configure_ac_pkg_config_check.patch
>
>
> From aclocal.m4:
> {code}
> # Note that if there is a possibility the first call to
> # PKG_CHECK_MODULES might not happen, you should be sure to include an
> # explicit call to PKG_PROG_PKG_CONFIG in your configure.ac
> {code}
> I believe the first call to PKG_CHECK_MODULE is the only one that is expanded
> by m4 into the detection and setup of the pkg-config variables. Because this
> call isn't always executed, future calls to PKG_CHECK_MODULE attempt to use
> pkg-config and can't find it. aclocal.m4 warns against this situation and
> proposes calling PKG_PROG_PKG_CONFIG.
> The fix looks like an explicit PKG_PROG_PKG_CONFIG should be added to
> configure.ac
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
