[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgis-users
Subject:    Re: [postgis-users] Compiling PostGIS 1.4.0 release on Solaris 10
From:       Paul Ramsey <pramsey () cleverelephant ! ca>
Date:       2009-11-27 18:05:29
Message-ID: 30fe546d0911271005q57994b8ar8caa4ff7b5e8abd9 () mail ! gmail ! com
[Download RAW message or body]

FYI, under OpenSolaris, I can build and regress without errors.

SunOS opensolaris 5.11 snv_111b i86pc i386 i86pc Solaris

P.

On Wed, Nov 25, 2009 at 10:42 AM, Nathan Widmyer <lighthousej@gmail.com> wrote:
> Ah, thank you for clearing that up.
>
> I was going off of:
> http://postgis.refractions.net/documentation/manual-1.4/ch02.html#id2531756
>  which, respectively,
> Which is how I've always built software, test before install, so I
> didn't question the directions.
>
> I understand not conflicting with a running PostgreSQL, but is there a
> socket-only connection style like MySQL can do to connect to just that
> specific instance?
> I figured the tests were writing to a temp postgis.sql somewhere so it
> wouldn't require installing into PostgreSQL, and something like a sed
> or shell command wasn't working quite right.
> There is a shell command to call "pushd" (regress/Makefile.in), which
> doesn't exist in my user compiling PostGIS that uses bourne shell by
> default (not bourne again shell), so I didn't know if there were other
> things being called that don't exist on Solaris.
>
> I just ran make check and it failed 5 out of 42 tests, so I'll take a
> closer look at it.
>
> Thanks again for letting me know, and I'll definitely put that down as
> the thing to do.
> Nate
> _______________________________________________
> postgis-users mailing list
> postgis-users@postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users
>
_______________________________________________
postgis-users mailing list
postgis-users@postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-users

[prev in list] [next in list] [prev in thread] [next in thread]