[MacPorts] #50119: LibreCAD 2.0.8_0.darwin failure on destroot
#50119: LibreCAD 2.0.8_0.darwin failure on destroot --------------------------------+-------------------------------- Reporter: ernesto.migliore@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: --------------------------------+-------------------------------- Hi, LibreCAD installation fails on mac osx 10.10.5 with the following trace log ---> Verifying checksums for LibreCAD ---> Extracting LibreCAD ---> Configuring LibreCAD ---> Building LibreCAD ---> Staging LibreCAD into destroot Error: org.macports.destroot for port LibreCAD returned: command execution failed To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port LibreCAD failed -- Ticket URL: <https://trac.macports.org/ticket/50119> MacPorts <https://www.macports.org/> Ports system for OS X
#50119: LibreCAD 2.0.8_0.darwin failure on destroot ---------------------------------+------------------------ Reporter: ernesto.migliore@… | Owner: librecad@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: LibreCAD | ---------------------------------+------------------------ Changes (by ryandesign@…): * cc: dongxuli2011@… (added) * owner: macports-tickets@… => librecad@… * port: => LibreCAD Old description:
Hi, LibreCAD installation fails on mac osx 10.10.5 with the following trace log
---> Verifying checksums for LibreCAD ---> Extracting LibreCAD ---> Configuring LibreCAD ---> Building LibreCAD ---> Staging LibreCAD into destroot Error: org.macports.destroot for port LibreCAD returned: command execution failed To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port LibreCAD failed
New description: Hi, LibreCAD installation fails on mac osx 10.10.5 with the following trace log {{{ ---> Verifying checksums for LibreCAD ---> Extracting LibreCAD ---> Configuring LibreCAD ---> Building LibreCAD ---> Staging LibreCAD into destroot Error: org.macports.destroot for port LibreCAD returned: command execution failed To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port LibreCAD failed }}} -- Comment: The failure in the destroot phase is: {{{ sh: macdeployqt: command not found }}} I also see earlier errors in the build phase. The errors are not formatted correctly (missing newlines at the end of each error, causing them all to run together on a single line); I've tried to clean it up here for legibility: {{{ Project MESSAGE: We will be using CPP11 features Project ERROR: Boost installation not found. Project ERROR: does not contain a Boost installation Project MESSAGE: Using bundled muparser Project MESSAGE: Emulating C99 math features. Project MESSAGE: qtAddLibrary: found framework QtHelp in directory /opt/local/libexec/qt4/Library/Frameworks Project MESSAGE: Warning: unknown QT: help Project MESSAGE: qtAddLibrary: found framework QtSvg in directory /opt/local/libexec/qt4/Library/Frameworks Project MESSAGE: qtAddLibrary: found framework QtSql in directory /opt/local/libexec/qt4/Library/Frameworks Project MESSAGE: qtAddLibrary: found framework QtGui in directory /opt/local/libexec/qt4/Library/Frameworks Project MESSAGE: qtAddLibrary: found framework QtCore in directory /opt/local/libexec/qt4/Library/Frameworks/opt/local/libexec/qt4/share/mkspecs/features/qt_functions.prf(240): Function 'system' is not implemented Project ERROR: Package muparser not foundPackage muparser was not found in the pkg-config search path. }}} {{{ Project MESSAGE: Using bundled muparser/opt/local/libexec/qt4/share/mkspecs/features/qt_functions.prf(240): Function 'system' is not implemented Project ERROR: Package muparser not foundPackage muparser was not found in the pkg-config search path. }}} The qt4-mac port was recently rearranged and file are now installed in different places than before. The LibreCAD port may need to be updated for those changes. -- Ticket URL: <https://trac.macports.org/ticket/50119#comment:1> MacPorts <https://www.macports.org/> Ports system for OS X
#50119: LibreCAD 2.0.8_0.darwin failure on destroot ---------------------------------+------------------------ Reporter: ernesto.migliore@… | Owner: librecad@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: LibreCAD | ---------------------------------+------------------------ Comment (by and.damore@…): The Boost and muParser errors are already in #42555 and #43276, those are not critical though as I see the application bundle in my work directory properly working. The command is being manually called in the overridden destroot phase, in fact replacing {{{ system -W ${worksrcpath} "macdeployqt LibreCAD.app" }}} with {{{ system -W ${worksrcpath} "$prefix/libexec/qt4/bin/macdeployqt LibreCAD.app" }}} is enough to complete destroot target. This makes me wonder if this is the right approach rather than going through the actual qmake's scripts considering '''scripts/build-osx.sh''' uses the '''${QT_PATH}/macdeployqt''' command. -- Ticket URL: <https://trac.macports.org/ticket/50119#comment:2> MacPorts <https://www.macports.org/> Ports system for OS X
#50119: LibreCAD 2.0.8_0.darwin failure on destroot ---------------------------------+------------------------ Reporter: ernesto.migliore@… | Owner: librecad@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: LibreCAD | ---------------------------------+------------------------ Comment (by ernesto.migliore@…): Replying to [comment:2 and.damore@…]:
The Boost and muParser errors are already in #42555 and #43276, those are not critical though as I see the application bundle in my work directory properly working.
The command is being manually called in the overridden destroot phase, in fact replacing {{{ system -W ${worksrcpath} "macdeployqt LibreCAD.app" }}} with {{{ system -W ${worksrcpath} "$prefix/libexec/qt4/bin/macdeployqt LibreCAD.app" }}} is enough to complete destroot target.
This makes me wonder if this is the right approach rather than going through the actual qmake's scripts considering '''scripts/build-osx.sh''' uses the '''${QT_PATH}/macdeployqt''' command.
Does it translate into something that a non-expert MacPort user (aka me) can do to fix the problem? -- Ticket URL: <https://trac.macports.org/ticket/50119#comment:3> MacPorts <https://www.macports.org/> Ports system for OS X
#50119: LibreCAD 2.0.8_0.darwin failure on destroot ---------------------------------+------------------------ Reporter: ernesto.migliore@… | Owner: librecad@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: LibreCAD | ---------------------------------+------------------------ Comment (by and.damore@…): Replying to [comment:3 ernesto.migliore@…]:
Does it translate into something that a non-expert MacPorts user (aka me) can do to fix the problem?
Either [https://guide.macports.org/#development.local-repositories create a local repository] and perform the mentioned change in the Portfile or just wait. I'm attaching the (trivial) patchfile. -- Ticket URL: <https://trac.macports.org/ticket/50119#comment:4> MacPorts <https://www.macports.org/> Ports system for OS X
#50119: LibreCAD 2.0.8_0.darwin failure on destroot ---------------------------------+------------------------ Reporter: ernesto.migliore@… | Owner: librecad@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: duplicate | Keywords: Port: LibreCAD | ---------------------------------+------------------------ Changes (by g5pw@…): * status: new => closed * resolution: => duplicate Comment: This is a duplicate of #49843 -- Ticket URL: <https://trac.macports.org/ticket/50119#comment:5> MacPorts <https://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts