Boost Serialization on Sun Solaris with rwtools7_std
Hi All, My project is using rwtools7_std library on Sun Solaris. However, Boos Serialization needs stlport4 and these two libraries cannot work together. Does anyone use Boost on Sun Solaris with rwtools7_std before? Can I change Boost library to use rwtools7_std instead of stlport4? The reason is my project has to use rwtools7_std. Thank you. Dennis
Duc Tran wrote:
Hi All,
My project is using rwtools7_std library on Sun Solaris.
However, Boos Serialization needs stlport4 and these two libraries cannot work together.
Does anyone use Boost on Sun Solaris with rwtools7_std before?
Can I change Boost library to use rwtools7_std instead of stlport4? The reason is my project has to use rwtools7_std.
In the past I tested with stlport - though not with this compiler - and had all the tests pass. This was several years ago so it won't help you much now. But it does indicate that it should be possible to make this work.
Thank you. Dennis
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Thanks Robert. It works with stlport. But my project currently uses rogue wave. I am looking a way to use Boost Serialiazation without changing my current codes (it is a tedious task). Dennis /DucTran On Tue, Oct 15, 2013 at 12:01 AM, Robert Ramey <ramey@rrsd.com> wrote:
Duc Tran wrote:
Hi All,
My project is using rwtools7_std library on Sun Solaris.
However, Boos Serialization needs stlport4 and these two libraries cannot work together.
Does anyone use Boost on Sun Solaris with rwtools7_std before?
Can I change Boost library to use rwtools7_std instead of stlport4? The reason is my project has to use rwtools7_std.
In the past I tested with stlport - though not with this compiler - and had all the tests pass. This was several years ago so it won't help you much now. But it does indicate that it should be possible to make this work.
Thank you. Dennis
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Duc Tran wrote:
Thanks Robert.
It works with stlport.
But my project currently uses rogue wave. I am looking a way to use Boost Serialiazation without changing my current codes (it is a tedious task).
Have you tried building/testing the serialization library with rwtools7_std? It's easy to try. Turns out that the serialization library originally worked with MSVC 6.0 and Borland 5.5 so it's possible it could work with your platform. The only thing that I know is broken is binary_?archive which lost backward compatibility with the introduction of a speed up for arrays. Robert Ramey
Dennis
/DucTran
On Tue, Oct 15, 2013 at 12:01 AM, Robert Ramey <ramey@rrsd.com> wrote:
Duc Tran wrote:
Hi All,
My project is using rwtools7_std library on Sun Solaris.
However, Boos Serialization needs stlport4 and these two libraries cannot work together.
Does anyone use Boost on Sun Solaris with rwtools7_std before?
Can I change Boost library to use rwtools7_std instead of stlport4? The reason is my project has to use rwtools7_std.
In the past I tested with stlport - though not with this compiler - and had all the tests pass. This was several years ago so it won't help you much now. But it does indicate that it should be possible to make this work.
Thank you. Dennis
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
I have tried to compiling the serialization library with rwtools7_std but failed; but able to compile with stlport4. Here is complie logs with rwtools7_std. $ ./bjam --toolset=sun --j4 --build-dir=./build --with-serialization stage
common.mkdir stage common.mkdir stage/lib common.mkdir build common.mkdir build/boost common.mkdir build/boost/bin.v2 common.mkdir build/boost/bin.v2/libs common.mkdir build/boost/bin.v2/libs/serialization common.mkdir build/boost/bin.v2/libs/serialization/build common.mkdir build/boost/bin.v2/libs/serialization/build/sun common.mkdir build/boost/bin.v2/libs/serialization/build/sun/release common.mkdir build/boost/bin.v2/libs/serialization/build/sun/release/stdlib-sun-stlport common.mkdir build/boost/bin.v2/libs/serialization/build/sun/release/stdlib-sun-stlport/threading-multi sun.compile.c++ build/boost/bin.v2/libs/serialization/build/sun/release/stdlib-sun-stlport/threading-multi/basic_archive.o sun.compile.c++ build/boost/bin.v2/libs/serialization/build/sun/release/stdlib-sun-stlport/threading-multi/basic_iarchive.o sun.compile.c++ build/boost/bin.v2/libs/serialization/build/sun/release/stdlib-sun-stlport/threading-multi/basic_iserializer.o sun.compile.c++ build/boost/bin.v2/libs/serialization/build/sun/release/stdlib-sun-stlport/threading-multi/basic_oarchive.o sun.compile.c++ build/boost/bin.v2/libs/serialization/build/sun/release/stdlib-sun-stlport/threading-multi/basic_oserializer.o sun.compile.c++ build/boost/bin.v2/libs/serialization/build/sun/release/stdlib-sun-stlport/threading-multi/basic_pointer_iserializer.o sun.compile.c++ build/boost/bin.v2/libs/serialization/build/sun/release/stdlib-sun-stlport/threading-multi/basic_pointer_oserializer.o sun.compile.c++ build/boost/bin.v2/libs/serialization/build/sun/release/stdlib-sun-stlport/threading-multi/basic_serializer_map.o sun.compile.c++ build/boost/bin.v2/libs/serialization/build/sun/release/stdlib-sun-stlport/threading-multi/basic_text_iprimitive.o "./boost/iterator/transform_iterator.hpp", line 49: Error: iterator_traits is not a member of std. "./boost/iterator/transform_iterator.hpp", line 76: Where: While specializing "boost::detail::transform_iterator_base<boost::archive::iterators::detail::to_6_bit<char>, boost::archive::iterators::remove_whitespace<boost::archive::iterators::istream_iterator<char>>, boost::use_default, boost::use_default>". "./boost/iterator/transform_iterator.hpp", line 76: Where: Specialized in boost::transform_iterator<boost::archive::iterators::detail::to_6_bit<char>, boost::archive::iterators::remove_whitespace<boost::archive::iterators::istream_iterator<char>>, boost::use_default, boost::use_default>. "./boost/archive/iterators/binary_from_base64.hpp", line 91: Where: Specialized in boost::archive::iterators::binary_from_base64<boost::archive::iterators::remove_whitespace<boost::archive::iterators::istream_iterator<char>>, char>. "./boost/detail/iterator.hpp", line 103: Where: Specialized in boost::detail::iterator_traits<boost::archive::iterators::binary_from_base64<boost::archive::iterators::remove_whitespace<boost::archive::iterators::istream_iterator<char>>, char>>. "./boost/iterator/iterator_traits.hpp", line 49: Where: Specialized in boost::iterator_difference<boost::archive::iterators::binary_from_base64<boost::archive::iterators::remove_whitespace<boost::archive::iterators::istream_iterator<char>>, char>>. "./boost/mpl/eval_if.hpp", line 41: Where: Specialized in boost::mpl::eval_if<boost::is_same<boost::use_default, boost::use_default>, boost::iterator_difference<boost::archive::iterators::binary_from_base64<boost::archive::iterators::remove_whitespace<boost::archive::iterators::istream_iterator<char>>, char>>, boost::mpl::identity<boost::use_default>>. "./boost/iterator/iterator_adaptor.hpp", line 166: Where: Specialized in boost::detail::ia_dflt_help<boost::use_default, boost::iterator_difference<boost::archive::iterators::binary_from_base64<boost::archive::iterators::remove_whitespace<boost::archive::iterators::istream_iterator<char>>, char>>>. "./boost/iterator/iterator_adaptor.hpp", line 216: Where: Specialized in boost::detail::iterator_adaptor_base<boost::archive::iterators::transform_width<boost::archive::iterators::binary_from_base64<boost::archive::iterators::remove_whitespace<boost::archive::iterators::istream_iterator<char>>, char>, 8, 6, char>, boost::archive::iterators::binary_from_base64<boost::archive::iterators::remove_whitespace<boost::archive::iterators::istream_iterator<char>>, char>, char, boost::single_pass_traversal_tag, char, boost::use_default>. "./boost/iterator/iterator_adaptor.hpp", line 265: Where: Specialized in boost::iterator_adaptor<boost::archive::iterators::transform_width<boost::archive::iterators::binary_from_base64<boost::archive::iterators::remove_whitespace<boost::archive::iterators::istream_iterator<char>>, char>, 8, 6, char>, boost::archive::iterators::binary_from_base64<boost::archive::iterators::remove_whitespace<boost::archive::iterators::istream_iterator<char>>, char>, char, boost::single_pass_traversal_tag, char, boost::use_default>. "./boost/archive/iterators/transform_width.hpp", line 54: Where: Specialized in boost::archive::iterators::transform_width<boost::archive::iterators::binary_from_base64<boost::archive::iterators::remove_whitespace<boost::archive::iterators::istream_iterator<char>>, char>, 8, 6, char>. "./boost/archive/impl/basic_text_iprimitive.ipp", line 90: Where: Instantiated from boost::archive::basic_text_iprimitive<std::istream>::load_binary(void*, unsigned). "libs/serialization/src/basic_text_iprimitive.cpp", line 25: Where: Instantiated from non-template code. "./boost/iterator/transform_iterator.hpp", line 49: Error: ")" expected instead of "<". "./boost/iterator/transform_iterator.hpp", line 76: Where: While specializing "boost::detail::transform_iterator_base<boost::archive::iterators::detail::to_6_bit<char>, boost::archive::iterators::remove_whitespace<boost::archive::iterators::istream_iterator<char>>, boost::use_default, boost::use_default>". "./boost/iterator/transform_iterator.hpp", line 76: Where: Specialized in boost::transform_iterator<boost::archive::iterators::detail::to_6_bit<char>, boost::archive::iterators::remove_whitespace<boost::archive::iterators::istream_iterator<char>>, boost::use_default, boost::use_default>. "./boost/archive/iterators/binary_from_base64.hpp", line 91: Where: Specialized in boost::archive::iterators::binary_from_base64<boost::archive::iterators::remove_whitespace<boost::archive::iterators::istream_iterator<char>>, char>. "./boost/detail/iterator.hpp", line 103: Where: Specialized in boost::detail::iterator_traits<boost::archive::iterators::binary_from_base64<boost::archive::iterators::remove_whitespace<boost::archive::iterators::istream_iterator<char>>, char>>. "./boost/iterator/iterator_traits.hpp", line 49: Where: Specialized in boost::iterator_difference<boost::archive::iterators::binary_from_base64<boost::archive::iterators::remove_whitespace<boost::archive::iterators::istream_iterator<char>>, char>>. "./boost/mpl/eval_if.hpp", line 41: Where: Specialized in boost::mpl::eval_if<boost::is_same<boost::use_default, boost::use_default>, boost::iterator_difference<boost::archive::iterators::binary_from_base64<boost::archive::iterators::remove_whitespace<boost::archive::iterators::istream_iterator<char>>, char>>, boost::mpl::identity<boost::use_default>>. "./boost/iterator/iterator_adaptor.hpp", line 166: Where: Specialized in boost::detail::ia_dflt_help<boost::use_default, boost::iterator_difference<boost::archive::iterators::binary_from_base64<boost::archive::iterators::remove_whitespace<boost::archive::iterators::istream_iterator<char>>, char>>>.
.....
"CC" -library=rwtools7_std -xO4 -mt -erroff=%none -KPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_SERIALIZATION_DYN_LINK=1 -DNDEBUG -I"." -c -o "build/boost/bin.v2/libs/serialization/build/sun/release/stdlib-sun-stlport/threading-multi/basic_text_oprimitive.o" "libs/serialization/src/basic_text_oprimitive.cpp" ...failed sun.compile.c++ build/boost/bin.v2/libs/serialization/build/sun/release/stdlib-sun-stlport/threading-multi/basic_text_oprimitive.o...
/DucTran On Wed, Oct 16, 2013 at 1:13 PM, Robert Ramey <ramey@rrsd.com> wrote:
Duc Tran wrote:
Thanks Robert.
It works with stlport.
But my project currently uses rogue wave. I am looking a way to use Boost Serialiazation without changing my current codes (it is a tedious task).
Have you tried building/testing the serialization library with rwtools7_std? It's easy to try. Turns out that the serialization library originally worked with MSVC 6.0 and Borland 5.5 so it's possible it could work with your platform. The only thing that I know is broken is binary_?archive which lost backward compatibility with the introduction of a speed up for arrays.
Robert Ramey
Dennis
/DucTran
On Tue, Oct 15, 2013 at 12:01 AM, Robert Ramey <ramey@rrsd.com> wrote:
Duc Tran wrote:
Hi All,
My project is using rwtools7_std library on Sun Solaris.
However, Boos Serialization needs stlport4 and these two libraries cannot work together.
Does anyone use Boost on Sun Solaris with rwtools7_std before?
Can I change Boost library to use rwtools7_std instead of stlport4? The reason is my project has to use rwtools7_std.
In the past I tested with stlport - though not with this compiler - and had all the tests pass. This was several years ago so it won't help you much now. But it does indicate that it should be possible to make this work.
Thank you. Dennis
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Duc Tran wrote:
I have tried to compiling the serialization library with rwtools7_std but failed; but able to compile with stlport4. Here is complie logs with rwtools7_std.
$ ./bjam --toolset=sun --j4 --build-dir=./build --with-serialization stage
<snip>.. That's all the errors? It seems to me that making the serialization work with this environment would be doable - but it would take some effort. So I can't offer you any zero effort solution. If your company wanted to sponsor this kind effort we could talk about it. Or you could do it yourself. Robert Ramey
That's not all errors, still have many. Unfortunately, my company is unable to sponsor it. I have to do it myself. Do you have any suggestions? /DucTran On Thu, Oct 17, 2013 at 12:34 AM, Robert Ramey <ramey@rrsd.com> wrote:
Duc Tran wrote:
I have tried to compiling the serialization library with rwtools7_std but failed; but able to compile with stlport4. Here is complie logs with rwtools7_std.
$ ./bjam --toolset=sun --j4 --build-dir=./build --with-serialization stage
<snip>..
That's all the errors? It seems to me that making the serialization work with this environment would be doable - but it would take some effort. So I can't offer you any zero effort solution. If your company wanted to sponsor this kind effort we could talk about it. Or you could do it yourself.
Robert Ramey
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Duc Tran wrote:
That's not all errors, still have many. Unfortunately, my company is unable to sponsor it. I have to do it myself. Do you have any suggestions?
No specific suggestion - you just have to do the work. On the upside you'll learn alot. Here are some ideas. It looks to me that things are looking pretty good. Just make changes to get the library to build. Once it builds you can run the tests. Then you go through each failed test and make changes to the library untill all tests pass. That's all there is to it. I'm guessing you're company is underestimating the effort required - or maybe I'm over estimating. Good luck in any case. Robert Ramey
participants (2)
-
Duc Tran -
Robert Ramey