Skip site navigation (1) Skip section navigation (2)

Re: Call for porting reports

From: "Kardos, Dr(dot) Andreas" <kardos(at)repas-aeg(dot)de>
To: "Peter Eisentraut" <peter_e(at)gmx(dot)net>
Cc: <hackers(at)postgresql(dot)org>, <pgsql-ports(at)postgresql(dot)org>
Subject: Re: Call for porting reports
Date: 2000-04-11 13:18:34
Message-ID: 03a701bfa3b8$71592200$ (view raw, whole thread or download thread mbox)
Lists: pgsql-ports
Thanks for clarification.

2) configure works correctly (HAVE_INET_ATON etc.). There is a inet_aton.c
in backend/port. But this one is included only in the backend tree. In
interfaces/libpq/Makefile isn't any reference to it. It should be included
into the Makefile like snprintf has been included.

3) -h doesn't help to start the postmaster. For clients I'm using -h anyway.
Should Unix domain sockets be excluded from postmaster.c as it has been done
for CYGWIN32 and QNX? In general it could be better to handle this problem
by a additional postmaster option.

Andreas Kardos

-----Urspr√ľngliche Nachricht-----
Von: Peter Eisentraut <e99re41(at)DoCS(dot)UU(dot)SE>
An: Kardos, Dr. Andreas <kardos(at)repas-aeg(dot)de>
Cc: <hackers(at)postgresql(dot)org>; <pgsql-ports(at)postgresql(dot)org>
Gesendet: Dienstag, 11. April 2000 14:39
Betreff: Re: Call for porting reports

On Tue, 11 Apr 2000, Kardos, Dr. Andreas wrote:

> 2) The link of pg_dump fails because fe-connect.c calls inet_aton(). There
> is no inet_aton() on this platform. Since the problem is not pg_dump but
> this is a general problem!

There's a configure test for inet_aton, which does the right thing on this
sparc-sun-solaris2.5.1/gcc 2.8.1 (which doesn't have it either). Perhaps
remove the config.cache before reconfiguring? *shrug*

> 3) The postmaster cannot be started:
> sun2$ postmaster -i
> FATAL: StreamServerPort: setsockopt(SO_REUSEADDR) failed: Protocol error
> /usr/local/pgsql/bin/postmaster: cannot create UNIX stream port
> Does SunOS not support Unix domain sockets? The same error appears without
> the -i option.

No kidding. I don't get this problem but the regression tests occasionally
fail with broken pipe messages, but everything goes fine when I use TCP/IP
explicitly (-h option to psql). I don't know much more about it either

Besides the Unix socket issue this platform works and all the regression
tests pass.

Peter Eisentraut                  Sernanders väg 10:115
peter_e(at)gmx(dot)net                   75262 Uppsala            Sweden

In response to

pgsql-ports by date

Next:From: Kardos, Dr. AndreasDate: 2000-04-11 15:53:39
Subject: Re: setsockopt(SO_REUSEADDR) (Re: Call for porting reports)
Previous:From: Peter EisentrautDate: 2000-04-11 12:39:14
Subject: Re: Call for porting reports

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group