- Boost-users - lists.boost.org

[serialization] strange assert with wrong cid
by Sergey Skorniakov 05 Jul '05

05 Jul '05

Hello, All! sometimes I got errors in basic_iarchive_impl::load_pointer in line assert(new_cid == cid). Can anyone tell me what exactly this assertion means and whan it can occurs? Is this error posiible if I remove some BOOST_CLASS_EXPORTs from my code and try to load old files? With best regards, Sergey

2 4

Re: [Boost-users] Building on AIX
by Mark.Gibbons＠jpmorgan.com 05 Jul '05

05 Jul '05

Toon I think that's probably my simplest option. I'm also trying to get gcc working as well though and am getting errors on that too. regards -Mark ---------------------------------------------------------------------------------- FX Options and Commodities AD INTL +44-207-742-0982 GDP 742-0982 Mobile +44-7808682149 |---------+-----------------------------------> | | Toon Knapen | | | <toon.knapen(a)fft.be> | | | Sent by: | | | boost-users-bounces@list| | | s.boost.org | | | | | | | | | 04/07/2005 15:26 | | | Please respond to | | | boost-users | | | | |---------+-----------------------------------> >------------------------------------------------------------------------------------------------------------------------------| | | | To: boost-users(a)lists.boost.org | | cc: | | Subject: Re: [Boost-users] Building on AIX | >------------------------------------------------------------------------------------------------------------------------------| Mark.Gibbons(a)jpmorgan.com wrote: > Hi > I'm trying to build Boost 1_32_0 on AIX using vacpp/xlc 5.0. > I strongly suggest to upgrade to at least version 6.0. Version 7 has been released also for some time and I'm sure it performs even better than version 6 although I have not tested it yet. _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates.

2 1

Possible bug in 1.33 Serialization
by Brett Carswell 05 Jul '05

05 Jul '05

Hi All, We've been doing some testing with the 1.33 CVS Head and there appears to be a bug in the xml serialization. If the tag name has a 0 character in it (not at the start) an exception is thrown. Looking in the source for basic_xml_oarchive.ipp it seems like there is an error in the lookup_table array. Where it's trying to allow 0-9 and the : char to be valid it is actually allowing 1-9 : and ;. Anyone else experienced this or have I got the wrong end of the stick? Cheers, Brett

2 1

[preprocessor] What is AUTO_REC doing?
by Jason 05 Jul '05

05 Jul '05

Hi, I'm a fresh hand on boost library. I am now trying to read the source of preprocessor lib, and get stuck with AUTO_REC. Could anyone tell me what it is meant to do? Thanks! Jason

2 1

boost::lambda::bind question
by Vishnevetsky, Eugene (IT) 04 Jul '05

04 Jul '05

