August 2005 - Boost-users - lists.boost.org

Re: [Boost-users] Problems: Building Boost with VC7 and STLport 4.6.2
by Jasper, Alexander 15 Aug '05

15 Aug '05

Hi! I had the same problem a few weeks ago. You've got to use the following command line. For debug libs build\bjam.exe -sTOOLS=vc-7_1-stlport "-sBUILD=<define>BOOST_NO_STD_WSTRING" "-sSTLPORT_4.6.2_PATH=D:\Alexander...." "-sstlport-iostreams=on" --with-date_time stage You need to build release libs with an extra step: build\bjam.exe -sTOOLS=vc-7_1-stlport "-sBUILD=release <define>BOOST_NO_STD_WSTRING" "-sSTLPORT_4.6.2_PATH=D:\Alexander...." "-sstlport-iostreams=on" --with-date_time stage This informations is based to 1.32, though. But I think it applies to 1.33 as well. hope this helps Alex > -----Ursprüngliche Nachricht----- > Von: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org]Im Auftrag von Hao Song > Gesendet: Sonntag, 14. August 2005 17:33 > An: boost-users(a)lists.boost.org > Betreff: [Boost-users] Problems: Building Boost with VC7 and STLport > 4.6.2 > > > Hi, > I tried to build Boost with VC7 and STLport 4.6.2, but failed to > compile some source files of Boost.date_time. Error messages are like: > > vc-C++ > E:\CppLibs\boost_1_33_0\temp\bin\boost\libs\date_time\build\bo > ost_date_time.dll\vc7-stlport\release\threading-multi\greg_month.obj > greg_month.cpp > E:\CppLibs\STLport-4.6.2\stlport\stl\_iterator_base.h(98) > : error C2825: > ¡°_Iterator::iterator_category¡±£ºcan not form a qualified name > > E:\CppLibs\boost_1_33_0\boost\date_time\date_parsing.hpp(270) : see > reference to class template instantiation > '_STL::iterator_traits<_Iterator>' > being compiled > with > [ > > _Iterator=_STL::basic_string<char,_STL::char_traits<char>,_STL > ::allocator<char>>::iterator > ] > > E:\CppLibs\boost_1_33_0\boost\date_time\gregorian\parsers.hpp(79) : > see reference to function template instantiation > 'boost::date_time::period<point_rep,duration_rep> > boost::date_time::from_simple_string_type<boost::gregorian::da > te,char>(const > _STL::basic_string<_CharT,_Traits,_Alloc> &)' being compiled > with > [ > point_rep=boost::gregorian::date, > duration_rep=boost::gregorian::date_duration, > _CharT=char, > _Traits=_STL::char_traits<char>, > _Alloc=_STL::allocator<char> > ] > E:\CppLibs\STLport-4.6.2\stlport\stl\_iterator_base.h(98) : > error C2039: > 'iterator_category' : is not a member of 'operator "global > namespace" ' > > And bjam failed to build DLLs > > vc-Link > E:\CppLibs\boost_1_33_0\temp\bin\boost\libs\date_time\build\bo > ost_date_time.dll\vc7-stlport\debug\threading-multi\boost_date > _time-vc7-mt-gdp-1_33.dll > E:\CppLibs\boost_1_33_0\temp\bin\boost\libs\date_time\build\bo > ost_date_time.dll\vc7-stlport\debug\threading-multi\boost_date > _time-vc7-mt-gdp-1_33.lib > LINK : fatal error LNK1181: cannot open input > file¡°stlport_vc6_stldebug.lib¡± > > > > It seems that auto-linking doesn't function properly. but I > can't see why. > any idea about these? Thanks in advance! > > > >

2 1

Is there a way to say that exception is expected/unexpected in Boost.Test-based Test Case?
by Voronkov Konstantin 15 Aug '05

15 Aug '05

Hello, All! I have a question whether there is a way to say that exception is expected/unexpected in Boost.Test-based Test Case? And depends on this the Test Case is threated as passed or failed. Best Regards, Voronkov Konstantin

