Boost C++ Libraries: Ticket #2291: unregistered void cast in 1.35 for all test_exported* tests https://svn.boost.org/trac10/ticket/2291 <p> I believe I am experiencing the same failures reported as unresolved issues against gcc-4.2.1 here: <a href="http://www.boost.org/development/tests/release-1_35_0/developer/issues_release_.html#serialization">http://www.boost.org/development/tests/release-1_35_0/developer/issues_release_.html#serialization</a>. I am using gcc-4.0.1 on SLES-10 Linux. It is well known that darwin-4.0.1 is not quite a normal gcc toolset, which may explain why it does not show the same failures in Boost-1.35. Unfortunately, for 1.36, it appears that we stopped testing on the platforms where the unresolved issues were coming up, so the problems were effectively masked. </p> <p> Robert, I can test against 1.36.0 or the trunk on request. I can also give you access to the machine where these failures are occurring on request. If these issues were actually somehow fixed for 1.36, I'd like to know what the changes were. </p> <p> Noel, are you still seeing those failures when you test on the same machines? </p> <p> Thanks </p> en-us Boost C++ Libraries /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/2291 Trac 1.4.3 Dave Abrahams Fri, 05 Sep 2008 20:30:11 GMT attachment set https://svn.boost.org/trac10/ticket/2291 https://svn.boost.org/trac10/ticket/2291 <ul> <li><strong>attachment</strong> → <span class="trac-field-new">serialization-release.log</span> </li> </ul> <p> bjam testing log </p> Ticket Dave Abrahams Fri, 05 Sep 2008 20:31:38 GMT cc set https://svn.boost.org/trac10/ticket/2291#comment:1 https://svn.boost.org/trac10/ticket/2291#comment:1 <ul> <li><strong>cc</strong> <span class="trac-author">Beman Dawes</span> <span class="trac-author">kbelco@…</span> added </li> </ul> Ticket Robert Ramey Fri, 05 Sep 2008 22:54:20 GMT <link>https://svn.boost.org/trac10/ticket/2291#comment:2 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/2291#comment:2</guid> <description> <p> note that between 1.35 and 1.36 there were a lot of changes related making the library thread safe. This sort of rippled through export and pretty much replaced ALL the hacky code required to get things instantiated and avoid code stripping on the wide variety of platforms. To the extent there is some of the hacky code left, its mostly concentrated in boost/serialization/singleton and a little bit in boost/serialization/export. </p> <p> Given this, only a test of 1.36 or trunk would be of value to me. </p> <p> Since I just checked in some changes to the trunk day before yesterday, the easiest would be to wait a week or so and test against the trunk. Or maybe even simpler, just add this combination to the normal trunk tests for at least one cycle. Now that I'm installed some changes, I'll be checking the trunk tests for the next week or so. </p> <p> Robert Ramey </p> <p> Robert Ramey </p> </description> <category>Ticket</category> </item> <item> <dc:creator>Dave Abrahams</dc:creator> <pubDate>Fri, 05 Sep 2008 23:29:10 GMT</pubDate> <title/> <link>https://svn.boost.org/trac10/ticket/2291#comment:3 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/2291#comment:3</guid> <description> <p> Replying to <a class="ticket" href="https://svn.boost.org/trac10/ticket/2291#comment:2" title="Comment 2">ramey</a>: </p> <blockquote class="citation"> <p> Given this, only a test of 1.36 or trunk would be of value to me. </p> </blockquote> <p> As I said, I'll be happy to test either or both. Just let me know what you would like. </p> <blockquote class="citation"> <p> Since I just checked in some changes to the trunk day before yesterday, the easiest would be to wait a week or so and test against the trunk. </p> </blockquote> <p> Now, why would I want to wait? </p> <blockquote class="citation"> <p> Or maybe even simpler, just add this combination to the normal trunk tests for at least one cycle. Now that I'm installed some changes, I'll be checking the trunk tests for the next week or so. </p> </blockquote> <p> Sorry, which combination? You lost me. </p> </description> <category>Ticket</category> </item> <item> <dc:creator>Dave Abrahams</dc:creator> <pubDate>Fri, 05 Sep 2008 23:48:08 GMT</pubDate> <title>attachment set https://svn.boost.org/trac10/ticket/2291 https://svn.boost.org/trac10/ticket/2291 <ul> <li><strong>attachment</strong> → <span class="trac-field-new">changeset_r43949_backport.patch</span> </li> </ul> Ticket Dave Abrahams Fri, 05 Sep 2008 23:54:46 GMT <link>https://svn.boost.org/trac10/ticket/2291#comment:4 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/2291#comment:4</guid> <description> <p> Actually all that was needed was to backport <a class="changeset" href="https://svn.boost.org/trac10/changeset/43949" title="fixes #1711">r43949</a>; patch attached. You might want to close <a class="closed ticket" href="https://svn.boost.org/trac10/ticket/1711" title="#1711: Bugs: Boost Serialization export facility broken on gcc 4.1, 4.2 (closed: fixed)">#1711</a> when you decide how to dispose of this ticket. </p> </description> <category>Ticket</category> </item> <item> <dc:creator>Robert Ramey</dc:creator> <pubDate>Sat, 06 Sep 2008 03:34:40 GMT</pubDate> <title/> <link>https://svn.boost.org/trac10/ticket/2291#comment:5 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/2291#comment:5</guid> <description> <p> When I look at the current tests, I see gcc 4.01 passing all tests for darwin (both ppc and intel builds). I also see gcc 4.2.1 passing all tests. Do you still think that application of this patch to the trunk is necessary?. </p> </description> <category>Ticket</category> </item> <item> <dc:creator>Dave Abrahams</dc:creator> <pubDate>Sat, 06 Sep 2008 23:22:38 GMT</pubDate> <title>cc deleted https://svn.boost.org/trac10/ticket/2291#comment:6 https://svn.boost.org/trac10/ticket/2291#comment:6 <ul> <li><strong>cc</strong> <span class="trac-author">Beman Dawes</span> <span class="trac-author">kbelco@…</span> removed </li> </ul> <p> Replying to <a class="ticket" href="https://svn.boost.org/trac10/ticket/2291#comment:5" title="Comment 5">ramey</a>: </p> <blockquote class="citation"> <p> When I look at the current tests, I see gcc 4.01 passing all tests for darwin (both ppc and intel builds). I also see gcc 4.2.1 passing all tests. </p> </blockquote> <p> Yes, that's all because of <a class="changeset" href="https://svn.boost.org/trac10/changeset/43949" title="fixes #1711">r43949</a> </p> <blockquote class="citation"> <p> Do you still think that application of this patch to the trunk is necessary?. </p> </blockquote> <p> No; that patch is the backport of <a class="changeset" href="https://svn.boost.org/trac10/changeset/43949" title="fixes #1711">r43949</a> to the 1.35 codebase. Was something unclear about that? I attached it in case Boost should ever do a 1.35.1 release or you would like to post a hotfix. </p> <p> Again, I suggest looking at <a class="closed ticket" href="https://svn.boost.org/trac10/ticket/1711" title="#1711: Bugs: Boost Serialization export facility broken on gcc 4.1, 4.2 (closed: fixed)">#1711</a> and seeing if you want to close it. In your place, I certainly would. </p> Ticket Robert Ramey Sun, 07 Sep 2008 04:49:38 GMT status changed; resolution set https://svn.boost.org/trac10/ticket/2291#comment:7 https://svn.boost.org/trac10/ticket/2291#comment:7 <ul> <li><strong>status</strong> <span class="trac-field-old">new</span> → <span class="trac-field-new">closed</span> </li> <li><strong>resolution</strong> → <span class="trac-field-new">fixed</span> </li> </ul> <p> fixed in 1.36 </p> Ticket