From: Sean Perry (perry_at_[hidden])
Date: 2005-07-08 14:19:27
I thought the additional failures were because of defining the workaround
macro. If you use v7.0 you don't need the macro which would make those
unreolved symbols go away.
I don't have our results for the v7.0 compiler with 1.33.0 right now. I
can post them later if you would like.
--
Sean Perry
Compiler Development, W-Code Architect
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]
07/08/2005 12:24 [vacpp] Release status
PM and updated timeline
Please respond to
boost
Sean Perry ha escrito:
> Which version of vacpp are you using?
6.0.
> The vacpp 7.0 compiler handles the
> static const data as you expect it. That should solve the unresolved
> externals.
Well, that'd fix the static const data externals, but after these an
additional
bunch of undefined symbols appear, as shown in my previous mail.
It'd be good to know whether vacpp 7.0 fixes those also.
Unfortunately, I am not the person running vacpp tests -- Toon Knapen
is the man, I only try to help a little.
>
>
> If you need help with aix or vacpp issues, feel free to contact me.
>
Joaquín M López Muñoz
Telefónica, Investigación y Desarrollo
_______________________________________________
Unsubscribe & other changes:
http://listarchives.boost.org/mailman/listinfo.cgi/boost