Actually I have another problem now...
When try to build a python application using boost, I'm getting this error using make.
I tried to use ./b2 cxxflags="-ftemplate-depth=256" as mentioned in this topic https://groups.google.com/forum/#!topic/boost-list/KJXwGcugNEs but didn't make any difference.
Any idea?
Thanks!
[ 1%] Building CXX object src/CMakeFiles/pagmo_static.dir/problem/death_penalty.o
In file included from /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pagmo-code/src/problem/death_penalty.cpp:29:
In file included from /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pagmo-code/src/problem/../types.h:30:
In file included from /usr/local/boost_1_55_0/boost/lexical_cast.hpp:165:
In file included from /usr/local/boost_1_55_0/boost/type_traits/has_left_shift.hpp:43:
In file included from /usr/local/boost_1_55_0/boost/type_traits/detail/has_binary_operator.hpp:15:
/usr/local/boost_1_55_0/boost/type_traits/is_fundamental.hpp:26:20: fatal error: recursive template instantiation exceeded maximum depth
of 128
::boost::is_arithmetic<T>::value
^
/usr/local/boost_1_55_0/boost/type_traits/is_fundamental.hpp:38:64: note: in instantiation of template class
'boost::detail::is_fundamental_impl<const double>' requested here
BOOST_TT_AUX_BOOL_TRAIT_DEF1(is_fundamental,T,::boost::detail::is_fundamental_impl<T>::value)
^
/usr/local/boost_1_55_0/boost/type_traits/detail/bool_trait_def.hpp:69:30: note: expanded from macro 'BOOST_TT_AUX_BOOL_TRAIT_DEF1'
BOOST_TT_AUX_BOOL_C_BASE(C) \
^
/usr/local/boost_1_55_0/boost/type_traits/detail/bool_trait_def.hpp:63:81: note: expanded from macro 'BOOST_TT_AUX_BOOL_C_BASE'
# define BOOST_TT_AUX_BOOL_C_BASE(C) : public ::boost::integral_constant
^
/usr/local/boost_1_55_0/boost/mpl/if.hpp:63:68: note: in instantiation of template class 'boost::is_fundamental<const double>' requested
here
BOOST_MPL_AUX_STATIC_CAST(bool, BOOST_MPL_AUX_VALUE_WKND(T1)::value)
^
/usr/local/boost_1_55_0/boost/mpl/aux_/value_wknd.hpp:57:40: note: expanded from macro 'BOOST_MPL_AUX_VALUE_WKND'
# define BOOST_MPL_AUX_VALUE_WKND(C) C
^
/usr/local/boost_1_55_0/boost/mpl/aux_/static_cast.hpp:24:62: note: expanded from macro 'BOOST_MPL_AUX_STATIC_CAST'
# define BOOST_MPL_AUX_STATIC_CAST(T, expr) static_cast<T>(expr)
^
/usr/local/boost_1_55_0/boost/mpl/eval_if.hpp:37:22: note: in instantiation of template class 'boost::mpl::if_, boost::mpl::eval_if, boost::mpl::eval_if, boost::mpl::eval_if, mpl_::int_<0> > > > >' requested here
typedef typename if_::type f_;
^
/usr/local/boost_1_55_0/boost/mpl/eval_if.hpp:38:22: note: in instantiation of template class
'boost::mpl::eval_if, boost::mpl::eval_if, boost::mpl::eval_if, boost::mpl::eval_if, mpl_::int_<0> > > > >' requested here
typedef typename f_::type type;
^
/usr/local/boost_1_55_0/boost/serialization/level.hpp:53:37: note: in instantiation of template class
'boost::mpl::eval_if,
boost::serialization::implementation_level_impl<const double>::traits_class_level<const double>,
boost::mpl::eval_if, boost::mpl::eval_if, boost::mpl::eval_if, boost::mpl::eval_if, mpl_::int_<0> > > > > >' requested here
BOOST_DEDUCED_TYPENAME mpl::eval_if<
^
/usr/local/boost_1_55_0/boost/serialization/level.hpp:93:12: note: (skipping 119 contexts in backtrace; use -ftemplate-backtrace-limit=0
to see all)
public implementation_level_impl<const T>
^
/usr/local/boost_1_55_0/boost/serialization/export.hpp:66:12: note: in instantiation of member function
'boost::serialization::singleton >::get_const_instance' requested here
>::get_const_instance();
^
/usr/local/boost_1_55_0/boost/serialization/export.hpp:111:5: note: in instantiation of member function
'boost::archive::detail::export_impl::enable_load' requested here
export_impl::enable_load(
^
/usr/local/boost_1_55_0/boost/serialization/export.hpp:95:37: note: in instantiation of member function
'boost::archive::detail::ptr_serialization_support::instantiate'
requested here
&ptr_serialization_support::instantiate
^
/usr/local/boost_1_55_0/boost/serialization/export.hpp:142:9: note: in instantiation of member function
'boost::archive::detail::extra_detail::guid_initializerpagmo::problem::death_penalty::export_guid' requested here
export_guid(boost::serialization::is_abstract< T >());
^
/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pagmo-code/src/problem/death_penalty.cpp:206:1: note: in
instantiation of member function
'boost::archive::detail::extra_detail::guid_initializerpagmo::problem::death_penalty::export_guid' requested here
BOOST_CLASS_EXPORT_IMPLEMENT(pagmo::problem::death_penalty)
^
/usr/local/boost_1_55_0/boost/serialization/export.hpp:167:35: note: expanded from macro 'BOOST_CLASS_EXPORT_IMPLEMENT'
>::get_mutable_instance().export_guid(); \
^
/usr/local/boost_1_55_0/boost/type_traits/is_fundamental.hpp:26:20: note: use -ftemplate-depth=N to increase recursive template
instantiation depth
::boost::is_arithmetic<T>::value
^
1 error generated.
make[2]: *** [src/CMakeFiles/pagmo_static.dir/problem/death_penalty.o] Error 1
make[1]: *** [src/CMakeFiles/pagmo_static.dir/all] Error 2
make: *** [all] Error 2
Corentin Hamel
Software Engineer
Rocketboots
Level 11, 189 Kent Street
Sydney NSW 2000
----- Original Message -----
From: "Corentin Hamel"
To: boost-users@lists.boost.org
Sent: Wednesday, 2 April, 2014 11:16:50 AM
Subject: Re: [Boost-users] installing boost getting error "ld: symbol(s) not found for architecture x86_64" on OSX 10.9.2
Works grey!
Thanks a lot!
Corentin Hamel
Software Engineer
Rocketboots
Level 11, 189 Kent Street
Sydney NSW 2000
----- Original Message -----
From: "Steven Watanabe"
To: boost-users@lists.boost.org
Sent: Wednesday, 2 April, 2014 10:24:34 AM
Subject: Re: [Boost-users] installing boost getting error "ld: symbol(s) not found for architecture x86_64" on OSX 10.9.2
AMDG
On 04/01/2014 03:35 PM, Corentin Hamel wrote:
The problem is if I don't specify
include="/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/"*/
I get the following error:
/boost/python/detail/wrap_python.hpp:50:11: fatal error: 'pyconfig.h' file not found
# include
^
1 error generated.
It's failing for the same reason that linking is
failing later. double initialization is corrupting
the python module and preventing the flags from
being passed to the compiler.
Even if using ./b2 --debug-configuration, I can see the python include path well set
notice: [python-cfg] interpreter command: "/Library/Frameworks/Python.framework/Versions/2.7/bin/python"
notice: [python-cfg] include path: "/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7"
notice: [python-cfg] library path: "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/config" "/Library/Frameworks/Python.framework/Versions/2.7/lib"
And here is the full message output but debug configuration. I can't really see anything bad
Both ~/user-config.jam and ./project-config.jam
are trying to set up python. Just delete the
using python ; line from project-config.jam
and you should be good. (This is a bug in the
bootstrap script, which I will fix.)
In Christ,
Steven Watanabe
_______________________________________________
Boost-users mailing list
Boost-users@lists.boost.org
http://lists.boost.org/mailman/listinfo.cgi/boost-users
