From: Sean Perry (perry_at_[hidden])
Date: 2005-07-08 09:56:07
Which version of vacpp are you using? The vacpp 7.0 compiler handles the
static const data as you expect it. That should solve the unresolved
externals.
If you need help with aix or vacpp issues, feel free to contact me.
--
Sean Perry
Compiler Development
IBM Canada Lab
(905)-413-6031 (tie 969-6031), fax (905)-413-4839
Joaquín Mª López
Muñoz
<joaquin_at_[hidden]> To
Sent by: boost_at_[hidden]
boost-bounces_at_lis cc
ts.boost.org
Subject
Re: [boost] [1.33.0] [acc] [vacpp]
07/08/2005 03:54 Release status and updated
AM timeline
Please respond to
boost
Robert Ramey ha escrito:
>
> b) acc - looks pretty good - but all DLL versions fail
I cannot help much here, but I can confirm that as of
June 28, dll tests were working OK on this compiler, and in
fact only 14 tests used to fail:
http://listarchives.boost.org/boost/2005/06/29357.php
so I guess something has changed later on that breaks this
platform.
>
> g) last time I checked SunOS, DMC and vacpp failed to build the library
due
> to failures in code outside the serialization library. Generally I have
> marked these compilers as not usable.
>
Toon Knapen and I have beeing doing some offlist research on
vacpp these days, and came close to being able to use Boost.Serialization,
but finally gave up. I summarize here our findings in case you want to
take on the challenge (now or after 1.33)
* Currently Boost.Serialization builds in vacpp.
* When trying to use it, the linker complains about undefined symbols
like this:
ld: 0711-317 ERROR: Undefined symbol:
boost::serialization::version<boost::serialization::nvp<const unsigned
long>
>::value
this seems to be related to a defect in the compiler by which it needs
static const data to be defined outside their class:
http://listarchives.boost.org/MailArchives/boost/msg30039.php
the problem can be remedied by defining
BOOST_NO_INCLASS_MEMBER_INITIALIZATION, though I'm not sure this
is a safe move (see http://listarchives.boost.org/boost/2004/07/7289.php).
* We locally defined BOOST_NO_INCLASS_MEMBER_INITIALIZATION
for vacpp 6.0 (this change hasn't been commited to the CVS) and the
aforementioned
problems went away, but then other type of undefined symbols appeared:
ld: 0711-317 ERROR: Undefined symbol:
.boost::archive::detail::basic_archive_impl::lookup_helper(const
boost::serialization::extended_type_info*,boost::shared_ptr<void>&)
ld: 0711-317 ERROR: Undefined symbol:
.boost::archive::detail::basic_archive_impl::insert_helper(const
boost::serialization::extended_type_info*,boost::shared_ptr<void>&)
ld: 0711-317 ERROR: Undefined symbol:
.boost::archive::detail::basic_pointer_iserializer::~basic_pointer_iserializer()
ld: 0711-317 ERROR: Undefined symbol:
.boost::archive::detail::basic_pointer_iserializer::basic_pointer_iserializer(const
boost::serialization::extended_type_info&)
ld: 0711-317 ERROR: Undefined symbol:
.boost::archive::detail::basic_pointer_oserializer::~basic_pointer_oserializer()
ld: 0711-317 ERROR: Undefined symbol:
.boost::archive::detail::basic_pointer_oserializer::basic_pointer_oserializer(c
and here I gave up. I hope this info is of some help in case you
decide to work on making Boost.Serialization work for vacpp.
Best,
Joaquín M López Muñoz
Telefónica, Investigación y Desarrollo
_______________________________________________
Unsubscribe & other changes:
http://listarchives.boost.org/mailman/listinfo.cgi/boost