- Boost - lists.boost.org

Re: [boost] [asio].[hp-ux].[1_33_1] Build related issue
by Gaurav.Jain＠iflexsolutions.com 08 Feb '07

08 Feb '07

Christopher Kohlhoff <chris <at> kohlhoff.com> writes: > > If possible, can you retry with the boost.asio 0.3.8 release candidate: > > http://sourceforge.net/project/showfiles.php?group_id=122478 > or against the CVS HEAD version of boost. It won't work for HP-UX yet, > but I'd like to make the changes against the latest source code. If the > changes are trivial (meaning changes to #ifdefs only) then I'd be happy > to add support for HP-UX in 0.3.8 (but only with _XOPEN_SOURCE_EXTENDED > undefined). > > Cheers, > Chris Hi Chris, As suggested, I have tried to build daytime_client.cpp - asio 0.3.8 with boost 1.33.1 on Solaris 10. As per Solaris 10 man pages msghdr structure is The recvmsg() function call uses a msghdr structure to minimize the number of directly supplied parameters. This structure is defined in <sys/socket.h> and includes the fol- lowing members: caddr_t msg_name; /* optional address */ int msg_namelen; /* size of address */ struct iovec *msg_iov; /* scatter/gather array */ int msg_iovlen; /* # elements in msg_iov */ caddr_t msg_accrights; /* access rights sent/received */ int msg_accrightslen; Based on this information I have replaced all the occurrences of msg.msg_control = 0; msg.msg_controllen = 0; msg.msg_flags = 0; With msg.msg_accrights = 0; msg.msg_accrightslen = 0; in asio/detail/socket_ops.hpp. Number of errors have come down to 3 on Solaris 10. boost/1_33_1/64/boost/array.hpp", line 74: Error: Too few arguments for template std::reverse_iterator<boost::T*>. "/boost/1_33_1/64/boost/array.hpp", line 166: Where: While specializing "boost::array<boost::T, boost::N>". "/boost/1_33_1/64/boost/array.hpp", line 166: Where: Specialized in non-template code. "/boost/1_33_1/64/boost/array.hpp", line 75: Error: Too few arguments for template std::reverse_iterator<const boost::T*>. "/boost/1_33_1/64/boost/array.hpp", line 166: Where: While specializing "boost::array<boost::T, boost::N>". "/boost/1_33_1/64/boost/array.hpp", line 166: Where: Specialized in non-template code. "daytime_client.cpp", line 24: Error: The operation "std::ostream<<boost::asio::error" is illegal. 3 Error(s) detected. I am not sure if Asio 0.3.8 will work with Boost 1.33.1. Regards, Gaurav Jain

3 2

Re: [boost] [asio].[hp-ux].[1_33_1] Build related issue
by Gaurav.Jain＠iflexsolutions.com 08 Feb '07

08 Feb '07

<Oliver.Kowalke <at> qimonda.com> writes: > > >This > > structure is defined in <sys/socket.h> and includes the fol- > > lowing members: > > caddr_t msg_name; /* optional address */ > > int msg_namelen; /* size of address */ > > struct iovec *msg_iov; /* scatter/gather array */ > > int msg_iovlen; /* # elements in msg_iov */ > > caddr_t msg_accrights; /* access rights sent/received */ > > int msg_accrightslen; > > This is the same behaviour on HP/UX. Without _XOPEN_SOURCE_EXTENDED (on > HP/UX) you get the old HP/UX specific socket api (-> different structes > like struct msghdr). The same seams to apply to Solaris 10. Maybe you > can find an hint in the documention for a special compiler flag in order > to get X/Open compliant functions and structures as Christopher uses in > its code. It would be cumbersome to manage each special UNIX flaviour > socket api in you code. Using an standardized api would be better for > future investments and because the UNIX supplier can deprecate its old > socket api too in future. > > Oliver msghdr structure used by asio would require "_XOPEN_SOURCE_EXTENDED" or "_XOPEN_SOURCE=500/600" to be defined since it is compliant with X/Open Networking Services Library Functions and also would require to be linked against -libxnet at least on Solaris. No particular compiler flags are mentioned in man pages. However, standards man page suggests that "-D_XOPEN_SOURCE=500" or "-D_XOPEN_SOURCE=600" be passed to compiler. It would be helpful if the asio library takes care of this in the header file. Regards, Gaurav Jain

2 1

[asio].[hp-ux].[1_33_1] Build related issue
by Gaurav.Jain＠iflexsolutions.com 08 Feb '07

08 Feb '07

Hi, I have tried using boost 1_33_1 on HP UX machine, while compiling the program I am getting some errors. Can anybody help me out? The detail of the compilation is as follows: Boost Version: 1_33_1 bjam install -sTOOLS=acc --prefix="/home/pthakre/boost" --builddir="/tmp" \ "-sBUILD=release <runtime-link>dynamic/static <threading>multi <cxxflags>+DD64 <cflags>+DD64 <linkflags>+DD64" --without-python Jamfile Compiler Details: aCC: HP C/aC++ B3910B A.06.13 [Nov 27 2006] OS Details: HP-UX B.11.23 ia64 While compiling "daytime_server.cpp" with -D_HPUX_SOURCE -D_XOPEN_SOURCE_EXTENDED, I am getting the following error: "boost-1_33_1/include/boost/asio/detail/socket_types.hpp", line 136: error #2020: identifier "ip_mreq" is undefined typedef ip_mreq in4_mreq_type; Also, from /usr/include/netinet/in.h #ifndef _XOPEN_SOURCE_EXTENDED /* * Argument structure for IP_ADD_MEMBERSHIP and IP_DROP_MEMBERSHIP. */ struct ip_mreq { struct in_addr imr_multiaddr; /* IP multicast address of group */ struct in_addr imr_interface; /* local IP address of interface */ }; #endif /* ! _XOPEN_SOURCE_EXTENDED */ Compiling "daytime_server.cpp" without -D_HPUX_SOURCE -D_XOPEN_SOURCE_EXTENDED, I m getting 22 errors. I have done the following changes: Line 575 ./asio/detail/socket_ops.hpp: #if defined(BOOST_WINDOWS) || defined(__CYGWIN__) || defined(__hpux) Line 611 ./asio/detail/socket_ops.hpp: #if defined(BOOST_WINDOWS) || defined(__CYGWIN__) || defined(__hpux) Line 274 ./asio/error.hpp: #if defined(__sun) || defined(__QNX__) || defined(__hpux) Line 109 ./asio/system_exception.hpp: #elif defined(__sun) || defined(__QNX__) || defined(__hpux) Regards, Gaurav

3 3

Re: [boost] [asio].[hp-ux].[1_33_1] Build related issue
by Gaurav.Jain＠iflexsolutions.com 08 Feb '07

08 Feb '07

Christopher Kohlhoff <chris <at> kohlhoff.com> writes: > > If possible, can you retry with the boost.asio 0.3.8 release candidate: > > http://sourceforge.net/project/showfiles.php?group_id=122478 > or against the CVS HEAD version of boost. It won't work for HP-UX yet, > but I'd like to make the changes against the latest source code. If the > changes are trivial (meaning changes to #ifdefs only) then I'd be happy > to add support for HP-UX in 0.3.8 (but only with _XOPEN_SOURCE_EXTENDED > undefined). > > Cheers, > Chris Hi Chris, I am yet to try boost.asio 0.3.8. But I have tried to build the daytime_client.cpp on AIX 5.3 with xlC 8.00 and Solaris 10 with Studio 11 without any success. Following errors relating to msghdr crop up often on Solaris: /boost/1_33_1/64/boost/asio/detail/socket_ops.hpp", line 170: Err or: msg_control is not a member of msghdr. "/boost/1_33_1/64/boost/asio/detail/socket_ops.hpp", line 171: Err or: msg_controllen is not a member of msghdr. "/boost/1_33_1/64/boost/asio/detail/socket_ops.hpp", line 172: Err or: msg_flags is not a member of msghdr. "/boost/1_33_1/64/boost/asio/detail/socket_ops.hpp", line 197: Err or: msg_control is not a member of msghdr. "/boost/1_33_1/64/boost/asio/detail/socket_ops.hpp", line 198: Err or: msg_controllen is not a member of msghdr. " /boost/1_33_1/64/boost/asio/detail/socket_ops.hpp", line 199: Err or: msg_flags is not a member of msghdr. Errors on AIX 5.3: "/home/gauravj/1_33_1/include/boost/asio/error.hpp", line 292.21: 1540-1260 (S) An obj ect of type "std::basic_string<char,std::char_traits<char>,std::allocator<char> >" can not be constructed from an rvalue of type "int". "/home/gauravj/1_33_1/include/boost/asio/detail/socket_ops.hpp", line 600.61: 1540-025 6 (S) A parameter of type "hostent_data *" cannot be initialized with an expression of type "char *". "/home/gauravj/1_33_1/include/boost/asio/detail/socket_ops.hpp", line 600.61: 1540-120 5 (I) The error occurred while converting to parameter 5 of "gethostbyaddr_r(const cha r *, size_t, int, hostent *, hostent_data *)". "/home/gauravj/1_33_1/include/boost/asio/detail/socket_ops.hpp", line 655.49: 1540-025 6 (S) A parameter of type "hostent_data *" cannot be initialized with an expression of type "char *". "/home/gauravj/1_33_1/include/boost/asio/detail/socket_ops.hpp", line 655.49: 1540-120 5 (I) The error occurred while converting to parameter 3 of "gethostbyname_r(const cha r *, hostent *, hostent_data *)". Regards, Gaurav Jain

1 0

[Boost-bugs] [ boost-Patches-1652860 ] Unused variable in format date parser
by SourceForge.net 08 Feb '07

08 Feb '07

