On Nov 10, 2006, at 15:52, Ryan Schmidt wrote:
MacPorts's PostgreSQL also includes a launch services item which should be able to start the server at startup. With most ports, you would install the port with the "+server" variant. This applies to e.g. mysql5 and to the old postgresql8 port. However, the newer current postgresql81 port does not offer this; instead it seems you're supposed to install the postgresql81-server port instead.
However, the php5 port variant "+postgresql" depends on the postgresql81 port, not the postgresql81-server port.
Does this work together? How did the authors of the postgresql81- server port and the +postgresql variant of the php5 port intend these options to work together?
Sorry! I remember now. The postgresql81-server port requires the postgresql81 port. The postgresql81-server port only provides the additional startup scripts to start the server. So, it should all work together nicely after all. As to your original problem report: On Nov 8, 2006, at 8:48 PM, Samuel V Green III wrote:
execute.c: In function 'ECPGstore_input': execute.c:549: warning: implicit declaration of function 'ECPGis_noind_null' execute.c: At top level: execute.c:1364: error: conflicting types for 'ECPGdo' /opt/local/include/ecpglib.h:50: error: previous declaration of 'ECPGdo' was here gnumake[4]: *** [execute.o] Error 1 gnumake[3]: *** [all] Error 2 gnumake[2]: *** [all] Error 2 gnumake[1]: *** [all] Error 2 gnumake: *** [all] Error 2
It looks like this has been reported on the mailing list before, in April 2006, with no response, as far as I can tell. http://www.opendarwin.org/pipermail/darwinports/2006-April/033319.html http://www.opendarwin.org/pipermail/darwinports/2006-April/033338.html There also seems to be a (badly-formatted) bug reported on this problem, back in February 2006. http://trac.macports.org/projects/macports/ticket/7506 The comments in the bug suggest that this problem could occur if you already have postgresql 7 installed at the time when you're trying to install postgresql8. Do you? If so, that apparently won't work, and you should remove postgresql 7 first.