[MacPorts] #46926: libvisio-0.1 @0.1.1 build fails on Leopard/PPC
#46926: libvisio-0.1 @0.1.1 build fails on Leopard/PPC -----------------------+-------------------------------- Reporter: khepler@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: libvisio-0.1 -----------------------+-------------------------------- Building libvisio-0.1 fails on Leopard/PPC (PowerPC G5) with the error: {{{ ...snip... /opt/local/include/boost/spirit/home/classic/symbols/symbols.hpp:105: warning: declaration of 'result' shadows a member of 'this' CXX VSDGeometryList.lo CXX VSDOutputElementList.lo CXX VSDPages.lo CXX VSDParagraphList.lo CXX VSDParser.lo CXX VSDMetaData.lo VSDMetaData.cpp:229: error: integer constant is too large for 'long' type make[3]: *** [VSDMetaData.lo] Error 1 make[3]: *** Waiting for unfinished jobs.... ...snip... }}} The offending line in VSDMetaData.cpp is: {{{ static const uint64_t epoch = 11644473600; }}} Is this considered an upstream bug or should it be patched in Macports because the compiler it chose assumes a non-suffixed literal integer is a long? Secondly, after applying the supplied patch (that appends ULL to the literal), the build fails if doxygen is not installed. -- Ticket URL: <https://trac.macports.org/ticket/46926> MacPorts <https://www.macports.org/> Ports system for OS X
#46926: libvisio-0.1 @0.1.1 build fails on Leopard/PPC ---------------------------+---------------------- Reporter: khepler@… | Owner: devans@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: libvisio-0.1 | ---------------------------+---------------------- Changes (by larryv@…): * owner: macports-tickets@… => devans@… Comment: In future tickets, please Cc relevant port maintainers (`port info --maintainers libvisio-0.1`). -- Ticket URL: <https://trac.macports.org/ticket/46926#comment:1> MacPorts <https://www.macports.org/> Ports system for OS X
#46926: libvisio-0.1 @0.1.1 build fails on Leopard/PPC ---------------------------+---------------------- Reporter: khepler@… | Owner: devans@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: libvisio-0.1 | ---------------------------+---------------------- Comment (by zanderpower@…): Replying to [ticket:46926 khepler@…]: Thanks for the patch. I have been having the same problem. After patching, libvisio-0.1 built and installed fine for me. I will see if I can get the latest inkscape to work with it and let you know how it goes on this post. I have doxygen installed, so I am unable to give you any info on whether libvisio-0.1 would fail if this were not the case. (PPC PowerBook G4 1.67 GHz with Leopard 10.5.8) -- Ticket URL: <https://trac.macports.org/ticket/46926#comment:2> MacPorts <https://www.macports.org/> Ports system for OS X
#46926: libvisio-0.1 @0.1.1 build fails on Leopard/PPC ---------------------------+---------------------- Reporter: khepler@… | Owner: devans@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: libvisio-0.1 | ---------------------------+---------------------- Comment (by devans@…): Fix committed in r133352 which * adds patch provided to fix build on 10.5.8, appears to build without problem on later platforms. * add +docs variant to enable build of documentation using doxygen, disabled by default. Please confirm whether this fixes your Leopard issues or not. Thanks for the report and the solution. I don't have a working Leopard system any more so I have to rely on those who do for solutions to problems like this. -- Ticket URL: <https://trac.macports.org/ticket/46926#comment:3> MacPorts <https://www.macports.org/> Ports system for OS X
#46926: libvisio-0.1 @0.1.1 build fails on Leopard/PPC ---------------------------+---------------------- Reporter: khepler@… | Owner: devans@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: libvisio-0.1 | ---------------------------+---------------------- Changes (by devans@…): * status: new => assigned -- Ticket URL: <https://trac.macports.org/ticket/46926#comment:4> MacPorts <https://www.macports.org/> Ports system for OS X
#46926: libvisio-0.1 @0.1.1 build fails on Leopard/PPC ---------------------------+---------------------- Reporter: khepler@… | Owner: devans@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: libvisio-0.1 | ---------------------------+---------------------- Comment (by khepler@…): Builds fine now without +docs variant. Having trouble testing +docs because doxygen is erroring. But +docs properly sets doxygen as a dependency at least. -- Ticket URL: <https://trac.macports.org/ticket/46926#comment:5> MacPorts <https://www.macports.org/> Ports system for OS X
#46926: libvisio-0.1 @0.1.1 build fails on Leopard/PPC ---------------------------+---------------------- Reporter: khepler@… | Owner: devans@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: fixed | Keywords: Port: libvisio-0.1 | ---------------------------+---------------------- Changes (by devans@…): * status: assigned => closed * resolution: => fixed Comment: Replying to [comment:5 khepler@…]:
Builds fine now without +docs variant.
Good!
Having trouble testing +docs because doxygen is erroring. But +docs
properly sets doxygen as a dependency at least.
'''edit''': Looks like there's some trouble when passing +docs down to
doxygen: #43894
libvisio-0.1 +docs builds fine when doxygen is built beforehand without
+docs. Yes, that's why I added the +docs variant as the doxygen problem is/has been a known issue on this platform. Thanks for verifying the fix. -- Ticket URL: <https://trac.macports.org/ticket/46926#comment:6> MacPorts <https://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts