April 2007 - Boost - lists.preview.boost.org

[Boost-bugs] [ boost-Support Requests-1694020 ] Error while compiling ><
by SourceForge.net 04 Apr '07

04 Apr '07

Support Requests item #1694020, was opened at 2007-04-03 20:39 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=207586&aid=1694020&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Error while compiling >< Initial Comment: Hi guys, im sorry if this isnt quite were this belongs but i cant figure it out, since im new to Boost :( heres whats happening to me, I run a MUD and im starting to intergrate boost and luabind to it. and when i use make on my game, after installing boost, and luabind i get: In file included from /usr/local/include/boost-1_33_1/boost/mpl/int.hpp:17, from /usr/local/include/boost-1_33_1/boost/type_traits/detail/template_arity_spec.hpp:10, from /usr/local/include/boost-1_33_1/boost/type_traits/detail/type_trait_def.hpp:14, from /usr/local/include/boost-1_33_1/boost/type_traits/add_const.hpp:16, from /usr/local/include/boost-1_33_1/boost/type_traits.hpp:13, from /home/abyss/abyss/src/luabind/luabind/class.hpp:79, from /home/abyss/abyss/src/luabind/luabind/luabind.hpp:28, from lua.c:9: /usr/local/include/boost-1_33_1/boost/mpl/int_fwd.hpp:22: error: syntax error before numeric constant /usr/local/include/boost-1_33_1/boost/mpl/int_fwd.hpp:25: confused by earlier errors, bailing out make: *** [lua.o] Error 1 im using g++ to compile, and im not sure how to fix this problem :( my Makefile looks like: CC = ccache g++ PROF = -O -ggdb W_FLAGS = -Wall -Werror NOCRYPT = LDFLAGS = -L/opt/lampp/lib/ -L/usr/local/lib/ -I/usr/local/include/boost-1_33_$ -L/home/abyss/abyss/src/lua-5.1.1/src/ -I./lua-5.1.1/src/ \ -L/usr/lib/mysql/ -I/usr/include/mysql/ -I/usr/local/include/scripti$ -I/home/abyss/abyss/src/luabind/ C_FLAGS = $(LDFLAGS) $(PROF) $(W_FLAGS) $(NOCRYPT) L_FLAGS = $(PROF) LIBS = -L/home/abyss/abyss/src/lua-5.1.1/src/ -llua \ -L/usr/local/lib/ -lgd -lcrypt -lm \ -lmysqlclient -lnsl -laspell ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=207586&aid=1694020&group_… ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

[Review] Quantitative Units
by K. R. Walker 04 Apr '07

04 Apr '07

Hello, This review of Quantitative Units is by Shaun Bloom and K. R. Walker of Stellar Science Ltd. Co. We have been following this library for approximately two months as we are developing a new scientific application and have committed to using compile-time dimensional analysis where possible. > What is your evaluation of the design? We believe the design is good. We understand the basic concepts of systems, dimensions, units, and quantities and could manipulate these items. > What is your evaluation of the implementation? We have been happy with the implementation. Some of our template-metaprogrammers have been able to dig into the source to figure out what's going on without spending much time. > What is your evaluation of the documentation? It's been a while since we thoroughly looked over the documentation. We tend to prefer looking over the source code and examples. A brief look at the current documentation revealed no surprises. > What is your evaluation of the potential usefulness of the library? This library performs compile-time dimensional analysis along with helping to clarify and enforce API parameters and elements: function( const quantity< length > & ) is better than function( const double & ) At an early stage, we discovered a minor error in our software after starting to use this library. This library provides greater confidence in calculations making the pervasive use of this library highly desirable. Our application domain involves working with vectors in different frames-of-reference. We have recently discussed the possibility of defining our own unit systems for these frames to prevent vectors in one frame from being incorrectly used with vectors of another. e.g., an Earth-Centered-Inertial (ECI) vector should not be added to an Orbital-frame vector. > Did you try to use the library? With what compiler? > Did you have any problems? We have been using version 0.7.2 of this library with Visual Studio 2005 (sp1) and gcc 4.0.1 on Mac OS X. We have defined our own custom units and found their use to be identical to those provided by the library. We would like to see quantities defined using derived SI units printed using the derived units instead of the base units (W/m^2 instead of Kg/s^3). We had a problem with the 'pascal' symbol with Visual Studio 2005. It's since been resolved. The only other problems have involved mistakes in unit arithmetic when defining values. > How much effort did you put into your evaluation? A glance? > A quick reading? In-depth study? We looked closely at this library in it's early state and decided that even in alpha, it was worth integrating into our software. Our evaluation has been much more than a quick reading, but a bit less than an in-depth study. > Are you knowledgeable about the problem domain? Yes, we have experience writing scientific software applications and understand and can perform dimensional analysis. > Do you think the library should be accepted as a Boost library? > Be sure to say this explicitly so that your other > comments don't obscure your overall opinion. Yes. We would very much like to see this library become part of Boost. In the unfortunate event it were not accepted, we intend to continue to use the library. Thank you, -- Shaun Bloom <sb(a)stellarscience.com> K. R. Walker <krwalker(a)stellarscience.com> Stellar Science Ltd Co - Stellar Scientific Software Solutions

