[BUGS] postgresql bug on macosx

2006-07-16 Thread Konstantin Pavlovsky
# port install postgresql--->  Building postgresql with target allError: Target com.apple.build returned: shell command "cd"/opt/local/var/db/dports/build/_opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_dports_databases_postgresql/work/postgresql-
7.4.12"&& gnumake all" returned error 2Command output: gnumake[3]: Nothing to be done for `all'.gnumake -C access allgnumake -C common SUBSYS.ognumake[4]: `SUBSYS.o' is up to date.
gnumake -C gist SUBSYS.ognumake[4]: `SUBSYS.o' is up to date.gnumake -C hash SUBSYS.ognumake[4]: `SUBSYS.o' is up to date.gnumake -C heap SUBSYS.ognumake[4]: `SUBSYS.o' is up to date.gnumake -C index 
SUBSYS.ognumake[4]: `SUBSYS.o' is up to date.gnumake -C nbtree SUBSYS.ognumake[4]: `SUBSYS.o' is up to date.gnumake -C rtree SUBSYS.ognumake[4]: `SUBSYS.o' is up to date.gnumake -C transam SUBSYS.o
/usr/bin/gcc-4.0 -no-cpp-precomp -I/opt/local/include -fno-strict-aliasing-Wall -Wmissing-prototypes -Wmissing-declarations -I../../../../src/include-I/opt/local/include  -I/opt/local/include  -c -o xlog.o xlog.c
In file included from ../../../../src/include/storage/spin.h:50, from xlog.c:35:../../../../src/include/storage/s_lock.h:543:2: error: #error PostgreSQL doesnot have native spinlock support on this platform. To continue the compilation,
rerun configure using --disable-spinlocks. However, performance will be poor.Please report this to pgsql-bugs@postgresql.org.In file included from ../../../../src/include/storage/spin.h:50,
 from xlog.c:35:../../../../src/include/storage/s_lock.h:551: error: conflicting types for'slock_t'../../../../src/include/pg_config_os.h:11: error: previous declaration of'slock_t' was here
gnumake[4]: *** [xlog.o] Error 1gnumake[3]: *** [transam-recursive] Error 2gnumake[2]: *** [access-recursive] Error 2gnumake[1]: *** [all] Error 2gnumake: *** [all] Error 2Error: /opt/local/bin/port: Status 1 encountered during processing.
-- Best reagdsPavlovsky Konstantinskype: sir_makkintoshicq: 375428


Re: [BUGS] postgresql bug on macosx

2006-07-16 Thread Theodore Petrosky
Strange, I have had  postgresql from version 7.0 to
8.1 running just fine on OS X. The only thing I ever
have to do is to install an up to date version of
bison and readline.

What version of OS X is this. It could be a problem
with darwinports. 

Ted

--- Konstantin Pavlovsky
<[EMAIL PROTECTED]> wrote:

> # port install postgresql
> --->  Building postgresql with target all
> Error: Target com.apple.build returned: shell
> command "cd
>
"/opt/local/var/db/dports/build/_opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_dports_databases_postgresql/work/postgresql-7.4.12"
> && gnumake all" returned error 2
> Command output: gnumake[3]: Nothing to be done for
> `all'.
> gnumake -C access all
> gnumake -C common SUBSYS.o
> gnumake[4]: `SUBSYS.o' is up to date.
> gnumake -C gist SUBSYS.o
> gnumake[4]: `SUBSYS.o' is up to date.
> gnumake -C hash SUBSYS.o
> gnumake[4]: `SUBSYS.o' is up to date.
> gnumake -C heap SUBSYS.o
> gnumake[4]: `SUBSYS.o' is up to date.
> gnumake -C index SUBSYS.o
> gnumake[4]: `SUBSYS.o' is up to date.
> gnumake -C nbtree SUBSYS.o
> gnumake[4]: `SUBSYS.o' is up to date.
> gnumake -C rtree SUBSYS.o
> gnumake[4]: `SUBSYS.o' is up to date.
> gnumake -C transam SUBSYS.o
> /usr/bin/gcc-4.0 -no-cpp-precomp
> -I/opt/local/include -fno-strict-aliasing
> -Wall -Wmissing-prototypes -Wmissing-declarations
> -I../../../../src/include
> -I/opt/local/include  -I/opt/local/include  -c -o
> xlog.o xlog.c
> In file included from
> ../../../../src/include/storage/spin.h:50,
>  from xlog.c:35:
> ../../../../src/include/storage/s_lock.h:543:2:
> error: #error PostgreSQL does
> not have native spinlock support on this platform.
> To continue the compilation,
> rerun configure using --disable-spinlocks. However,
> performance will be poor.
> Please report this to [EMAIL PROTECTED]
> In file included from
> ../../../../src/include/storage/spin.h:50,
>  from xlog.c:35:
> ../../../../src/include/storage/s_lock.h:551: error:
> conflicting types for
> 'slock_t'
> ../../../../src/include/pg_config_os.h:11: error:
> previous declaration of
> 'slock_t' was here
> gnumake[4]: *** [xlog.o] Error 1
> gnumake[3]: *** [transam-recursive] Error 2
> gnumake[2]: *** [access-recursive] Error 2
> gnumake[1]: *** [all] Error 2
> gnumake: *** [all] Error 2
> 
> Error: /opt/local/bin/port: Status 1 encountered
> during processing.
> 
> 
> 
> -- 
> Best reagds
> Pavlovsky Konstantin
> skype: sir_makkintosh
> icq: 375428
> 


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
   subscribe-nomail command to [EMAIL PROTECTED] so that your
   message can get through to the mailing list cleanly


