Opened 13 years ago

Closed 12 years ago

#31379 closed defect (fixed)

Podofo 0.9.1 build fails

Reported by: Greisby (Greisberger Christophe) Owned by: dbevans (David B. Evans)
Priority: Normal Milestone:
Component: ports Version: 2.0.3
Keywords: Cc:
Port: podofo

Description

Other infos:
OS: Snow Leopard 10.6.8
Arch: x86_64
FS: case sensitive
XCode: 4.0.2

Upgrading from 0.9.0 to 0.9.1 fails during the compilation phase.

First error in log:

:info:build //usr/include/c++/4.2.1/bits/stl_vector.h: In constructor ‘PoDoFo::PdfFontMetricsObject::PdfFontMetricsObject(PoDoFo::PdfObject*, PoDoFo::PdfObject*, const PoDoFo::PdfEncoding*)’:
:info:build //usr/include/c++/4.2.1/bits/stl_vector.h:419: error: ‘void std::vector<_Tp, _Alloc>::resize(size_t, _Tp) [with _Tp = PoDoFo::PdfObject, _Alloc = std::allocator<PoDoFo::PdfObject>]’ is inaccessible
:info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_podofo/podofo/work/podofo-0.9.1/src/doc/PdfFontMetricsObject.cpp:95: error: within this context
:info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_podofo/podofo/work/podofo-0.9.1/src/doc/PdfFontMetricsObject.cpp:95: error: ‘std::vector<PoDoFo::PdfObject, std::allocator<PoDoFo::PdfObject> >’ is not an accessible base of ‘PoDoFo::PdfArray’

I googled a bit but found only one reference:
http://www.mail-archive.com/podofo-users@lists.sourceforge.net/msg01595.html
It's a post about the same error with gcc 4.4 on Gentoo, and a fix in rev. 1447 of podofo (podofo 0.9.0 - 0.9.1 is rev. 1460)
Perhaps a regression?

Full build log file is attached to ticket.

Attachments (1)

podofo_build.log (827.8 KB) - added by Greisby (Greisberger Christophe) 13 years ago.
Build log

Download all attachments as: .zip

Change History (6)

Changed 13 years ago by Greisby (Greisberger Christophe)

Attachment: podofo_build.log added

Build log

comment:1 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: devans@… removed
Owner: changed from macports-tickets@… to devans@…

comment:2 Changed 13 years ago by jmknoble+macports@…

I've encountered the same problem upgrading podofo @0.9.0_0 to 0.9.1_0. Xcode Version 3.2.6 (1761) on Mac OS X 10.6.8.

comment:3 Changed 13 years ago by dbevans (David B. Evans)

Status: newassigned

comment:4 Changed 13 years ago by dbevans (David B. Evans)

I'm still working on a better fix but I think you can work around this by deactivating the old version before installing the new

sudo port deactivate podofo
sudo port install podofo

comment:5 Changed 12 years ago by dbevans (David B. Evans)

Resolution: fixed
Status: assignedclosed

The problem here is that somehow cmake generates build compile flags that put the MacPorts include path before the builds own private include paths. Therefore, if a previous version of podofo is active then its include files can override the new version's own files. I've mucked around with the cmake files quite a bit but I can't get it to quit doing this.

For now have added a pre-build phase to the port that asks the user to deactivate any active podofo port (if it exists) before performing the build.

Any suggestions on how to solve this otherwise would be appreciated. I'm also reporting this upstream.

Committed in r86836.

Note: See TracTickets for help on using tickets.