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

Re: Re: Cygwin PostgreSQL postmaster abort problem

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Jason Tishler <Jason(dot)Tishler(at)dothill(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-ports(at)postgresql(dot)org>
Subject: Re: Re: Cygwin PostgreSQL postmaster abort problem
Date: 2001-01-09 17:59:54
Message-ID: Pine.LNX.4.30.0101091858480.1538-100000@peter.localdomain (view raw, whole thread or download thread mbox)
Lists: pgsql-ports
Jason Tishler writes:

> > Seems like that's heading in the wrong direction.  Isn't there a
> > compiler switch or something we could give to make ALL global vars be
> > automatically marked DLLIMPORT?  That's generally how it works on Unix
> > platforms (for example, on HPUX the -E linker switch makes these symbols
> > available to dynamically linked shlibs).
> There is a way and the PostgreSQL build is already taking advantage of
> it:
>     dlltool --export-all --output-def postgres.def access/SUBSYS.o ...
> However, there is a downside to the above.  Now all functions and global
> variables are exported from postgres.exe -- not just the ones that make
> sense.

That's the same across all platforms though.  "Sense" is something the
user can find out about.

> Unfortunately, the above still does not mitigate the need for marking
> global variables DLLIMPORT in their corresponding header files to
> prevent unresolved linker errors by clients of libpostgres.a.

What's the point of --export-all then?

Peter Eisentraut      peter_e(at)gmx(dot)net

In response to


pgsql-ports by date

Next:From: Tom LaneDate: 2001-01-09 18:05:13
Subject: Re: Cygwin PostgreSQL postmaster abort problem
Previous:From: Yutaka tanidaDate: 2001-01-09 15:43:21
Subject: Re: (Cygwin) postmaster shutdown problem

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