FAQ
Current developers tree ports to NT directly using Cygnus tools. See
FAQ for older releases.
I'm CC'ng this into the ports mailing list...

I swore someone posted a URL to work done in this regard, using all the
Cygnus utilities for NT, but can't find the link ...
On Thu, 4 Mar 1999, Espen Harlinn wrote:

As far as I am able to determine, all attempts on porting PostgreSQL to
Windows NT have failed. This seems to be directly related to items 3 and 4
in my original mail for you. The use of shellscripts/awk/sed etc. is
probably the hardest part to get right - and is a direct result of NT not
supporting any fork-like functionality. Due to the lack of fork it's next to
impossible to build a fully working version of bash, the various seds, awks,
greps, etc. for NT all have their small faults resulting in problems with
the shellscripts/awk/sed etc.

The nice thing about perl is that the language works very well on NT, and in
this case there should be no incompatibility problems between a Unix version
and a NT version replacing the current method.

I also think that a fully functional Windows NT version of PostgreSQL will
generate more support for the system both on Linux and on Windows NT.
If you could direct me to somebody who would be willing to do the conversion
of the scripts this would be greatly appreciated.

Espen Harlinn
Senior Engineer, Software
Seamos AS
e-mail:espen.harlinn@seamos.no
-----Original Message-----
From: The Hermit Hacker
Sent: 4. mars 1999 15:23
To: Espen Harlinn
Subject: Re: How about a Windows NT port of PostgreSQL



There is currently a port of PostgreSQL to NT...you'll wnant to search the
mailing list archives, though, to find out more information...
On Thu, 4 Mar 1999, Espen Harlinn wrote:

I have been toying with the idea of creating a Windows NT port
of PostgreSQL
for some time, and I am willing to attempt to port PostgreSQL
to Windows NT.
I am well aware that this is not a trivial project, and I would need some
help and support to accomplish such a project.

As far as I have been able to determine this will require some
restructuring
of the code:

1. The use of fork.

2. Adaptation of TCP/IP to Winsock

3. The use of shellscripts/awk/sed etc. If someone would
convert this part
of the code into perl scripts I should be able
to perform the rest of the port.

4. remake of the build process - again I think perl is the tool
for job, and
I may come up with a tool which is easier to
maintain than autoconf.

Best regards

Espen Harlinn
Senior Engineer, Software
Seamos AS
e-mail:espen.harlinn@seamos.no
Marc G. Fournier
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary:
scrappy@{freebsd|postgresql}.org
Marc G. Fournier
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org


--
Bruce Momjian | http://www.op.net/~candle
maillist@candle.pha.pa.us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

Search Discussions

Discussion Posts

Previous

Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 2 of 4 | next ›
Discussion Overview
grouppgsql-ports @
categoriespostgresql
postedMar 4, '99 at 5:44p
activeMar 7, '99 at 4:53a
posts4
users4
websitepostgresql.org
irc#postgresql

People

Translate

site design / logo © 2022 Grokbase