>> ./get-data-psql.at:124: pg_ctl start -w -o "-k `pwd` -h ''" >> --- /dev/null 2012-02-04 13:45:32.000000000 -0500 >> +++ >> /opt/local/var/macports/build/_Users_aeetes_dports_math_pspp-devel/pspp-devel/work/pspp-0.7.9-gb367f5/tests/testsuite.dir/at-groups/183/stderr >> 2012-02-04 13:46:32.000000000 -0500 >> @@ -0,0 +1,2 @@ >> +pg_ctl: could not start server >> +Examine the log output. >> stdout: >> waiting for server to start....LOG: could not translate service >> "/opt/local/var/macports/build/_Users_aeetes_dports_math_pspp-devel/pspp-devel/work/pspp-0.7.9-gb367f5/tests/testsuite.dir/183/.s.PGSQL.6543" >> to address: Non-recoverable failure in name resolution >> WARNING: could not create Unix-domain socket >> FATAL: no socket created for listening > > This is the crux of the problem. It couldn't create a Unix domain socket. > Quite why > I'm not sure. Is that path writable? I'm also unsure why name resolution is > involved. > > Maybe Mac doesn't support Unix-domain sockets. or perhaps there is something > special > that has to be done to create them?
Some Googling has left me at this page: http://nextmarvel.net/blog/2011/09/brew-install-postgresql-on-os-x-lion/ It seems that, perhaps, the test isn't consistently calling the same psql? There is a system-provided one, but I told ./configure to use the one from MacPorts (env PG_CONFIG). The errors we're seeing were remedied by symlinking the non-system pgsql "into place". That's not something I'm comfortable doing to a user's system, as they would then rely on my installers for updates to it. I'll see if I can't get the system version to just work for next week.
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ pspp-dev mailing list pspp-dev@gnu.org https://lists.gnu.org/mailman/listinfo/pspp-dev