Is it possible to use boost::ref() or boost::lambda::var() of an abstract class as a parameter to boost::lambda::bind()? It seems that compiler attempts to instantiate an object of that abstract class. Example: ----------------- using namespace boost; using namespace boost::lambda; class Y { public: virtual void foo() = 0; void foo2 (){ } }; class Z : public Y { public: void foo(){} }; class TT { public: void test( Y& y ) { y.foo2(); } }; int main() { std::vector<TT> xt; Z z; Y &y = z; std::for_each (xt.begin(), xt.end(), bind(&TT::test,_1, ref(y))); return 0; } ---------------------- And Error message from g++ (GCC) 3.2.3: --------------------------------- /boost/tuple/detail/tuple_basic.hpp: In instantiation of `boost::tuples::cons<Y, boost::tuples::null_type>': /boost/tuple/detail/tuple_basic.hpp:326: instantiated from `boost::tuples::cons<boost::tuples::null_type, boost::tuples::cons<Y, boost::tuples::null_type> >' /boost/tuple/detail/tuple_basic.hpp:326: instantiated from `boost::tuples::cons<void (TT::*const)(Y&), boost::tuples::cons<boost::tuples::null_type, boost::tuples::cons<Y, boost::tuples::null_type> > >' /boost/lambda/detail/lambda_functor_base.hpp:151: instantiated from `boost::lambda::detail::has_null_type<boost::tuples::cons<void (TT::*const)(Y&), boost::tuples::cons<boost::tuples::null_type, boost::tuples::cons<Y, boost::tuples::null_type> > > >' /boost/lambda/detail/lambda_functor_base.hpp:229: instantiated from `boost::lambda::detail::deduce_non_ref_argument_types<boost::tuples::tup le<void (TT::*const)(Y&), const boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, Y&, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type>, boost::tuples::null_type>' /boost/lambda/detail/lambda_functor_base.hpp:412: instantiated from `boost::lambda::lambda_functor_base<boost::lambda::action<3, boost::lambda::function_action<3, boost::lambda::detail::unspecified> >, boost::tuples::tuple<void (TT::*const)(Y&), const boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, Y&, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> >::sig<boost::tuples::null_type>' /boost/lambda/detail/lambda_functors.hpp:135: instantiated from `boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost: :lambda::action<3, boost::lambda::function_action<3, boost::lambda::detail::unspecified> >, boost::tuples::tuple<void (TT::*const)(Y&), const boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, Y&, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> > >' lamtest.cpp:35: instantiated from here /boost/tuple/detail/tuple_basic.hpp:320: cannot declare field `boost::tuples::cons<Y, boost::tuples::null_type>::head' to be of type `Y' /boost/tuple/detail/tuple_basic.hpp:320: because the following virtual functions are abstract: lamtest.cpp:12: virtual void Y::foo() ---------------------------------------- Thanks, Eugene Vishnevetsky -------------------------------------------------------- NOTICE: If received in error, please destroy and notify sender. Sender does not waive confidentiality or privilege, and use is prohibited.

2 1

Building on AIX
by Mark.Gibbons＠jpmorgan.com 04 Jul '05

04 Jul '05

Hi I'm trying to build Boost 1_32_0 on AIX using vacpp/xlc 5.0. I've managed to build bjam with with xlc but I'm not sure if I need Python to run the Boost build. I get the following "error" when I run the build: u307325@ubri72:/vobs/fxsystems/fxorapido/external/boost_1_32_0>bjam "-sTOOLS=vacpp" --------------------------------------------------------------------- skipping Boost.Python library build due to missing or incorrect configuration couldn't find Python.h in "/usr/local/include/python2.2" You can configure the location of your python installation by setting: PYTHON_ROOT - currently "/usr/local" PYTHON_VERSION - The 2-part python Major.Minor version number (e.g. "2.2", NOT "2.2.1") - currently "2.2" The following are automatically configured from PYTHON_ROOT if not otherwise set: PYTHON_LIB_PATH - path to Python library object; currently "/usr/local/lib/python2.2/config" PYTHON_INCLUDES - path to Python #include directories; currently "/usr/local/include/python2.2" --------------------------------------------------------------------- regards -Mark ---------------------------------------------------------------------------------- FX Options and Commodities AD INTL +44-207-742-0982 GDP 742-0982 Mobile +44-7808682149 This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates.

3 2

Re: [Boost-users] Building on AIX
by Mark.Gibbons＠jpmorgan.com 04 Jul '05

04 Jul '05

