On Aug 29, 2007, at 22:41, Jeff Stubbs wrote:
On Aug 29, 2007, at 5:07 PM, Daniel J. Luke wrote:
... but you're interested in it. Would you consider becoming the
maintainer?
Possibly. Right now I feel a little overwhelmed dealing with MP's
API and the complexity of trying to build the grass package. That's
actually a good sign.... <grin> If I can manage those tasks, I'd
feel more competent as a port's maintainer
One thing to do would be to check (perhaps with 'otool -L') and
see if any of the postgis binary files link against one of those
libraries or not.
otool reports that only postgresql and libiconv are dependecies.
pgsql is reported in /opt/local, but for some reason, postgis is
picking up the iconv library in /usr/lib. Even if I tweak the
configure.args directive to point to the libiconv port.
I thought I read in the MP guide, that MP sets the LDFLAGS to point
to the /opt/local/lib directory. Something must be hardwired in the
makefile or configure script. I'll dig deeper.
Slightly off topic: I like Simon's ruby script that list all the
dependencies of a port. Also Ryan had posted an graphic image of a
certain port's dependencies. Is there a MP port that can
automatically create a graphic image of a port's requirements. I
tried manually with OmniGraffle, but got bogged down in the details.
I don't think so. I create my dependency images with a PHP script I
wrote. My hope is that the MacPorts web site can eventually show each
port's dependency graph.
_______________________________________________
macports-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo/macports-users
