[Boost-testing] Re: serialization library test on tru64 cxx

From: Robert Ramey (ramey_at_[hidden])
Date: 2004-10-25 12:23:00

Hmmm - I'm not sure I can speculate on how to address this.  However I can
offer some observations which might be useful.

a) It doesn't seem to miss any of the symbols defined in the
test_execmonitor library.
b) it seems that expicit instanciations are not being included.  These are
found in the *.ipp files.  Instantiations of these function should be found
in the library.  you might try displaying the strings of the library to see
if these instantiations are in there.
c) It seems taht const static variables are not found in the library
(ARCHIVE_VERSION).  The library should be checked for these
c) template instantiations don't seem to be generated for the test modules.
This could be a compiler quirk.  This could result in modles not being
generated for the library.
d) some functions void_cast_self_register arn't even templates an not found
in the library.  This function is called as part of a template instantiation
however.

To me its seems quite possible that explicit template instantiation needs
some kind of compiler/link switches on this platfform to be supported.  This
is pure specualtion on my part - sorry I can't be of more help.

Robert Ramey

"Markus Schöpflin" <markus.schoepflin_at_[hidden]> wrote in message
news:clihpl$798$1_at_sea.gmane.org...
Robert Ramey wrote:

> "Markus Schöpflin" <markus.schoepflin_at_[hidden]> wrote in message
> news:cl3q15$bji$1_at_sea.gmane.org...

>> Just today I comment out this workaround locally to see if I could do
>> anything about it. The library compiles ok if the workaround is
>> removed but I had unresolved symbols when linking, so I didn't pursue
>> the issue any further. If you are interested, I will try to get a
>> small isolated test case from the serialization library up and
>> running.
>
> I'm sure that this is why I put in that special code for rogue wave.  I
> would like to see the list of undefined symbols.  I suspect this can be
> addressed by using a special workaround for this platform just as I made
> one for the one we did for BCB 5.5.1 .  I'm inclined to comment out this
> work around for this platform and see which tests fail to link in the
> nightly test

I finally got around to producing the list of unresolved symbols. Here they
are:

tru64cxx65-Link-action
../../../bin/boost/libs/serialization/test/test_shared_ptr_text_archive.test
/tru64cxx65-041/debug/test_shared_ptr_text_archive

    cxx -noimplicit_include -g -model ansi -gall  -o
"../../../bin/boost/libs/serialization/test/test_shared_ptr_text_archive.tes
t/tru64cxx65-041/debug/test_shared_ptr_text_archive
"
-L../../../bin/boost/libs/serialization/build/libboost_serialization.a/tru64
cxx65-041/debug
-L../../../bin/boost/libs/test/build/libboost_test_exec_monitor.a/tru64cxx65
-041/deb
ug
"../../../bin/boost/libs/serialization/test/test_shared_ptr_text_archive.tes
t/tru64cxx65-041/debug/test_shared_ptr.o"
  "../../../bin/boost/libs/serialization/build/libboost_s
erialization.a/tru64cxx65-041/debug/libboost_serialization.a"
"../../../bin/boost/libs/test/build/libboost_test_exec_monitor.a/tru64cxx65-
041/debug/libboost_test_exec_monitor.a"

"../../../bin/boost/libs/serialization/build/libboost_serialization.a/tru64c
xx65-041/debug/libboost_serialization.a"
"../../../bin/boost/libs/test/build/libboost_test_exec_monitor
.a/tru64cxx65-041/debug/libboost_test_exec_monitor.a"   -lrt -lm

ld:
Unresolved:
boost::serialization::detail::extended_type_info_typeid_0::type_info_key
boost::archive::null_pointer_tag
boost::archive::ARCHIVE_SIGNATURE
boost::archive::ARCHIVE_VERSION
boost::serialization::extended_type_info::self_register(void)
boost::serialization::extended_type_info::find(const
boost::serialization::extended_type_info*)
boost::serialization::void_cast_detail::void_caster::self_register(void)
void
boost::archive::text_oarchive_impl<boost::archive::text_oarchive>::save(cons
t
std::basic_string<char, std::char_traits<char>, std::allocator<char> >&)
boost::archive::basic_text_oprimitive<T0=std::basic_ostream<char,
std::char_traits<char> > >::basic_text_oprimitive(T0&, bool)
boost::archive::basic_text_oprimitive<std::basic_ostream<char,
std::char_traits<char> > >::~basic_text_oprimitive(void)
void
boost::archive::text_iarchive_impl<boost::archive::text_iarchive>::load(std:
:basic_string<char,
std::char_traits<char>, std::allocator<char> >&)
boost::archive::basic_text_iprimitive<T0=std::basic_istream<char,
std::char_traits<char> > >::basic_text_iprimitive(T0&, bool)

<and more to come>

Can you make anything out of this?

Markus