Ticket #25319 (closed defect: fixed)
qwt52 will not destroot: libqwt_designer_plugin.bundle not found
| Reported by: | golden@… | Owned by: | michaelld@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.9.0 |
| Keywords: | Cc: | michaelld@… | |
| Port: | qwt52 |
Description (last modified by michaelld@…) (diff)
Am not able to build qwt using snow leopard 10.6.4 and Xcode 3.2.3
---> Computing dependencies for qwt52 ---> Fetching qwt52 ---> Verifying checksum(s) for qwt52 ---> Extracting qwt52 ---> Applying patches to qwt52 ---> Configuring qwt52 ---> Building qwt52 ---> Staging qwt52 into destroot Error: Target org.macports.destroot returned: shell command failed Log for qwt52 is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync. macports.org_release_ports_graphics_qwt52/main.log Error: Status 1 encountered during processing.
main.log is attached.
Attachments
Change History
comment:2 in reply to: ↑ description Changed 3 years ago by golden@…
Replying to golden@…:
Am not able to build qwt using snow leopard 10.6.4 and Xcode 3.2.2
---> Computing dependencies for qwt52 ---> Fetching qwt52 ---> Verifying checksum(s) for qwt52 ---> Extracting qwt52 ---> Applying patches to qwt52 ---> Configuring qwt52 ---> Building qwt52 ---> Staging qwt52 into destroot Error: Target org.macports.destroot returned: shell command failed Log for qwt52 is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_qwt52/main.log Error: Status 1 encountered during processing.
main.log is attached.
comment:5 Changed 3 years ago by jmr@…
- Summary changed from qwt52 will not install to qwt52 will not destroot: libqwt_designer_plugin.bundle not found
comment:6 Changed 3 years ago by michaelld@…
The actual installed file name as built is 'libqwt_designer_plugin.dylib' on OSX. For some reason, it's listed as 'libqwt_designer_plugin.bundle' in the Portfile. There's patch for qt4-mac that changes the extension to .bundle, which for some reason was removed 3 weeks ago (Changeset r68459). Is it desirable to use it (again)? It's simple to put back in place & it should fix this issue.