3 3

Re: [boost] Intrusive library review results: library accepted
by brass goowy 03 Apr '07

03 Apr '07

>Thank you to Ion Gaztañaga for all the hard work >involved in creating a Boost library, to Olaf Krzikalla, >who wrote the first versions of this piece of work, >and to all the participants in the review. > >The list of issues to be addressed follows. Feel free >to comment if you detect some error or omission from >my part. I don't recall any mention of marshalling/serialization support in the reviews and the documentation table of contents doesn't mention it. >* Naming >- Change Destroyer to a more suitable name (e.g. Sink or > Disposer), rename member functions accordingly. >- Rename current() as iterator_to(). >- Rename [s]list_algorithms as circular_[s]list_algorithms. >- Drop the 'i' prefix from the names of containers. I disagree with this one. I think std and intrusive containers will often be used together. This decision will lead to longer names in those cases. I would support dropping the prefix if the resulting name wasn't the same as in the std. Why not get rid of all the vowels and call them lst? Brian Wood Ebenezer Enterprises www.webEbenezer.net

2 1

[Report] 1 regressions on RC_1_34_0 (2007-04-01)
by Douglas Gregor 03 Apr '07

03 Apr '07

Boost Regression test failures Report time: 2007-04-01T02:22:36Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_34_0/developer/i… 1 failures in 1 libraries parameter (1) |parameter| python_test: gcc-cygwin-3.4.4

3 4

Boost packages?
by Mårten Rånge 03 Apr '07

03 Apr '07