Rene thanks. One step further! Now I've got it building on the first file I get this error which is repeated for subsequent files: ************************************* xlc-C++-action bin/boost/libs/date_time/build/libboost_date_time.so/vacpp/debug/greg_month.o "/view/gibbonsm/vobs/fxsystems/fxorapido/external/boost_1_32_0/boost/detail/shared_count.hpp", line 366.27: 1540-0152 (W) A template dependent name that is a type must be qualified with "typename". "/view/gibbonsm/vobs/fxsystems/fxorapido/external/boost_1_32_0/boost/shared_ptr.hpp", line 85.86: 1540-0152 (W) A template dependent name that is a type must be qualified with "typename". "/view/gibbonsm/vobs/fxsystems/fxorapido/external/boost_1_32_0/boost/shared_ptr.hpp", line 197.25: 1540-0152 (W) A template dependent name that is a type must be qualified with "typename". "/view/gibbonsm/vobs/fxsystems/fxorapido/external/boost_1_32_0/boost/shared_ptr.hpp", line 221.28: 1540-0152 (W) A template dependent name that is a type must be qualified with "typename". "/view/gibbonsm/vobs/fxsystems/fxorapido/external/boost_1_32_0/boost/shared_ptr.hpp", line 434.37: 1540-0152 (W) A template dependent name that is a type must be qualified with "typename". "/view/gibbonsm/vobs/fxsystems/fxorapido/external/boost_1_32_0/boost/shared_ptr.hpp", line 434.76: 1540-0152 (W) A template dependent name that is a type must be qualified with "typename". "/view/gibbonsm/vobs/fxsystems/fxorapido/external/boost_1_32_0/boost/date_time/period.hpp", line 54.35: 1540-0716 (S) The template argument "boost::date_time::period" does not match the template parameter "class T". "/view/gibbonsm/vobs/fxsystems/fxorapido/external/boost_1_32_0/boost/date_time/int_adapter.hpp", line 475.3: 1540-0152 (W) A template dependent name that is a type must be qualified with "typename". "/view/gibbonsm/vobs/fxsystems/fxorapido/external/boost_1_32_0/boost/date_time/int_adapter.hpp", line 476.14: 1540-0152 (W) A template dependent name that is a type must be qualified with "typename". "/view/gibbonsm/vobs/fxsystems/fxorapido/external/boost_1_32_0/boost/date_time/date_duration.hpp", line 25.36: 1540-0716 (S) The template argument "boost::date_time::date_duration" does not match the template parameter "class T". "/view/gibbonsm/vobs/fxsystems/fxorapido/external/boost_1_32_0/boost/mpl/aux_/integral_wrapper.hpp", line 69.13: 1540-0152 (W) A template dependent name that is a type must be qualified with "typename". "/view/gibbonsm/vobs/fxsystems/fxorapido/external/boost_1_32_0/boost/mpl/aux_/integral_wrapper.hpp", line 70.13: 1540-0152 (W) A template dependent name that is a type must be qualified with "typename". xlC: 1501-230 Internal compiler error; please contact your Service Representative xlC -c -I/view/gibbonsm/vobs/fxsystems/fxorapido/external/boost_1_32_0 -DBOOST_ALL_DYN_LINK=1 -qNOOPTimize -qnoinline -g -qfullpath -qnotempinc -qfuncsect -qeh -qrtti -I"bin/boost/libs/date_time/build" -I"/view/gibbonsm/vobs/fxsystems/fxorapido/external/boost_1_32_0" -o "bin/boost/libs/date_time/build/libboost_date_time.so/vacpp/debug/greg_month.o" "/view/gibbonsm/vobs/fxsystems/fxorapido/external/boost_1_32_0/libs/date_time/build/../src/gregorian/greg_month.cpp" ...failed xlc-C++-action bin/boost/libs/date_time/build/libboost_date_time.so/vacpp/debug/greg_month.o... ...skipped <@boost!libs!date_time!build/libboost_date_time.so/vacpp/debug>libboost_date_time-xlc-d-1_32.so for lack of <@boost!libs!date_time!build/libboost_date_time.so/vacpp/debug>greg_month.o... ...skipped <@boost!lib>libboost_date_time-xlc-d-1_32.so for lack of <@boost!libs!date_time!build/libboost_date_time.so/vacpp/debug>libboost_date_time-xlc-d-1_32.so... xlc-C++-action bin/boost/libs/date_time/build/libboost_date_time.so/vacpp/debug/threading-multi/greg_month.o ^C...interrupted ************************************* I'm using VACPP v5. Any ideas? If I use gcc 'bjam "-sTOOLS=gcc" stage' I get: Reading specs from /opt/freeware/lib/gcc-lib/powerpc-ibm-aix5.1.0.0/3.3.2 /specs Configured with: ../configure --with-as=/usr/bin/as --with-ld=/usr/bin/ld --disable-nls --enable-languages=c,c++ --prefix=/opt/freeware --enable-threads --enable-version-specific-runtime-libs --host=powerpc-ibm-aix5.1.0.0 Thread model: aix gcc version 3.3.2 ************************************* ...found 4449 targets... ...updating 154 targets... gcc-Link-action bin/boost/libs/date_time/build/libboost_date_time.so/gcc/debug/shared-linkable-true/libboost_date_time-gcc-d-1_32.so set -e LIBPATH=bin/boost/libs/date_time/build/libboost_date_time.so/gcc/debug/shared-linkable-true:$LIBPATH export LIBPATH "g++" -g -fPIC -shared -o "bin/boost/libs/date_time/build/libboost_date_time.so/gcc/debug/shared-linkable-true/libboost_date_time-gcc-d-1_32.so" "bin/boost/libs/date_time/build/libboost_date_time.so/gcc/debug/shared-linkable-true/greg_month.o" "bin/boost/libs/date_time/build/libboost_date_time.so/gcc/ debug/shared-linkable-true/greg_weekday.o" "bin/boost/libs/date_time/build/libboost_date_time.so/gcc/debug/shared-linkable-true/date_generators.o" ...failed gcc-Link-action bin/boost/libs/date_time/build/libboost_date_time.so/gcc/debug/shared-linkable-true/libboost_date_time-gcc-d-1_32.so... ...skipped <@boost!lib>libboost_date_time-gcc-d-1_32.so for lack of <@boost!libs!date_time!build/libboost_date_time.so/gcc/debug/shared-linkable-true>libboos t_date_time-gcc-d-1_32.so... gcc-Link-action bin/boost/libs/date_time/build/libboost_date_time.so/gcc/debug/shared-linkable-true/threading-multi/libboost_date_time-gcc-mt-d-1_32.so set -e LIBPATH=bin/boost/libs/date_time/build/libboost_date_time.so/gcc/debug/shared-linkable-true/threading-multi:$LIBPATH export LIBPATH "g++" -g -pthread -fPIC -shared -o "bin/boost/libs/date_time/build/libboost_date_time.so/gcc/debug/shared-linkable-true/threading-multi/libboost_dat e_time-gcc-mt-d-1_32.so" "bin/boost/libs/date_time/build/libboost_date_time.so/gcc/debug/shared-linkable-true/threading-multi/greg_month.o" "bin/boost/lib s/date_time/build/libboost_date_time.so/gcc/debug/shared-linkable-true/threading-multi/greg_weekday.o" "bin/boost/libs/date_time/build/libboost_date_time.so/ gcc/debug/shared-linkable-true/threading-multi/date_generators.o" -lrt ...failed gcc-Link-action bin/boost/libs/date_time/build/libboost_date_time.so/gcc/debug/shared-linkable-true/threading-multi/libboost_date_time-gcc-mt-d-1_3 2.so... ...skipped <@boost!lib>libboost_date_time-gcc-mt-d-1_32.so for lack of <@boost!libs!date_time!build/libboost_date_time.so/gcc/debug/shared-linkable-true/thre ading-multi>libboost_date_time-gcc-mt-d-1_32.so... gcc-Link-action bin/boost/libs/date_time/build/libboost_date_time.so/gcc/release/shared-linkable-true/libboost_date_time-gcc-1_32.so set -e LIBPATH=bin/boost/libs/date_time/build/libboost_date_time.so/gcc/release/shared-linkable-true:$LIBPATH export LIBPATH "g++" -s -fPIC -shared -o "bin/boost/libs/date_time/build/libboost_date_time.so/gcc/release/shared-linkable-true/libboost_date_time-gcc-1_32.so" "bin/boost/libs/date_time/build/libboost_date_time.so/gcc/release/shared-linkable-true/greg_month.o" "bin/boost/libs/date_time/build/libboost_date_time.so/gc c/release/shared-linkable-true/greg_weekday.o" "bin/boost/libs/date_time/build/libboost_date_time.so/gcc/release/shared-linkable-true/date_generators.o" In stderr I see: ld: 0711-317 ERROR: Undefined symbol: .pthread_mutex_init ld: 0711-317 ERROR: Undefined symbol: .pthread_mutex_destroy ld: 0711-317 ERROR: Undefined symbol: .pthread_mutex_lock ld: 0711-317 ERROR: Undefined symbol: .pthread_mutex_unlock ld: 0711-345 Use the -bloadmap or -bnoquiet option to obtain more information. collect2: ld returned 8 exit status collect2: library librt not found ld: 0711-317 ERROR: Undefined symbol: .pthread_mutex_lock ld: 0711-317 ERROR: Undefined symbol: .pthread_mutex_unlock ld: 0711-317 ERROR: Undefined symbol: .pthread_mutex_init ld: 0711-317 ERROR: Undefined symbol: .pthread_mutex_destroy ld: 0711-345 Use the -bloadmap or -bnoquiet option to obtain more information. collect2: ld returned 8 exit status collect2: library librt not found ld: 0711-317 ERROR: Undefined symbol: .pthread_mutex_lock ld: 0711-317 ERROR: Undefined symbol: .pthread_mutex_unlock ld: 0711-317 ERROR: Undefined symbol: .pthread_mutex_init ld: 0711-317 ERROR: Undefined symbol: .pthread_mutex_destroy ld: 0711-345 Use the -bloadmap or -bnoquiet option to obtain more information. collect2: ld returned 8 exit status collect2: library librt not found ld: 0711-317 ERROR: Undefined symbol: .pthread_mutex_lock ld: 0711-317 ERROR: Undefined symbol: .pthread_mutex_unlock ld: 0711-317 ERROR: Undefined symbol: .pthread_mutex_init ld: 0711-317 ERROR: Undefined symbol: .pthread_mutex_destroy ld: 0711-345 Use the -bloadmap or -bnoquiet option to obtain more information. collect2: ld returned 8 exit status collect2: library librt not found ld: 0711-317 ERROR: Undefined symbol: .pthread_mutex_init ld: 0711-317 ERROR: Undefined symbol: .pthread_mutex_lock ld: 0711-317 ERROR: Undefined symbol: .pthread_mutex_unlock ************************************* TIA -Mark |---------+-----------------------------------> | | Rene Rivera | | | <grafik.list@redshift-so| | | ftware.com> | | | Sent by: | | | boost-users-bounces@list| | | s.boost.org | | | | | | | | | 30/06/2005 21:48 | | | Please respond to | | | boost-users | | | | |---------+-----------------------------------> >------------------------------------------------------------------------------------------------------------------------------| | | | To: boost-users(a)lists.boost.org | | cc: | | Subject: Re: [Boost-users] Building on AIX | >------------------------------------------------------------------------------------------------------------------------------| Mark.Gibbons(a)jpmorgan.com wrote: > Hi > I'm trying to build Boost 1_32_0 on AIX using vacpp/xlc 5.0. > > I've managed to build bjam with with xlc but I'm not sure if I need Python > to run the Boost build. You don't need it. You only need it if you want to use the Boost.Python C++ to/from Python binding library. > I get the following "error" when I run the build: It's more of a warning. You can ignore it if you don't care about Boost.Python. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - Grafik/jabber.org _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates.

