The sequence (prior to 1.5) is actually

make
make install
make check

which might be the problem.

We can't start the DB automatically as there might be one already
running, under system privs. At least a couple of your issues are
improved in 1.5, but we leave the stable series generally along except
for bugs that break expected behavior. Your report is unpleasant, but
entirely expected, behavior.

P.

On Wed, Nov 25, 2009 at 8:10 AM, Nathan Widmyer <[email protected]> wrote:
> When I'm running "make check", the first unit tests run but the tests
> against the DB doesn't run.
>
> The line with the error says:
>
> psql:postgis.sql:52: ERROR:  could not access file "$libdir/postgis-1.4": No
> such file or directory
>
> Looking on another installation, the $libdir is filled out as Pg's lib
> directory.
>
> I did compile this before and have a working, but older, PostgreSQL/PostGIS
> server which *does* still have "$libdir/postgis-1.4" in the same place in
> the postgis.sql file I use all the time.
>
> Perhaps I'm missing doing something?  The older instructions were lost on
> how I used to get it to work, but now I'm trying to automate this better now
> with a better documented approach.
> Also, I find myself having to manually start the DB instead of the tests
> perhaps starting them for me.  Also, the tests don't drop the old db if it
> already exists (from a failed run).
>
> Thanks,
> Nate
>
> _______________________________________________
> postgis-users mailing list
> [email protected]
> http://postgis.refractions.net/mailman/listinfo/postgis-users
>
>
_______________________________________________
postgis-users mailing list
[email protected]
http://postgis.refractions.net/mailman/listinfo/postgis-users

Reply via email to