Thanks for the info, Tom!
Anyway, I made following changes to the configure.in script and it
worked. Don't know whether they are correct.
AC_MSG_CHECKING([for boost])
AC_LANG(C++)
safe_CXXFLAGS=$CXXFLAGS
safe_LIBS=$LIBS
# CXXFLAGS="-lboost_thread-mt $mflag_primary"
CXXFLAGS="$mflag_primary"
LIBS="-lboost_thread-mt $LIBS"
BST_FLAGS="$CXXFLAGS $LIBS"
AC_LINK_IFELSE([AC_LANG_SOURCE([
#include <boost/thread.hpp>
static void thread_func(void)
{ }
int main(int argc, char** argv)
{
boost::thread t(thread_func);
return 0;
}
])],
[
ac_have_boost_1_35=yes
AC_SUBST([BOOST_CFLAGS], [])
# AC_SUBST([BOOST_LIBS], ["${CXXFLAGS}"])
AC_SUBST([BOOST_LIBS], ["${BST_FLAGS}"])
AC_MSG_RESULT([yes])
], [
ac_have_boost_1_35=no
AC_MSG_RESULT([no])
])
LIBS=$safe_LIBS
CXXFLAGS=$safe_CXXFLAGS
AC_LANG(C)
AM_CONDITIONAL([HAVE_BOOST_1_35], [test x$ac_have_boost_1_35 = xyes])
Now the commandline generated to build the test code is:
g++ -o conftest -m64 conftest.cpp -lboost_thread-mt
Thanks and regards,
~Plug
On Wed, Apr 18, 2012 at 3:49 PM, Tom Hughes <[email protected]> wrote:
> On 18/04/12 15:28, Plug Gulp wrote:
>
>> Is the above build failure the reason why Valgrind configure script
>> thinks that boost is not available on the system? How do I fix the
>> configure.in file to help Valgrind detect Boost?
>
>
> Boost is not used by valgrind itself, so I wouldn't worry too much if
> configure can't find it. It just means some of the tests won't be able to be
> built.
>
> Tom
>
> --
> Tom Hughes ([email protected])
> http://compton.nu/
------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users
