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)

[sumnernh@…]

Attempting to build medusa fails, asked me to submit error report with following debug: ​http://pastebin.com/Xdq868Ac

[sumnernh@…]

sorry, not build fail, "broken"

[ryandesign (Ryan Carsten Schmidt)]

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.

[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.

[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.

[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?

[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)

[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

[neverpanic (Clemens Lang)]

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.