2 2

Boost.Log for Debian
by martin f krafft 15 Aug '05

15 Aug '05

Dear boosters, Even though not yet official, I've made Debian packages of John Torjo's Boost.Log library, which has been submitted and is under review at the moment. You can find these packages here: http://debian.madduck.net/~madduck/packages/stage/libboost-log/ or install libboost-log-dev directly by including the following line in your /etc/apt/sources.list and the `apt-get update`-ing: deb http://debian.madduck.net ~madduck/packages/stage/libboost-log/ deb-src http://debian.madduck.net ~madduck/packages/stage/libboost-log/ Note /usr/lib/libboost_log.a is a symlink to libboost_log-gcc-mt-s.a in this package, and no other .a files are provided. That is to say that we make multi-threaded libraries the default in Debian boost. Also, because the library is not yet official, I only provide the static libraries, no shared objects (to guard against ABI/SONAME nightmares). I would appreciate feedback and testing. I will upload the library to Debian unstable sometime this week. -- .''`. martin f. krafft <madduck(a)debian.org> : :' : proud Debian developer and author: http://debiansystem.info `. `'` `- Debian - when you have better things to do than fixing a system Invalid/expired PGP (sub)keys? Use subkeys.pgp.net as keyserver! "the problem with america is stupidity. i'm not saying there should be a capital punishment for stupidity, but why don't we just take the safety labels off of everything and let the problem solve itself?" -- seen on irc

1 1

Problems: Building Boost with VC7 and STLport 4.6.2
by Hao Song 14 Aug '05

14 Aug '05

Hi, I tried to build Boost with VC7 and STLport 4.6.2, but failed to compile some source files of Boost.date_time. Error messages are like: vc-C++ E:\CppLibs\boost_1_33_0\temp\bin\boost\libs\date_time\build\boost_date_time.dll\vc7-stlport\release\threading-multi\greg_month.obj greg_month.cpp E:\CppLibs\STLport-4.6.2\stlport\stl\_iterator_base.h(98) : error C2825: ¡°_Iterator::iterator_category¡±£ºcan not form a qualified name E:\CppLibs\boost_1_33_0\boost\date_time\date_parsing.hpp(270) : see reference to class template instantiation '_STL::iterator_traits<_Iterator>' being compiled with [ _Iterator=_STL::basic_string<char,_STL::char_traits<char>,_STL::allocator<char>>::iterator ] E:\CppLibs\boost_1_33_0\boost\date_time\gregorian\parsers.hpp(79) : see reference to function template instantiation 'boost::date_time::period<point_rep,duration_rep> boost::date_time::from_simple_string_type<boost::gregorian::date,char>(const _STL::basic_string<_CharT,_Traits,_Alloc> &)' being compiled with [ point_rep=boost::gregorian::date, duration_rep=boost::gregorian::date_duration, _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] E:\CppLibs\STLport-4.6.2\stlport\stl\_iterator_base.h(98) : error C2039: 'iterator_category' : is not a member of 'operator "global namespace" ' And bjam failed to build DLLs vc-Link E:\CppLibs\boost_1_33_0\temp\bin\boost\libs\date_time\build\boost_date_time.dll\vc7-stlport\debug\threading-multi\boost_date_time-vc7-mt-gdp-1_33.dll E:\CppLibs\boost_1_33_0\temp\bin\boost\libs\date_time\build\boost_date_time.dll\vc7-stlport\debug\threading-multi\boost_date_time-vc7-mt-gdp-1_33.lib LINK : fatal error LNK1181: cannot open input file¡°stlport_vc6_stldebug.lib¡± It seems that auto-linking doesn't function properly. but I can't see why. any idea about these? Thanks in advance!

1 0

PC-Lint issues
by Okko Willeboordse 12 Aug '05

12 Aug '05

