<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffcc" text="#000066">
Mathieu Baudier wrote:
<blockquote
cite="midAANLkTi=Y=NfRQYQGjwVDkEZrYJBOFgoLyZQgp8_b_8kc@mail.gmail.com"
type="cite">
<pre wrap="">Hi Bill,
</pre>
<blockquote type="cite">
<pre wrap="">These are the switches I used when I built the original database:
./configure \
--with-pgsql=/usr/local/pgsql/bin/pg_config \
--with-geos=/usr/local/bin/geos-config \
--with-proj=/usr/local/ \
--with-proj-libdir=/usr/local/lib/
</pre>
</blockquote>
<pre wrap=""><!---->
The postgis spec file is here:
<a class="moz-txt-link-freetext" href="https://projects.argeo.org/elgis/svn/factory/trunk/rpmbuild/elgis/postgis/SPECS/postgis.spec">https://projects.argeo.org/elgis/svn/factory/trunk/rpmbuild/elgis/postgis/SPECS/postgis.spec</a>
The configure is at the line 78 and it doesn't indeed have many options:
%configure --with-gui
But my understanding is that the configure automatically finds its
dependencies (geos, proj, postgres) which are installed at standard
locations via RPMs (otherwise the build would not go very far I guess)
</pre>
</blockquote>
PostGS would be pretty useless without PG and GEOS, and PG needs PROJ,
so it would make sense that these would be included as the default
setting. But the docs don't say. So I explicitly set them just to be on
the safe side. But I think you're right; PostGIS must be able to find
these packages, because if the RPM doesn't specify them, I'm sure you
would have by now if it couldn't find PG. So I think we're OK on that.<br>
<br>
<blockquote
cite="midAANLkTi=Y=NfRQYQGjwVDkEZrYJBOFgoLyZQgp8_b_8kc@mail.gmail.com"
type="cite">
<pre wrap=""></pre>
<blockquote type="cite">
<pre wrap="">ERROR: aggregate public.st_union(geometry) does not exist
</pre>
</blockquote>
<pre wrap=""><!---->
I am especially surprised that such a basic function does not exist.
</pre>
</blockquote>
That's a postgres stored procedure, and the only way that gets into the
system is when you run it.So I bet there's a sript that needs t be run
first I bet we didn't "spatialize" the database yet.<br>
<blockquote
cite="midAANLkTi=Y=NfRQYQGjwVDkEZrYJBOFgoLyZQgp8_b_8kc@mail.gmail.com"
type="cite">
<pre wrap="">Maybe your problems could be due to syntax changes with PostGIS 1.5?
(just an idea)
Did you run the initializations scripts? (some file names changed)
</pre>
</blockquote>
Initialization scripts? What initialization scripts? ;-) <br>
I think I'll go look for those.<br>
<br>
Like this one:? (for restoring data after a hard upgrade)<br>
$ sh utils/postgis_restore.pl lwpostgis.sql newdb olddb.dump
> restore.log<br>
I had forgotten about these. So I'll just go back and RTFM and do what
it says.<br>
<br>
If that doesn't work, then I'll be back.<br>
<br>
Thanks Matthew!<br>
<br>
<div class="moz-signature">-- <br>
<p style="line-height: 1.15em;">
<b>Bill Thoen</b><br>
GISnet - <a href="http://www.gisnet.com/">www.gisnet.com</a><br>
1401 Walnut St., Suite C<br>
Boulder, CO 80302<br>
303-786-9961 tel<br>
303-443-4856 fax<br>
<a class="moz-txt-link-abbreviated" href="mailto:bthoen@gisnet.com">bthoen@gisnet.com</a><br>
</p>
</div>
</body>
</html>