Opened 13 years ago

Closed 13 years ago

Last modified 13 years ago

#3677 closed Bugs (fixed)

Serialization via a reference to a pointer fails at compile time

Reported by: churanov.port.maintainer@… Owned by: Robert Ramey
Milestone: Boost 1.42.0 Component: serialization
Version: Boost 1.41.0 Severity: Regression
Keywords: Cc:

Description

The 'x11-toolkits/gigi' application failed to compile with the Boost-1.41. The application is known to build successfully with boost 1.39.

The error message is: error: cannot convert 'const boost::serialization::extended_type_info_typeid<GG::Font>' to 'const boost::serialization::extended_type_info*' in return

The issue may be reproduced using the preprocessed translation unit "saveload.ii"

The command-line is g++43 -o saveload.o -c -fno-strict-aliasing -pipe -Wall -Wno-parentheses -O2 -pthread saveload.ii

The operating system is FreeBSD 7.2-RELEASE/i386
The compiler is g++43 (GCC) 4.3.5 20091115 (prerelease)

Links to external files:

Error log fragment - http://alexanderchuranov.com/boost-port/gigi-boost-1.41/gigi-boost-1.41.0.log
The preprocessed translation unit - http://alexanderchuranov.com/boost-port/gigi-boost-1.41/saveload.ii
The full application source - http://www.freebsd.org/cgi/pds.cgi?ports/x11-toolkits/gigi

Change History (8)

comment:1 by Robert Ramey, 13 years ago

Resolution: fixed
Status: newclosed

I believe this is the same problem reported in another ticket. That ticket has been addressed and the fix has been checked into the trunk. I will migrate to the release branch soon.

So I'm marking this as "fixed". Feel free to integrate the fix from the trunk to your own copy and retest.

Robert Ramey

comment:2 by churanov.port.maintainer@…, 13 years ago

Robert,

Please, be specific on this. What is 'that' ticket?

I've looked through the tickets for 1.41, 1.42 and unspecified milestones and did not find the appropriate one. I'd like to patch for the specific issue or a set of issues, not to integrate all changes from the trunk.

Could you please provide me with exact ticket name/ID?

Alexander Churanov,
maintainer of devel/boost-* for FreeBSD

comment:3 by anonymous, 13 years ago

Damn, I can't find the track item either.

But I believe that I have fixed this (if it's what I think it is) and checked the fix into the trunk. If all goes well, I'll merger these changes into the release in a week or so.

Robert Ramey

comment:4 by gast128, 13 years ago

I had the same problem searching for the ticket. But I think it is 'https://svn.boost.org/trac/boost/ticket/3638'

comment:5 by churanov.port.maintainer@…, 13 years ago

Robert,

I see 12 modified files under /serialization in trunk and more than one hundred under /archive compared to 1.41 release tag. The ticket #3638 does not contain any information about the check-in which fixed the issue.

Could you point me to correct revision numbers, so that I could create a patch that fixes the particular issue?

If this is really hard, I would be pleased if you just tell me how to roll back the serialization library from 1.41 to 1.39, which is known to work. Is that possible given that there are dependencies between Boost libraries?

Thank you for your attention to this problem.

Alexander Churanov

comment:6 by churanov.port.maintainer@…, 13 years ago

Resolution: fixed
Status: closedreopened

Folks,

Please provide a definite answer on this.

The issue is important, because the update of serialization library to 1.41 breaks the existing application, preventing the whole boost package from integration into the FreeBSD ports.

It is sufficient to provide one of the following:

1) A patch file that fixes the issue.
2) A revision number, in which the issue was fixed.
3) A set of instructions explaining how to roll back the serialization library to 1.39 (it's known to work).

Alexander Churanov
maintainer of devel/boost-* for FreeBSD

comment:7 by Robert Ramey, 13 years ago

Resolution: fixed
Status: reopenedclosed

The fix for this was checked into the trunk 27 November - change set #57981.

Subsequently, all changes in the trunk have been merged to the release branch so should show up in version 1.42

Robert Ramey

comment:8 by churanov.port.maintainer@…, 13 years ago

Robert,

Using the change set information provided by you I was able to find the particular fix and include it into the port. This allows Gigi toolkit to build successfully.

Thank you for your time!

Alexander Churanov

Note: See TracTickets for help on using tickets.