Re: [C++-sig] boost python calling conventions support patch submission (__stdcall, __cdecl, __fastcall)
Thanks Dave, not quite sure of it, but it looks like you added the unit tests to the Jamfile, but you did not add the tests source code to the svn, did I miss something. Also, the tests i submitted do not consider the compiler brand/version, so they may fail on compilers that do not have the Microsoft calling conventions. Did you consider that point ? Best regards, Nicolas. Le 24/01/2010 03:10, David Abrahams a écrit : At Fri, 15 Jan 2010 18:09:36 +0100, Nicolas Lelong wrote: My previous mail once again got lost, gotta be more careful... Changes (by dave): This looks terrific! I'll try to get it applied ASAP. Please poke me if you don't see it in trunk by the end of the week. Thanks ! As I didn't see the batch in trunk today, I poke you :) Applied; thanks for your patience. ___ Cplusplus-sig mailing list Cplusplus-sig@python.org http://mail.python.org/mailman/listinfo/cplusplus-sig
Re: [C++-sig] boost python calling conventions support patch submission (__stdcall, __cdecl, __fastcall)
At Mon, 25 Jan 2010 10:47:06 +0100, Nicolas Lelong wrote: > > Thanks Dave, > > not quite sure of it, but it looks like you added the unit tests to > the Jamfile, but you did not add the tests source code to the svn, > did I miss something. Gah, I hate SVN. > Also, the tests i submitted do not consider the compiler > brand/version, so they may fail on compilers that do not have the > Microsoft calling conventions. Did you consider that point ? No! The next question is, should defining the macros to turn on calling convention support cause an error on platforms where they're not supported (which would imply XML markup for those tests and/or #ifdef _MSC_VER in the tests themselves) or should it be benign (implying #ifdef _MSC_VER in the library files)? Your opinion? -- Dave Abrahams Meet me at BoostCon: http://www.boostcon.com BoostPro Computing http://www.boostpro.com ___ Cplusplus-sig mailing list Cplusplus-sig@python.org http://mail.python.org/mailman/listinfo/cplusplus-sig
Re: [C++-sig] Please help: boost python 1.41 extension problem
On Fri, 2010-01-22 at 17:29 -0800, lin yun wrote: > Hi, > > I am trying to install boost 1.41 on Redhat Enterprise Linux 5.3 and I > got problem with the extension test. Following the instructions here: > http://www.boost.org/doc/libs/1_41_0/libs/python/doc/building.html > * I built boost python using bjam. > * cd into the libs/python/example/quickstart/ directory > * bjam toolset=gcc --verbose-test test > Now I see embedding test passes while extension test failed. I got the > same problem with boost 1.35, 1.37 on Fedora 7. Below is the error > messages: > > ../../../../boost/type_traits/detail/cv_traits_impl.hpp:37: internal > compiler error: in make_rtl_for_nonlocal_decl, at cp/decl.c:5067 > > Please submit a full bug report, > > with preprocessed source if appropriate. > > See http://bugzilla.redhat.com/bugzilla> for instructions. > Your error message indicates a gcc internal error. While it's probably due at least in part to something unusual in your code or boost::python, that kind of stuff should cause gcc to exit more gracefully (and informatively) than this. You might learn something by reporting your error message either to the gcc developers (or Red Hat, since they're more directly responsible for the binary you have). At the very least, I imagine they'd like to hear about it. Jim Bosch ___ Cplusplus-sig mailing list Cplusplus-sig@python.org http://mail.python.org/mailman/listinfo/cplusplus-sig
Re: [C++-sig] Please help: boost python 1.41 extension problem
Hi, Jim: Thank you very much for your reply ! I did not mention that I had no problem with Boost 1.34, on the same system. Also I ever tried Boost 1.34 and 1.37 on Fedora 7, I got exactly the same result: Boost 1.34 worked fine while 1.37 failed on extension test. The test I ran was the example test from boost package: libs/python/example/quickstart/, which was recommended in the boost python installation instruction. There was no any personal code involved. I wonder if you, or anyone else had related experience ? Thanks again, Yun On Mon, Jan 25, 2010 at 12:20 PM, Jim Bosch wrote: > On Fri, 2010-01-22 at 17:29 -0800, lin yun wrote: > > Hi, > > > > I am trying to install boost 1.41 on Redhat Enterprise Linux 5.3 and I > > got problem with the extension test. Following the instructions here: > > http://www.boost.org/doc/libs/1_41_0/libs/python/doc/building.html > > * I built boost python using bjam. > > * cd into the libs/python/example/quickstart/ directory > > * bjam toolset=gcc --verbose-test test > > Now I see embedding test passes while extension test failed. I got the > > same problem with boost 1.35, 1.37 on Fedora 7. Below is the error > > messages: > > > > ../../../../boost/type_traits/detail/cv_traits_impl.hpp:37: internal > > compiler error: in make_rtl_for_nonlocal_decl, at cp/decl.c:5067 > > > > Please submit a full bug report, > > > > with preprocessed source if appropriate. > > > > See http://bugzilla.redhat.com/bugzilla> for instructions. > > > > Your error message indicates a gcc internal error. While it's probably > due at least in part to something unusual in your code or boost::python, > that kind of stuff should cause gcc to exit more gracefully (and > informatively) than this. > > You might learn something by reporting your error message either to the > gcc developers (or Red Hat, since they're more directly responsible for > the binary you have). At the very least, I imagine they'd like to hear > about it. > > Jim Bosch > > > > > ___ Cplusplus-sig mailing list Cplusplus-sig@python.org http://mail.python.org/mailman/listinfo/cplusplus-sig
Re: [C++-sig] Please help: boost python 1.41 extension problem
On Mon, 2010-01-25 at 12:38 -0800, lin yun wrote: > I did not mention that I had no problem with Boost 1.34, on the same > system. Also I ever tried Boost 1.34 and 1.37 on Fedora 7, I got > exactly the same result: Boost 1.34 worked fine while 1.37 failed on > extension test. The test I ran was the example test from boost > package: libs/python/example/quickstart/, which was recommended in > the boost python installation instruction. There was no any personal > code involved. > > I wonder if you, or anyone else had related experience ? > I have not, but I haven't tried boost > 1.34.1 on any Red Hat distros. I can confirm that this example compiles successfully with Boost 1.40 and the latest trunk on Ubuntu 9.10 (gcc 4.4.1). You may have noticed the line gcc aborts on: > > > > ../../../../boost/type_traits/detail/cv_traits_impl.hpp:37: > internal > > compiler error: in make_rtl_for_nonlocal_decl, at > cp/decl.c:5067 > > has not changed between Boost 1.34 and 1.35, but it refers to the macro BOOST_STATIC_CONSTANT, which is defined in boost/config/suffix.hpp, and reflects whether a compiler supports in-class initialization of static integral constant members. Perhaps your compiler does not fully support this feature, but boost thinks it does? Try adding the line #define BOOST_NO_INCLASS_MEMBER_INITIALIZATION to boost/config/user.hpp. Then recompile boost. Jim Bosch ___ Cplusplus-sig mailing list Cplusplus-sig@python.org http://mail.python.org/mailman/listinfo/cplusplus-sig
