[
https://issues.apache.org/jira/browse/THRIFT-730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12912364#action_12912364
]
Todd Lipcon commented on THRIFT-730:
------------------------------------
Something like this should do the trick:
{noformat}
# Check whether the C++ compiler works.
AC_DEFUN([rw_PROG_CXX_WORKS],
[AC_REQUIRE([AC_PROG_CXX])dnl
AC_CACHE_CHECK([whether the C++ compiler works],
[rw_cv_prog_cxx_works],
[AC_LANG_PUSH([C++])
AC_LINK_IFELSE([AC_LANG_PROGRAM([], [])],
[rw_cv_prog_cxx_works=yes],
[AC_MSG_FAILURE([c++ compiler does not work])])
AC_LANG_POP([C++])])
])
rw_PROG_CXX_WORKS
{noformat}
> configure should check for g++ before checking for boost
> --------------------------------------------------------
>
> Key: THRIFT-730
> URL: https://issues.apache.org/jira/browse/THRIFT-730
> Project: Thrift
> Issue Type: Bug
> Affects Versions: 0.2
> Reporter: Todd Lipcon
>
> The configure script that's generated fails the "checking for boost" part if
> g++ is not installed. This confuses people into thinking something's wrong
> with the boost installation, whereas in fact missing g++ is the issue. A g++
> check should be moved in front of the boost check.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
