No source files from which to build Postgis extension

Hi there,
I've used the windows installation of postgresql 7.3.1. Found here: http://techdocs.postgresql.org/guides/InstallingOnWindows.

I wish to add the postgis extension to postgresql. Install instructions below. The problem is that i don't have the source files from which to make postGIS. So i think i've got two choices;
1. remove windows install and build postgresql and postgis the manual way (though i am a newbie and have run into difficulties this way with administrator passwords)
2. keep the windows install, make postgresql in a temporary area, build postgis and configure it to work with the windows install: "./configure --enable-multibyte --with-CXX --prefix=/usr --sysconfdir=/etc --docdir=/usr/doc/postgresql-$version"

It's my first posting to the pgsql-cygwin mailing list, so I just want to say hello. My reason for getting into postgresql is to run postgis as a spatial database for an internet map server using Mapserver on winXP.

Regards,
Andrew Bailey

Here's the PostGIS desired install;
> Instructions for postgis:
> Move the tar file to the 'contrib' directory of you PostgreSQL support
> tree, and de-compress it.
> cd contrib
> gunzip postgis-0.7.1.tar.gz
> tar xvf postgis-0.7.1.tar
> Change directories to the root of the PostgreSQL source tree:
> $ cd ../..
> Use the following configure arguments to configure the master makefile
> correctly, then make, but DON'T make install
> ./configure --enable-multibyte --with-CXX --prefix=/usr
> --sysconfdir=/etc --docdir=/usr/doc/postgresql-$version
> make
> Return to the PostGIS directory, and follow the standard installation
> instructions:
> make
> make install

> My windows install directory for postgresql is as follows;
> C:\Program Files\Postgresql
> bin
> data
> etc
> lib
> tmp
> usr
> var

Andrew,

On Sat, Apr 05, 2003 at 01:12:33PM +0100, Andrew Bailey wrote:
> So i think i've got two choices;
> [snip]

There is a third option. Convince the PostGIS folks to contribute their
code to the PostgreSQL contrib tree. Then the PostGIS extension would
become part of the standard Cygwin PostgreSQL package automatically:

http://cygwin.com/ml/cygwin-announce/2003-02/msg00026.html

Jason

--
PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers
Fingerprint: 7A73 1405 7F2B E669 C19D 8784 1AFD E4CC ECF4 8EF6

Jason Tishler writes:
>
> Andrew,
>
> On Sat, Apr 05, 2003 at 01:12:33PM +0100, Andrew Bailey wrote:
> > So i think i've got two choices;
> > [snip]
>
> There is a third option. Convince the PostGIS folks to contribute their
> code to the PostgreSQL contrib tree. Then the PostGIS extension would
> become part of the standard Cygwin PostgreSQL package automatically:
>
> http://cygwin.com/ml/cygwin-announce/2003-02/msg00026.html

I continue to suggest this and it may happen in the future but until then

The easiest way to get PostGIS running in Cygwin is probably just to
install the binary Cygwin PostgreSQL distribution and then add my
pre-compiled PostGIS package on top.

for a link to the binary package and the changes I had to make see
http://postgis.refractions.net/pipermail/postgis-users/2003-March/002260.htm
l

HTH

Norman

Norman,

On Mon, Apr 07, 2003 at 10:02:51AM -0400, Norman Vine wrote:
> for a link to the binary package and the changes I had to make see
> http://postgis.refractions.net/pipermail/postgis-users/2003-March/002260.html

Please submit a patch to <pgsql-patches(at)postgresql(dot)org> to add the
missing DLLIMPORT for cpu_index_tuple_cost to
src/include/optimizer/cost.h.

BTW, under 7.3.2-1, I get the following link errors:

dllwrap -o postgis.dll --dllname postgis.dll --def postgis.def postgis_debug.o postgis_ops.o postgis_fn.o postgis_inout.o postgis_proj.o postgis_chip.o postgis_transform.o postgis_gist_72.o postgis_estimate.o ../../src/utils/dllinit.o -L/usr/local/lib -L/usr/local/lib postgis_debug.o(.text+0x2e0): In function `mem_size':
/home/jt/src/postgresql-7.3.2-1/contrib/postgis/postgis_debug.c:101: undefined reference to `_pg_detoast_datum'
...