Re: [BUGS] postgresql bug on macosx

2006-07-16 Thread Tom Lane
"Konstantin Pavlovsky" <[EMAIL PROTECTED]> writes:
> Error: Target com.apple.build returned: shell command "cd
> "/opt/local/var/db/dports/build/_opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_dports_databases_postgresql/work/postgresql-7.4.12"
> && gnumake all" returned error 2

Try a newer PG version.  8.0.x is the first branch that has any hope of
working on Intel OS X (which I gather is what you got there, though you
failed to provide any info).  8.1.x is the first branch that actually
got any testing on that platform, since it didn't exist till recently.

Even in the 7.4.x branch, 7.4.12 was obsoleted two months ago because of
security problems.  darwinports seems to be having a problem keeping up
to date :-(

regards, tom lane

---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster


[BUGS] BUG #2533: PostGIS- envelope function returns wrong results

2006-07-16 Thread Vania Bogorny

The following bug has been logged online:

Bug reference:  2533
Logged by:  Vania Bogorny
Email address:  [EMAIL PROTECTED]
PostgreSQL version: 7.4
Operating system:   Windows XP
Description:PostGIS- envelope function returns wrong results
Details: 

I would like to report an error with the evelope function in PostGIS (Geos
library).

According to the OGC, two geometries may only overlap if they are both of
the same type. I performed a query in PostGIS with 2 objects one polygon and
on multi-line. using the overlaps operation with the envelope function this
query returned 71 rows. It should return zero, since polygons and lines may
cross, an not overlap. Indeed, the crosses operations returns zero rows
among this objects using the evelope function. 

Have you already presented a solution for the envelope operation or has this
problem not been reported previously.

Regards,
Vania

---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?

   http://www.postgresql.org/docs/faq


Re: [BUGS] BUG #2533: PostGIS- envelope function returns wrong results

2006-07-16 Thread Michael Fuhr
On Sun, Jul 16, 2006 at 01:11:53PM +, Vania Bogorny wrote:
> I would like to report an error with the evelope function in PostGIS (Geos
> library).

PostGIS and GEOS are separate projects from PostgreSQL.  Questions
and bug reports should go to their respective mailing lists and
bug trackers.

http://postgis.refractions.net/support/

> According to the OGC, two geometries may only overlap if they are both of
> the same type. I performed a query in PostGIS with 2 objects one polygon and
> on multi-line. using the overlaps operation with the envelope function this
> query returned 71 rows. It should return zero, since polygons and lines may
> cross, an not overlap. Indeed, the crosses operations returns zero rows
> among this objects using the evelope function. 

If you report this to the PostGIS project then please provide an
example query that demonstrates the behavior you're seeing.  The
PostGIS folks might also want to know what versions of PostGIS and
GEOS you're running.

You mention that you're using envelope() but you don't say how --
are you converting the multilinestring to a polygon with envelope()
and using that polygon as one of the parameters to overlaps()?

-- 
Michael Fuhr

---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?

   http://www.postgresql.org/docs/faq