2 1

bjam's need of boost-build.jam
by Oliver Schoenborn 04 Jul '05

04 Jul '05

Hi, Is there a way of specifying the boost-build dir in the top-level Jamfile of a project? It seems like it can only be done in the boost-build.jam file (using environment var is not an option here). Seems like a bit of a cludge to have to use yet another file to specify that. Thanks, Oliver

5 5

Re: [Boost-users] Problem with boost::filesystem::copy_file
by tong wang 03 Jul '05

03 Jul '05

Could you be more specific? what should i do to solve the problem? thanks a lot ----- Original Message ----- From: Jan Stetka <janpstetka(a)supanet.com> Date: Sunday, July 3, 2005 11:19 am Subject: Re: [Boost-users] Problem with boost::filesystem::copy_file > Is not trying to support 98/ME an option? > > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-users >

1 0

Problem with boost::filesystem::copy_file
by alice.johnson＠sophos.com 03 Jul '05

03 Jul '05

Hi, I think I've found a problem with this function. On Windows 98/Me computers, it can fail with path not found error (3) if the from path is on a network share. I would suggest the following change to src\filesystem\operations_posix_windows.cpp: Currently: if ( !::CopyFileA( from_file_ph.string().c_str(), to_file_ph.string().c_str(), /*fail_if_exists=*/true ) ) Suggested change: if ( !::CopyFileA( from_file_ph.native_file_string().c_str(), to_file_ph.native_file_string().c_str(), /*fail_if_exists=*/true ) ) There may be other areas in the filesystem code where it would be better to use native_file_string(). Alice

3 2