This may have been discussed earlier and been proved impractical or impossible. I'm a big fan of the boost library; high-quality; great utility; great range. What's not to like? Unfortunately while I've been trying to introduce boost at the places I've been working on I find that the sheer scope of the boost library makes it discouraging. Often it's desirable to just demand a certain compiler and build enviroment (gcc or Visual Studio) then the developers run check out from subversion (for instance) and run the build script and they are on the way. boost isn't as easy as it could be IMO (due to its size and scope) to include into an existing project with many developers (many who might be unwilling to receive something that complicate the build enviroment). So let's take the project I'm working on now as an example. What I would like to do is just to download and use the smart pointers in boost to introduce the other developers to the possibility of reusing high-quality smart pointers instead of writing your own or worse not use smart pointers at all. In my world I would then like to download the smart pointer boost package (with dependencies?) which should be a fairly small download. Due to a more manageable size I would then foresee that it would easier for me to get it into the source control system and into the build environment. Also, it would be easier for me to convince the systems architect that boost is worth more than the hassle it introduces (right now I can't). Later when people see the benefit of boost and we want to do some text parsing I'd like to download the boost.spirit package and set it up. And so on. I would also think that packaging boost in different packages (a small base package and then perhaps each individual library as a package) would give benefits to the development of the new releases. Right now I have the feeling that getting a new release is rather daunting task. Which I guess comes from boost being a monolithic, large library that supports many different compilers and platforms. By packaging boost into several different packages one could perhaps have different release schedules for different packages? Different supported compilers on different packages ( ie VC6 I guess is a pain to get working with mpl but shared_ptr<> should work rather straightforward with that aging but still widely used compiler)? What do you think? I realize that this would be a rather daunting task in itself (impossible?) since I guess that the dependencies between the different libraries in boost might not be 100% documented and well understood. I do however think that there would be benefits in terms of spreading the popularity of boost and managing boost releases if it could be done. Regards, Mårten Rånge

8 15

[Boost-bugs] [ boost-Patches-1693879 ] [iostreams] workaround for the boost + stdcxx on MSVC 7.1
by SourceForge.net 03 Apr '07

03 Apr '07

Patches item #1693879, was opened at 2007-04-03 23:12 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=307586&aid=1693879&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Farid (farid_zaripov) Assigned to: Nobody/Anonymous (nobody) Summary: [iostreams] workaround for the boost + stdcxx on MSVC 7.1 Initial Comment: I have been working on the Apache C++ Standard Library project (STDCXX): http://incubator.apache.org/stdcxx/ I've trying to compile the boost library with stdcxx. The details can be found here: http://mail-archives.apache.org/mod_mbox/incubator-stdcxx-dev/200704.mbox/% 3c7BDB2168BEAEF14C98F1901FD2DE64386573EB(a)epmsa009.minsk.epam.com%3e Boost version: 1.33.1 STDCXX version: 4.2 I've got the error in boost\iostreams\device\mapped_file.hpp: D:\_Libs\boost_1_33_1\boost\iostreams\device\mapped_file.hpp(67) : error C2065: '__rw_openmode' : undeclared identifier D:\_Libs\boost_1_33_1\boost\iostreams\device\mapped_file.hpp(67) : error C2064: term does not evaluate to a function taking 0 arguments D:\_Libs\boost_1_33_1\boost\iostreams\device\mapped_file.hpp(72) : error C2064: term does not evaluate to a function taking 0 arguments CALL "C:\Program Files\Microsoft Visual Studio .NET 2003\VC7\bin\VCVARS32.BAT" >nul "C:\Program Files\Microsoft Visual Studio .NET 2003\VC7\bin\cl" /Zm800 -nologo /EHsc -c -D_RWSTDDEBUG /Z7 /Od /Ob0 /EHsc /GR /MTd /Op /wd4675 /Zc:forScope -I"bin\boost\libs\iostreams\build" -I"D:\_Libs\boost_1_33_1" -I"D:\_Projects\stdcxx_working\include" -I"D:\_Projects\stdcxx_working\include\ansi" -I"D:\_Projects\stdcxx_working\build\msvc-7.1\15s\include" -I"D:\_Libs\boost_1_33_1" -Fo"bin\boost\libs\iostreams\build\libboost_iostreams.lib\vc-7_1-stdcxx\debug\runtime-link-static\threading-multi\mapped_file.obj" -Tp"D:\_Libs\boost_1_33_1\libs\iostreams\build\..\src\mapped_file.cpp" This error issued because of the following bug of the MSVC 7.1: https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?Feedb… The proposed patch is attached. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=307586&aid=1693879&group_… ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

Re: [boost] [Review] Quantitative Units library review begins today, March 26
by Eric Lemings 03 Apr '07

03 Apr '07

What is your evaluation of the design? My biggest design concerns at the moment: 1. The scope of the library must neccessarily be limited. It should contain the dimensional analysis framework, all predefined base and derived physical dimensions, dimensionless constants, metric prefix wrappers, possibly the SI units of measurement, and that's about it. All other dimensions, units, and systems of measurement should be treated as "localized" extensions that are built on top of this library. 2. Exponents should be tightly coupled to their respective dimension or unit. Specifying them implicitly in a list as a pair is not tightly coupled. unit< meter, 1, gram, 2, second, -1 > Make the exponent a template parameter of the dimension or unit. This syntax is more natural and more intuitive. unit< meter<1>, gram<2>, second<-1> > 3. Generally speaking, the vast majority of units are converted to one another by simply multiplying the quanity by a factor. The current proposal potentially requires a separate template specicialization for each of these conversions. This type of conversion should be generalized, if at all possible, into a single generic operation. What is your evaluation of the implementation? My biggest concerns about the implementation: 4. Many Boost libraries follow the "fine-grained" header policy (e.g. MPL) while also providing convenience headers that include entire components or the entire library with a single include directive. Looking at the proposed library, I would like to see at least one convenience header file that includes the "core" library. Also a few of the headers are rather large and should be broken into smaller headers. 5. Don't see the need for ordinal class template. How is it different from the MPL integer constant wrappers? There are also other such questionable symbols (e.g. the whole operators.hpp header, make_dimension_list). 6. Code that should ideally be included as part of other Boost libraries (e.g. static_rational as part of Boost Math) should be defined within the ideal namespace to indicate the intended namespace partitioning even if the header currently resides in the proposed library. 7. The code sometimes confuses dimensions and units. Example: boost/units/systems/si/length.hpp:22:typedef unit<length_type,SI::system> length; Length is a dimension, not a unit. The type name 'length_type' however does have a sensible definition: ./boost/units/systems/physical_units.hpp:typedef fundamental_dimension<length_tag>::type length_type; Meter however is a unit and its dimension is length but to define 'meter' as a constant, even a constant whose type is 'length', looks really suspect of a design tradeoff: ./boost/units/systems/si/length.hpp:BOOST_UNITS_STATIC_CONSTANT(meter,le ngth); Not sure about the benifits and drawbacks of such a design. What is your evaluation of the documentation? Adequate for purposes of the proposal. It would need quite a bit more work to bring it up to the level of other Boost libraries. Compared to design and implementation of such a library, this is a relatively small issue. What is your evaluation of the potential usefulness of the library? Apart from some usage issues and prototypical implementation, it's headed in the right direction. Some scientists and engineers will certainly find it useful as is but many programmers will have issues with its current form I believe. Did you try to use the library? With what compiler? Did you have any problems? I tried to build the examples on MSVC 8.0 and Mac OS X but couldn't because there is only a BoostBuild v2 Jamfile and v2 is troublesome to say the least. A v1 Jamfile would have been extremely helpful. How much effort did you put into your evaluation? Few days of code and documentation review with light experimentation and testing of the examples. Are you knowledgeable about the problem domain? Enough to design and write a similar library and thus be aware of all the issues involved with such development. Do you think the library should be accepted as a Boost library? Not in its current form. While it does demonstrate the potential for becoming a Boost library, it needs more work. Symptomatically, the authors have stated that the library is still in development and I am hesitant to formally accept any library that is still in development. I would politely recommend that the authors gather, analyze, and integrate all review commments so far. I would also encourage rigorous testing by a larger, more objective audience. Eric.

3 5

[Boost-bugs] [ boost-Bugs-1693867 ] errors when build with Apache stdcxx
by SourceForge.net 03 Apr '07

03 Apr '07

Bugs item #1693867, was opened at 2007-04-03 22:55 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1693867&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: regex Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Farid (farid_zaripov) Assigned to: John Maddock (johnmaddock) Summary: errors when build with Apache stdcxx Initial Comment: I have been working on the Apache C++ Standard Library project (STDCXX): http://incubator.apache.org/stdcxx/ I've trying to compile the boost library with stdcxx. The details can be found here: http://mail-archives.apache.org/mod_mbox/incubator-stdcxx-dev/200704.mbox/% 3c7BDB2168BEAEF14C98F1901FD2DE64386573EB(a)epmsa009.minsk.epam.com%3e Boost version: 1.33.1 STDCXX version: 4.2 I've got the following errors in boost/regex/v4/regex_workaround.hpp and boost/regex/v4/fileiter.hpp: D:\_Libs\boost_1_33_1\boost/regex/v4/regex_workaround.hpp(145) : error C2653: 'stdext' : is not a class or namespace name D:\_Libs\boost_1_33_1\boost/regex/v4/regex_replace.hpp(44) : see reference to function template instantiation 'OutputIterator boost::re_detail::copy<BidirectionalIterator,OutputIterator>(InputIterator,InputIterator,OutputIterator)' being compiled with [ OutputIterator=boost::re_detail::string_out_iterator<std::string>, BidirectionalIterator=__rw::__rw_debug_iter<std::basic_string<char,std::char_traits<char>,std::allocator<char>>,const char *,char *>, InputIterator=__rw::__rw_debug_iter<std::basic_string<char,std::char_traits<char>,std::allocator<char>>,const char *,char *> ] D:\_Libs\boost_1_33_1\libs\regex\build\../src/cregex.cpp(446) : see reference to function template instantiation 'OutputIterator boost::regex_replace<boost::re_detail::string_out_iterator<S>,__rw::__rw_debug_iter<_Container,_Iterator,_MutableIterator>,boost::regex_traits<charT>,char>(OutputIterator,BidirectionalIterator,BidirectionalIterator,const boost::basic_regex<charT,traits> &,const charT *,boost::regex_constants::match_flag_type)' being compiled with [ OutputIterator=boost::re_detail::string_out_iterator<std::string>, S=std::string, _Container=std::basic_string<char,std::char_traits<char>,std::allocator<char>>, _Iterator=const char *, _MutableIterator=char *, charT=char, BidirectionalIterator=__rw::__rw_debug_iter<std::basic_string<char,std::char_traits<char>,std::allocator<char>>,const char *,char *>, traits=boost::regex_traits<char> ] D:\_Libs\boost_1_33_1\boost/regex/v4/regex_workaround.hpp(145) : error C3861: 'unchecked_copy': identifier not found D:\_Libs\boost_1_33_1\boost/regex/v4/regex_workaround.hpp(145) : error C2653: 'stdext' : is not a class or namespace name D:\_Libs\boost_1_33_1\boost/regex/v4/regex_replace.hpp(44) : see reference to function template instantiation 'OutputIterator boost::re_detail::copy<BidirectionalIterator,OutputIterator>(InputIterator,InputIterator,OutputIterator)' being compiled with [ OutputIterator=boost::re_detail::string_out_iterator<std::string>, BidirectionalIterator=const char *, InputIterator=const char * ] D:\_Libs\boost_1_33_1\libs\regex\build\../src/cregex.cpp(456) : see reference to function template instantiation 'OutputIterator boost::regex_replace<boost::re_detail::string_out_iterator<S>,const char*,boost::regex_traits<charT>,char>(OutputIterator,BidirectionalIterator,BidirectionalIterator,const boost::basic_regex<charT,traits> &,const charT *,boost::regex_constants::match_flag_type)' being compiled with [ OutputIterator=boost::re_detail::string_out_iterator<std::string>, S=std::string, charT=char, BidirectionalIterator=const char *, traits=boost::regex_traits<char> ] D:\_Libs\boost_1_33_1\boost/regex/v4/regex_workaround.hpp(145) : error C3861: 'unchecked_copy': identifier not found CALL "D:\Program Files\Microsoft Visual Studio 8\Common7\Tools\..\..\VC\bin\vcvars32.BAT" >nul "D:\Program Files\Microsoft Visual Studio 8\Common7\Tools\..\..\VC\bin\cl" /Zm800 -nologo /EHsc -c -DBOOST_REGEX_CONFIG_INFO=1 -D_RWSTDDEBUG /Z7 /Od /Ob0 /EHsc /GR /MTd /Zc:forScope /Zc:wchar_t -I"bin\boost\libs\regex\build" -I"D:\_Projects\stdcxx_working\include" -I"D:\_Projects\stdcxx_working\include\ansi" -I"D:\_Projects\stdcxx_working\build\msvc-8.0\15s\include" -I"D:\_Libs\boost_1_33_1" -Fo"bin\boost\libs\regex\build\libboost_regex.lib\vc-8_0-stdcxx\debug\runtime-link-static\threading-multi\cregex.obj" -Tp"D:\_Libs\boost_1_33_1\libs\regex\build\../src/cregex.cpp" D:\_Libs\boost_1_33_1\boost/regex/v4/fileiter.hpp(331) : error C2039: 'ptrdiff_t' : is not a member of 'std' D:\_Libs\boost_1_33_1\boost/regex/v4/fileiter.hpp(378) : error C2039: 'ptrdiff_t' : is not a member of 'std' CALL "D:\Program Files\Microsoft Visual Studio 8\Common7\Tools\..\..\VC\bin\vcvars32.BAT" >nul "D:\Program Files\Microsoft Visual Studio 8\Common7\Tools\..\..\VC\bin\cl" /Zm800 -nologo /EHsc -c -DBOOST_REGEX_CONFIG_INFO=1 -D_RWSTDDEBUG /Z7 /Od /Ob0 /EHsc /GR /MTd /Zc:forScope /Zc:wchar_t -I"bin\boost\libs\regex\build" -I"D:\_Projects\stdcxx_working\include" -I"D:\_Projects\stdcxx_working\include\ansi" -I"D:\_Projects\stdcxx_working\build\msvc-8.0\15s\include" -I"D:\_Libs\boost_1_33_1" -Fo"bin\boost\libs\regex\build\libboost_regex.lib\vc-8_0-stdcxx\debug\runtime-link-static\threading-multi\fileiter.obj" -Tp"D:\_Libs\boost_1_33_1\libs\regex\build\../src/fileiter.cpp" I propose to #include <cstddef> in fileiter.hpp to define the std::ptrdiff_t. And also I propose to change the line 131 in regex_workaround.hpp from #if BOOST_WORKAROUND(BOOST_MSVC,>=1400) to the #if BOOST_WORKAROUND(BOOST_MSVC,>=1400) && defined(BOOST_DINKUMWARE_STDLIB) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1693867&group_… ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

[Boost-bugs] [ boost-Bugs-1693865 ] undeclared memcpy() in flex_string.hpp
by SourceForge.net 03 Apr '07

03 Apr '07

Bugs item #1693865, was opened at 2007-04-03 22:48 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1693865&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: wave Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Farid (farid_zaripov) Assigned to: Hartmut Kaiser (hkaiser) Summary: undeclared memcpy() in flex_string.hpp Initial Comment: I have been working on the Apache C++ Standard Library project (STDCXX): http://incubator.apache.org/stdcxx/ I've trying to compile the boost library with stdcxx. The details can be found here: http://mail-archives.apache.org/mod_mbox/incubator-stdcxx-dev/200704.mbox/% 3c7BDB2168BEAEF14C98F1901FD2DE64386573EB(a)epmsa009.minsk.epam.com%3e Boost version: 1.33.1 STDCXX version: 4.2 I've got the error in boost/wave/util/flex_string.hpp: D:\_Libs\boost_1_33_1\boost/wave/util/flex_string.hpp(126) : error C3861: 'memcpy': identifier not found D:\_Libs\boost_1_33_1\boost/wave/util/flex_string.hpp(654) : see reference to function template instantiation 'Pod *boost::wave::util::flex_string_details::pod_copy<char>(const Pod *,const Pod *,Pod *)' being compiled with [ Pod=char ] D:\_Libs\boost_1_33_1\boost/wave/util/flex_string.hpp(643) : while compiling class template member function 'void boost::wave::util::AllocatorStringStorage<E>::reserve(unsigned int)' with [ E=char ] D:\_Libs\boost_1_33_1\boost/wave/util/flex_string.hpp(1154) : see reference to class template instantiation 'boost::wave::util::AllocatorStringStorage<E>' being compiled with [ E=char ] CALL "D:\Program Files\Microsoft Visual Studio 8\Common7\Tools\..\..\VC\bin\vcvars32.BAT" >nul "D:\Program Files\Microsoft Visual Studio 8\Common7\Tools\..\..\VC\bin\cl" /Zm800 -nologo /EHsc -c -D_RWSTDDEBUG /Z7 /Od /Ob0 /EHsc /GR /MTd /Zc:forScope /Zc:wchar_t -I"bin\boost\libs\wave\build" -I"D:\_Libs\boost_1_33_1" -I"D:\_Projects\stdcxx_working\include" -I"D:\_Projects\stdcxx_working\include\ansi" -I"D:\_Projects\stdcxx_working\build\msvc-8.0\15s\include" -I"D:\_Libs\boost_1_33_1" -Fo"bin\boost\libs\wave\build\libboost_wave.lib\vc-8_0-stdcxx\debug\runtime-link-static\threading-multi\instantiate_cpp_exprgrammar.obj" -Tp"D:\_Libs\boost_1_33_1\libs\wave\build\../src/instantiate_cpp_exprgrammar.cpp" I propose to #include <string.h> in flex_string.hpp file to declare memcpy(). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1693865&group_… ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

[Boost-bugs] [ boost-Bugs-1693862 ] errors when build with Apache stdcxx
by SourceForge.net 03 Apr '07

03 Apr '07

Bugs item #1693862, was opened at 2007-04-03 22:44 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1693862&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: threads Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Farid (farid_zaripov) Assigned to: Mike Glassford (glassfordm) Summary: errors when build with Apache stdcxx Initial Comment: I have been working on the Apache C++ Standard Library project (STDCXX): http://incubator.apache.org/stdcxx/ I've trying to compile the boost library with stdcxx. The details can be found here: http://mail-archives.apache.org/mod_mbox/incubator-stdcxx-dev/200704.mbox/% 3c7BDB2168BEAEF14C98F1901FD2DE64386573EB(a)epmsa009.minsk.epam.com%3e Boost version: 1.33.1 STDCXX version: 4.2 I've got the folowing errors in libs/thread/src/once.cpp and boost/thread/recursive_mutex.hpp: D:\_Libs\boost_1_33_1\libs\thread\build\..\src\once.cpp(159) : error C2039: 'hex' : is not a member of 'std' D:\_Libs\boost_1_33_1\libs\thread\build\..\src\once.cpp(159) : error C2065: 'hex' : undeclared identifier CALL "D:\Program Files\Microsoft Visual Studio 8\Common7\Tools\..\..\VC\bin\vcvars32.BAT" >nul "D:\Program Files\Microsoft Visual Studio 8\Common7\Tools\..\..\VC\bin\cl" /Zm800 -nologo /EHsc -c -DBOOST_THREAD_LIB_NAME=boost_thread -DBOOST_THREAD_BUILD_LIB=1 -D_RWSTDDEBUG /Z7 /Od /Ob0 /EHsc /GR /MTd /Zc:forScope /Zc:wchar_t -I"bin\boost\libs\thread\build" -I"D:\_Projects\stdcxx_working\include" -I"D:\_Projects\stdcxx_working\include\ansi" -I"D:\_Projects\stdcxx_working\build\msvc-8.0\15s\include" -I"D:\_Libs\boost_1_33_1" -Fo"bin\boost\libs\thread\build\libboost_thread.lib\vc-8_0-stdcxx\debug\runtime-link-static\threading-multi\once.obj" -Tp"D:\_Libs\boost_1_33_1\libs\thread\build\..\src\once.cpp" D:\_Libs\boost_1_33_1\boost/thread/recursive_mutex.hpp(45) : error C2039: 'size_t' : is not a member of 'std' D:\_Libs\boost_1_33_1\boost/thread/recursive_mutex.hpp(92) : error C2039: 'size_t' : is not a member of 'std' D:\_Libs\boost_1_33_1\boost/thread/recursive_mutex.hpp(142) : error C2039: 'size_t' : is not a member of 'std' CALL "D:\Program Files\Microsoft Visual Studio 8\Common7\Tools\..\..\VC\bin\vcvars32.BAT" >nul "D:\Program Files\Microsoft Visual Studio 8\Common7\Tools\..\..\VC\bin\cl" /Zm800 -nologo /EHsc -c -DBOOST_THREAD_LIB_NAME=boost_thread -DBOOST_THREAD_BUILD_LIB=1 -D_RWSTDDEBUG /Z7 /Od /Ob0 /EHsc /GR /MTd /Zc:forScope /Zc:wchar_t -I"bin\boost\libs\thread\build" -I"D:\_Projects\stdcxx_working\include" -I"D:\_Projects\stdcxx_working\include\ansi" -I"D:\_Projects\stdcxx_working\build\msvc-8.0\15s\include" -I"D:\_Libs\boost_1_33_1" -Fo"bin\boost\libs\thread\build\libboost_thread.lib\vc-8_0-stdcxx\debug\runtime-link-static\threading-multi\recursive_mutex.obj" -Tp"D:\_Libs\boost_1_33_1\libs\thread\build\..\src\recursive_mutex.cpp" I propose to #include <ios> in once.cpp to define std::hex() and #include <cstddef> in recursive_mutex.hpp to define std::size_t. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1693862&group_… ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0