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

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

Re: build error in initdb on win32


  • From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
  • To: "Magnus Hagander" <mha(at)sollentuna(dot)net>
  • Cc: "PostgreSQL Developers" <pgsql-hackers(at)postgresql(dot)org>, pgsql-hackers-win32(at)postgresql(dot)org, "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>
  • Subject: Re: build error in initdb on win32
  • Date: Sun, 10 Oct 2004 16:07:37 -0400
  • Message-id: <13145(dot)1097438857(at)sss(dot)pgh(dot)pa(dot)us>

"Magnus Hagander" <mha(at)sollentuna(dot)net> writes:
> The underlying problem is still there, though. initdb is pulling all
> these symbols in from libpq.dll, which is clearly the wrong place to get
> them... Or are they supposed to be available? If so, they should be
> added to the official API, no?

"Used by our own code" does not equate to "should be part of the
official API".

> (The problem occured when I tried to fix the problem "fix MinGW libpq to
> export only required symbols". I have a patch that fixes this problem,
> but causes these others instead)

You'd better back off a little on what you're removing.  Or forget the
whole thing; I don't really agree that the above is a bug.  libpq has
always had rather more visible symbols than are in the official API,
and there are probably people using some of them.

			regards, tom lane



Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group