Patches item #1652860, was opened at 2007-02-05 17:52 Message generated for change (Comment added) made by alexis_wilke You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=307586&aid=1652860&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: Alexis Wilke (alexis_wilke) Assigned to: Jeff Garland (az_sw_dude) Summary: Unused variable in format date parser Initial Comment: May sound silly, but an unused variable could represent a bug. Thus, Coverity found it and signaled it. It would be nice to have it removed to avoid that error in the future. The variable seems to be a left over from other parsing functions which do make use of it. ---------------------------------------------------------------------- >Comment By: Alexis Wilke (alexis_wilke) Date: 2007-02-07 21:53 Message: Logged In: YES user_id=554061 Originator: YES Hi guys, I also noticed that by removing the code I removed, the current_char variable is actually unused. I uploaded a newer patch with all the fixes. Alexis Wilke File Added: format_date_parser.patch ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=307586&aid=1652860&group_… ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

asio failures on Borland compiler
by AlisdairM 08 Feb '07

08 Feb '07

I am only set up for testing with Borland compilers at the moment, and the test results aren't visible at the moment, but ... I am looking into two test cases, buffer.cpp and buffer_select.cpp. Both fail for the same reason - an attempt to instantiate array< const char, 1024 >. That looks like a genuine error to me, array does not support const PODs, instead you must declare a const array. However, I have not tracked down the source of this instantiation yet, so it might be a bad type deduction by the compiler as well. Any hints on where to look more closely appreciated. -- AlisdairM

2 5

[fusion] doc error
by Steven Watanabe 07 Feb '07

07 Feb '07

AMDG The documentation of find says template< typename Sequence, typename T > /unspecified/ find(Sequence const& seq); This should be template< typename T, typename Sequence > /unspecified/ find(Sequence const& seq); In Christ, Steven Watanabe

2 1

[fusion] Polymorphic Function Object doc error
by Steven Watanabe 07 Feb '07

07 Feb '07

AMDG The description of Polymorphic Function Object says that it is a refinement of MPL Metafunction Class. In Christ, Steven Watanabe

2 1

[Review] accumulators
by Bernhard Mäder 07 Feb '07

07 Feb '07

Hello all Hope I'm not too late with a small review of the accumulators library: • What is your evaluation of the design? I very much like the user interface of the library, it's pretty clean and concise; writing something like accumulator_set<double, stats<tag::median(with_p_square_quantile) > > acc; is as expressive as it gets. This is just cool. On the other side of the library, when defining new features, things are a bit more complicated. I experienced some ugly compile-time troubles when trying to implement a group of features that depended on each other. Writing that code took considerable more time than writing the same functionality without the framework. I'm quite willing to take this effort, though, for all the benefits of the accumulators framework. Then, I can't really get warm with the automatic feature resolution. On the one hand, it's a great feature for reducing accumulator set definition code. On the other hand, the programmer has to know which features get pulled in anyway (you'll need to include those header files, right?). Furthermore, it seems a bit dangerous to have such automatisms in a field, where you should always know what you're doing anyway (which is again exemplified by the discussion of the various implementations of the mean and variance features on this list). Then there is BOOST_ACCUMULATORS_MAX_FEATURES, which has to take into account even those features that are pulled in automatically. This is a bit counter intuitive and caused some troubles on my side. I'd wish that accumulator_set provided an operator<< to print it to console or files. We're often using accumulator sets from an interactive python console, which would further benefit from a pretty-printed output. Equally, they should be made serializable. The formerly discussed combine() feature could also come in very handy for some of our applications. Overall, I think the library's complexity is as high as I'm willing to go for every day's business. It's really nothing for C++ beginners to start with, as it requires some intermediate level "boost" thinking. • What is your evaluation of the implementation? The framework code is inspiring, as most of Eric's work. The stats are very well separated and pretty easy to read. • What is your evaluation of the documentation? A bit short at times. Some tools lack detailed description (depends_on, feature_of etc.), the external<> mechanics are not clearly described. The overall structure of the user's guide is very good, though. • What is your evaluation of the potential usefulness of the library? Well, we're already using it in production code, so I guess it's very real. There are many other application fields where I could imagine using it (signal processing, imaging, embedded systems with limited memory etc.) • Did you try to use the library? With what compiler? Did you have any problems? We're using the library on debian sarge with GCC3.4. Apart for some long and obscure compiler outputs on errors (and that's hardly boost accumulator's fault), all went fine. • How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? I've been using the library as end-user for quite some time now. I did not study all of the source code nor all of the design decisions, but come across many aspects of the library during normal usage. • Are you knowledgeable about the problem domain? I do know our requirements for statistics on current project, and see where they cause problems, But I'm not really a statistics expert. • Do you think the library should be accepted as a Boost library? Of course, it's a great enhancement to boost. Bernhard

2 1

[promotion traits]
by John Fletcher 07 Feb '07

07 Feb '07

What is the status of the promotion traits library as I would like to evaluate it? I have found it as conditionally accepted (April 12 2006) but I cannot find it in the CVS regressions. John Fletcher

2 3