Re: Re: Cygwin PostgreSQL postmaster abort problem - Mailing list pgsql-ports

From Peter Eisentraut
Subject Re: Re: Cygwin PostgreSQL postmaster abort problem
Date
Msg-id Pine.LNX.4.30.0101091858480.1538-100000@peter.localdomain
Whole thread Raw
In response to Re: Cygwin PostgreSQL postmaster abort problem  (Jason Tishler <Jason.Tishler@dothill.com>)
Responses Re: Re: Cygwin PostgreSQL postmaster abort problem
List 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@gmx.net       http://yi.org/peter-e/


pgsql-ports by date:

Previous
From: Yutaka tanida
Date:
Subject: Re: (Cygwin) postmaster shutdown problem
Next
From: Tom Lane
Date:
Subject: Re: Cygwin PostgreSQL postmaster abort problem