[MacPorts] #37152: medusa 2.1.1 build fail OSX 10.8.2
#37152: medusa 2.1.1 build fail OSX 10.8.2 -------------------------------+-------------------------------- Reporter: sumnernh@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: medusa build fail | Port: medusa -------------------------------+-------------------------------- Attempting to build medusa fails, asked me to submit error report with following debug: http://pastebin.com/Xdq868Ac -- Ticket URL: <https://trac.macports.org/ticket/37152> MacPorts <http://www.macports.org/> Ports system for Mac OS
#37152: medusa 2.1.1 build fail OSX 10.8.2 -------------------------+-------------------------------- Reporter: sumnernh@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: | Keywords: medusa build fail Port: medusa | -------------------------+-------------------------------- Comment (by sumnernh@…): sorry, not build fail, "broken" -- Ticket URL: <https://trac.macports.org/ticket/37152#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS
#37152: 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) -------------------------+------------------- Reporter: sumnernh@… | Owner: pmq@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: | Keywords: Port: medusa | -------------------------+------------------- Changes (by ryandesign@…): * owner: macports-tickets@… => pmq@… * keywords: medusa build fail => Comment: 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. -- Ticket URL: <https://trac.macports.org/ticket/37152#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS
#37152: 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) -------------------------+------------------- Reporter: sumnernh@… | Owner: pmq@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: | Keywords: Port: medusa | -------------------------+------------------- Comment (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. -- Ticket URL: <https://trac.macports.org/ticket/37152#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS
#37152: 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) -------------------------+------------------- Reporter: sumnernh@… | Owner: pmq@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: | Keywords: Port: medusa | -------------------------+------------------- Comment (by sumnernh@…): Replying to [comment:3 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. -- Ticket URL: <https://trac.macports.org/ticket/37152#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS
#37152: 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) -------------------------+------------------- Reporter: sumnernh@… | Owner: pmq@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: | Keywords: Port: medusa | -------------------------+------------------- Comment (by cal@…): Replying to [comment:4 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`? -- Ticket URL: <https://trac.macports.org/ticket/37152#comment:5> MacPorts <http://www.macports.org/> Ports system for Mac OS
#37152: 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) -------------------------+------------------- Reporter: sumnernh@… | Owner: pmq@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: | Keywords: Port: medusa | -------------------------+------------------- Comment (by sumnernh@…): Replying to [comment:5 cal@…]:
Replying to [comment:4 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) -- Ticket URL: <https://trac.macports.org/ticket/37152#comment:6> MacPorts <http://www.macports.org/> Ports system for Mac OS
#37152: 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) -------------------------+------------------- Reporter: sumnernh@… | Owner: pmq@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: | Keywords: Port: medusa | -------------------------+------------------- Comment (by sumnernh@…): Replying to [comment:2 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 -- Ticket URL: <https://trac.macports.org/ticket/37152#comment:7> MacPorts <http://www.macports.org/> Ports system for Mac OS
#37152: 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) -------------------------+-------------------- Reporter: sumnernh@… | Owner: pmq@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: invalid | Keywords: Port: medusa | -------------------------+-------------------- Changes (by cal@…): * status: new => closed * resolution: => invalid Comment: 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. -- Ticket URL: <https://trac.macports.org/ticket/37152#comment:8> MacPorts <http://www.macports.org/> Ports system for Mac OS
participants (1)
-
MacPorts