Opened 11 years ago
Closed 11 years ago
#37152 closed defect (invalid)
medusa: rev-upgrade says broken because: Could not open /usr/lib/libpq.5.dylib: Error opening or reading file (referenced from /opt/local/lib/medusa/modules/cvs.mod)
| Reported by: | sumnernh@… | Owned by: | pmq@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.1.2 |
| Keywords: | Cc: | ||
| Port: | medusa |
Description
Attempting to build medusa fails, asked me to submit error report with following debug: http://pastebin.com/Xdq868Ac
Change History (8)
comment:1 Changed 11 years ago by sumnernh@…
comment:2 follow-up: 7 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
| Keywords: | medusa build fail removed |
|---|---|
| Owner: | changed from macports-tickets@… to pmq@… |
| Summary: | medusa 2.1.1 build fail OSX 10.8.2 → medusa: rev-upgrade says broken because: Could not open /usr/lib/libpq.5.dylib: Error opening or reading file (referenced from /opt/local/lib/medusa/modules/cvs.mod) |
Looks like rev-upgrade found that medusa was broken because it linked with a file that is not there anymore:
Could not open /usr/lib/libpq.5.dylib: Error opening or reading file (referenced from /opt/local/lib/medusa/modules/cvs.mod)
/usr/lib/libpq.5.dylib exists on my Mountain Lion system (does it exist on yours?), but regardless medusa should not be linking with it; if medusa requires PostgreSQL, it should be using one of the MacPorts postgresql9X ports.
comment:3 follow-up: 4 Changed 11 years ago by pmq@…
Maybe an easy fix for you would be to uninstall medusa, clean it then reinstall the port. I will fix the port but in the mean time you can probably try that.
comment:4 follow-up: 5 Changed 11 years ago by sumnernh@…
Replying to pmq@…:
Maybe an easy fix for you would be to uninstall medusa, clean it then reinstall the port. I will fix the port but in the mean time you can probably try that.
In the meantime I made a symlink for "/usr/lib/libpq.5.4.dylib" (which does exist) named "/usr/lib/libpq.5.dylib". Medusa links to it and seems happy.
comment:5 follow-up: 6 Changed 11 years ago by neverpanic (Clemens Lang)
Replying to sumnernh@…:
In the meantime I made a symlink for "/usr/lib/libpq.5.4.dylib" (which does exist) named "/usr/lib/libpq.5.dylib". Medusa links to it and seems happy.
Can you provide the output of otool -L /usr/lib/libpq.5.4.dylib?
comment:6 Changed 11 years ago by sumnernh@…
Replying to cal@…:
Replying to sumnernh@…:
In the meantime I made a symlink for "/usr/lib/libpq.5.4.dylib" (which does exist) named "/usr/lib/libpq.5.dylib". Medusa links to it and seems happy.
Can you provide the output of
otool -L /usr/lib/libpq.5.4.dylib?
it Gives:
/usr/lib/libpq.5.4.dylib:
/usr/lib/libpq.5.dylib (compatibility version 5.0.0, current version 5.4.0) /usr/lib/libssl.0.9.8.dylib (compatibility version 0.9.8, current version 47.0.0) /usr/lib/libcrypto.0.9.8.dylib (compatibility version 0.9.8, current version 47.0.0) /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos (compatibility version 5.0.0, current version 6.0.0) /System/Library/Frameworks/LDAP.framework/Versions/A/LDAP (compatibility version 1.0.0, current version 2.4.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)
comment:7 Changed 11 years ago by sumnernh@…
Replying to ryandesign@…:
Looks like rev-upgrade found that medusa was broken because it linked with a file that is not there anymore:
Could not open /usr/lib/libpq.5.dylib: Error opening or reading file (referenced from /opt/local/lib/medusa/modules/cvs.mod)/usr/lib/libpq.5.dylib exists on my Mountain Lion system (does it exist on yours?), but regardless medusa should not be linking with it; if medusa requires PostgreSQL, it should be using one of the MacPorts postgresql9X ports.
It doesn't, but 5.4 does
comment:8 Changed 11 years ago by neverpanic (Clemens Lang)
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
The otool output clearly shows why the build did link against /usr/lib/libpq.5.dylib: It's the ID of the library in /usr/local/libpq.5.4.dylib (see the first line of the output).
If this file is not present in your installation your installation is broken. Whoever shipped this file should also have installed the symlink you manually created (or you accidentially deleted it at some point in time).
This is not a bug in MacPorts or the medusa port.
sorry, not build fail, "broken"