The above error is due to the dllwrap command missing the following
arguments:

-L ../../src/backend -lpostgres

I used the attached patch to the PostGIS Makefile to workaround this
"problem." Is this cockpit error on my part? Or, is the patch really
necessary?

Jason

--
PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers
Fingerprint: 7A73 1405 7F2B E669 C19D 8784 1AFD E4CC ECF4 8EF6

Jason Tishler writes:
>
> Norman,
>
> On Mon, Apr 07, 2003 at 10:02:51AM -0400, Norman Vine wrote:
> > for a link to the binary package and the changes I had to make see
> >
> http://postgis.refractions.net/pipermail/postgis-users/2003-March/
> 002260.html

Jason

Thank you for looking at this :-)
< FYI: Jason is the 'official' Cygwin PostgreSQL maintatiner >

> Please submit a patch to <pgsql-patches(at)postgresql(dot)org> to add the
> missing DLLIMPORT for cpu_index_tuple_cost to
> src/include/optimizer/cost.h.

OK, Will do

> BTW, under 7.3.2-1, I get the following link errors:
<snip>
> 1: undefined reference to `_pg_detoast_datum'
<snip>
> The above error is due to the dllwrap command missing the following
> arguments:
>
> -L ../../src/backend -lpostgres

Yes , I usually hardwire this into the Makefile

> I used the attached patch to the PostGIS Makefile to workaround this
> "problem." Is this cockpit error on my part? Or, is the patch really
> necessary?

AH... Your makefile patch is the correct solution :-)

TO PostGIS maintainers
Please apply this patch to the PostGIS makefile

Thanks

Norman

Norman,

On Tue, Apr 08, 2003 at 04:33:26PM -0400, Norman Vine wrote:
> Jason Tishler writes:
> Thank you for looking at this :-)

You are welcome.

> > Please submit a patch to <pgsql-patches(at)postgresql(dot)org> to add the
> > missing DLLIMPORT for cpu_index_tuple_cost to
> > src/include/optimizer/cost.h.
>
> OK, Will do

Thanks.

> > BTW, under 7.3.2-1, I get the following link errors:
> [snip]
> > -L ../../src/backend -lpostgres
>
> Yes , I usually hardwire this into the Makefile

Thanks for the confirmation.

> > I used the attached patch to the PostGIS Makefile to workaround this
> > "problem." Is this cockpit error on my part? Or, is the patch
> > really necessary?
>
> AH... Your makefile patch is the correct solution :-)

My patch is a workaround *not* the solution. It appears that the
following Makefile line attempted to deal with this issue:

override DLLLIBS := $(BE_DLLLIBS) $(DLLLIBS)

However, the above does not seem to work (anymore).

Additionally, my patch does not handle the Proj4 case.

> TO PostGIS maintainers Please apply this patch to the PostGIS makefile

PostGIS maintainers, please do not apply this patch as is. I'm willing
to help develop a real patch, if there is interest.

Jason

--
PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers
Fingerprint: 7A73 1405 7F2B E669 C19D 8784 1AFD E4CC ECF4 8EF6

Jason Tishler writes:
>
> > > I used the attached patch to the PostGIS Makefile to workaround this
> > > "problem." Is this cockpit error on my part? Or, is the patch
> > > really necessary?
> >
> > AH... Your makefile patch is the correct solution :-)
>
> My patch is a workaround *not* the solution. It appears that the
> following Makefile line attempted to deal with this issue:
>
> override DLLLIBS := $(BE_DLLLIBS) $(DLLLIBS)
>
> However, the above does not seem to work (anymore).

true sigh....

> Additionally, my patch does not handle the Proj4 case.
>
> > TO PostGIS maintainers Please apply this patch to the PostGIS makefile
>
> PostGIS maintainers, please do not apply this patch as is. I'm willing
> to help develop a real patch, if there is interest.

Plenty of interest !

Any help making PostGIS installation as easy and platform independent
as possible will be *appreciated* :-)

Let us know where we can help.

Thanks again

Norman