When I lint my code, using boost 1-32, using PC-Lint I get some issues on the Boost code. I use 'PC-lint for C/C++ (NT) Vers. 8.00r, Copyright Gimpel Software 1985-2005' so the new patch that should deal with Boost better. These are the issues; BOOST_STATIC_CONSTANT(bool, value = helper::value); C:\Boost\include\boost-1_32\boost\type_traits\is_enum.hpp(143): error 1061: (Error -- public member 'boost::mpl::bool_<<1>>::value' is not accessible through non-public inheritance) BOOST_MPL_HAS_XXX_TRAIT_NAMED_DEF(has_apply, apply, false) C:\Boost\include\boost-1_32\boost\mpl\aux_\has_apply.hpp(22): error 64: (Error -- Type mismatch (arg. no. 1) (volatile const boost::mpl::aux::has_apply_wrapper_<T> * = boost::mpl::aux::has_apply_wrapper_<T> *)) BOOST_MPL_HAS_XXX_TRAIT_NAMED_DEF(has_tag, tag, false) C:\Boost\include\boost-1_32\boost\mpl\aux_\has_tag.hpp(20): error 64: (Error -- Type mismatch (arg. no. 1) (volatile const boost::mpl::aux::has_tag_wrapper_<T> * = boost::mpl::aux::has_tag_wrapper_<T> *)) Are these Boost or PC-Lint issues? Okko These are descriptions of the issues; 1061 String member 'Symbol' is not accessible through non-public inheritance -- There is an attempt to access a private, protected or public member (the text of the message indicates which kind as well as which member) of a class through a class derived from the original. There is an access violation (see 1060 for the more common access violation) critically dependent on the fact that the inheritance relationship is non-public. [11 section 11.2] 64 Type mismatch (Context) (TypeDiff) -- There was a mismatch in types across an assignment (or implied assignment, see Context). TypeDiff specifies the type difference. See options -epn, -eps, -epu, -epp (Section 5.2 Error Inhibition Options) to suppress this message when assigning some kinds of pointers.

2 2

Broken link on new stite
by Delfin Rojas 12 Aug '05

12 Aug '05

Before anything else I would like to congratulate everybody involved with the new site design. I love the color scheme styles and organization - it is really innovative (I had never seen links like that) but I still feel at home like with the old site. That been said, there is a broken link on the main page for the program_options library. The link points to http://www.boost.org/libs/program_options/doc/index.html from which it is redirected to http://www.boost.org/doc/html/program_option.html but the program_options documentation is at http://www.boost.org/doc/html/program_options.html (notice the final s on options). Once more, congratulations on the site. -delfin

2 1

vc-7_1 fails on cvs wave
by Serge Skorokhodov 12 Aug '05

12 Aug '05

Hi, Just for info: vc-7_1 fails to compile wave from the last cvs updated with a bunch of lo-o-ong error messages;) All of them seems to relate to files in detail and ambiguity of 'detail' symbol: boost::detail and boost::spirit::detail. -- Serge

2 1

Re: [Boost-users] numeric/interval overflow & test_float
by Steven Solie 12 Aug '05

12 Aug '05

=?iso-8859-1?Q??= MIME-Version: 1.0 Content-Type: text/plain Guillaume Melquiond wrote: > Unfortunately the output of these tests is a bit poor, since it doesn't > display the parameters causing the failure. I suppose that, since the > overflow test fails on non-double floating-point formats, the same > problem must happen for the test_float test. > > Is there any difference in the way AmigaOS deals with floating-point > computations with respect to other PowerPC operating systems like Darwin > or OSX? I don't have a machine that can run Darwin and I haven't used OSX. However, I do know a couple of things about AmigaOS math support: 1. math exceptions such as divide by zero are simply ignored 2. the underlying C library is custom made 3. the C++ library is the one that comes with GCC 3.4.4 I'm suspecting there may be a bug in the C99 library at this point. Since the C library is open source, you can look for yourself at http://sourceforge.net/projects/clib2/ What I'm wondering now is what math functions the failed tests are executing from the C library? Perhaps there is a boundary condition that a math function is not handling correctly or something. Since these tests don't fail on another PowerPC based system I think the problem lies with my platform but I need help narrowing it down a bit more. Thanks! --Steven

