Opened 5 years ago
Closed 4 years ago
#58827 closed defect (fixed)
qgis @2.18.14+postgresql10 broken linking
Reported by: | ChrisFr | Owned by: | Veence (Vincent) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | ||
Port: | qgis |
Description
I installed wgrib2 which seemed successful other than a trailing report of two broken ports, one of them qgis. The console log is attached. I OKed an automatic rev-upgrade but that failed to rebuild qgis successfully.
I then updated the ports tree, cleaned the qgis port, and tried to rebuild qgis (port update qgis). This also failed. The build log for this second attempt is attached.
Attachments (2)
Change History (5)
Changed 5 years ago by ChrisFr
Attachment: | consolelog.txt added |
---|
Changed 5 years ago by ChrisFr
Attachment: | main.log.zip added |
---|
comment:1 Changed 5 years ago by jmroot (Joshua Root)
Owner: | set to Veence |
---|---|
Port: | qgis added |
Status: | new → assigned |
Summary: | qgis @2.18.14+postgresql10 broken by install of wgrib2 @2.0.7_9+gfortran → qgis @2.18.14+postgresql10 broken linking |
comment:2 Changed 5 years ago by ChrisFr
OK, but I'm a bit bemused by your comments, Vince. The initial report of linking errors was directed to the console towards the end of an install. At that point I had not knowingly initiated a rev-upgrade, or even taken any action to cause a check to be made of binaries that might be associated with the install. Is it the case that binaries for all ports are checked for linking errors at the end of an install, or perhaps just ports that might be affected? Does answering the question "The following ports will be rebuilt: x, y, z; Continue? [Y/n]:" Y cause a rev-upgrade? If so, perhaps that should be stated clearly.
comment:3 Changed 4 years ago by Veence (Vincent)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
- Outdated -
The broken linking in qgis could easily have nothing to do with wgrib2, it just happened to be detected by rev-upgrade running after installing the latter. If you run
sudo port -dy rev-upgrade
you will get more detailed information about which files are mis-linked without actually attempting to rebuild the corresponding ports.