2 1

[serialization][1.33.0?] xml_archive_exception
by Jeff Flinn 12 Aug '05

12 Aug '05

Robert, In using xml_archive_exception, I find that I need to #include <boost/archive/basic_xml_archive.hpp>. This required searching through the boost directory since the documentation does not mention this requirement. The only mention in the docs is to #include <boost/archive/archive_exception.hpp>, which is insufficient. I would have expected that xml_archive_exception is part of the interface for an xml_(i|o)archive and would be included when #include-ing <boost/archive/xml_(i|o)archive.hpp>. Alternatively, perhaps this class should be placed in <boost/archive/xml_archive_exception.hpp> and documented as such, to be consistent with <boost/archive/archive_exception.hpp>. Additionally, I find the overlap of exception_code misleading when debugging. I caught an archive_exception& and and code returns 0 - 'no_exception'( within the context of an archive_exception ). At this point what() returns null also. Of course, catching an xml_archive_exception helps because what() returns a reasonable description. I run into the above, when loading a file, but that file was generated by a legacy product(not xml or an archive). I had (erroneously)expected that xml_archive would throw an xml_archive_exception equivalent to exception_code==invalid_signature. It would be nice to have a some better granularity on archive_parsing_error, that would tell me that the input does not start with an xml header, or it's xml but not an xml_archive, or it passed those two, and some other error occurs. Thanks, Jeff Flinn

2 1

[Serialization] 1.33 RC1 nvp.hpp gotcha
by Richard Jennings 12 Aug '05

12 Aug '05

I have found that the requirement that no serialization headers can be included before any archive headers means that you have to be careful which serialization headers you include in your class headers and indeed in what order you include them. In particular if you include serialization/nvp.hpp before serialization/vector.hpp and you use that class in another module that does not use archiving at all then that module will hit the error directive, example below. A solution would seem to be that serialization/nvp.hpp should only be included in the module that includes archive headers. I guess what I would like is some guidance on using serialization as it's become a bit more tricky in my experience. At least you can't willy-nilly include serialization headers in any order in any headers and expect the application to compile. Perhaps it only worked by luck before! For example, given class A below: class A { private: friend class boost::serialization::access; template <class ArchiveT> void serialize(ArchiveT &ar, unsigned int) { ar & BOOST_SERIALIZATION_NVP(m_Vector); } std::vector<int> m_Vector; }; What serialization headers should be included in A's header? What should be included in the header of the class that serializes A? My inclination would be to include serialization/nvp.hpp and serialization/vector.hpp since these are needed if (but only if) the template is instantiated. This is on the idea that a class should (generally) compile on it's own and you should not have to look to see what it is composed of to be able to get it to compile. Here's the example that does not work: B fails to compile with [C++ Fatal Error] basic_archive.hpp(21): F1003 Error directive: "no serialization headers my precede any archive headers" If you include nvp after vector, then it's ok too! A.h: ======= #include <vector> #include <boost/serialization/nvp.hpp> #include <boost/serialization/access.hpp> #include <boost/serialization/vector.hpp> class A { private: friend class boost::serialization::access; template <class ArchiveT> void serialize(ArchiveT &ar, unsigned int) { ar & BOOST_SERIALIZATION_NVP(m_Vector); } std::vector<int> m_Vector; }; ======= B.h: class B { public: B(); }; ======= B.cpp: #include "B.h" #include "A.h" B::B() { A InstanceOfA; } ======= Main.cpp #include <sstream> #include <boost/archive/text_oarchive.hpp> #include "A.h" #include "B.h" int main(int argc, char* argv[]) { A InstanceOfA; B InstanceOfB; std::stringstream ss; boost::archive::text_oarchive oa(ss); oa & InstanceOfA; return 0; }

4 10