Re: Complier warnings on mingw gcc 4.5.0
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Magnus Hagander <magnus@hagander.net>, Alvaro Herrera <alvherre@commandprompt.com>, Itagaki Takahiro <itagaki.takahiro@gmail.com>, Hiroshi Inoue <inoue@tpf.co.jp>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2010-12-15T23:42:12Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Make the win32 putenv() override update *all* present versions of the
- 741e4ad7de9e 9.0.0 cited
-
Remove the use of the pg_auth flat file for client authentication.
- e710b65c1c56 9.0.0 cited
Andrew Dunstan <andrew@dunslane.net> writes: > Mingw code attached. Hm, where did you get this? Because it does have optreset, albeit in a gratuitously ABI-incompatible fashion: > #ifdef _BSD_SOURCE > /* > * BSD adds the non-standard `optreset' feature, for reinitialisation > * of `getopt' parsing. We support this feature, for applications which > * proclaim their BSD heritage, before including this header; however, > * to maintain portability, developers are advised to avoid it. > */ > # define optreset __mingw_optreset > > extern int optreset; > #endif However, I pulled down the allegedly current mingw source tarball from sourceforge, and what I found in it is an older version that has *not* got that change. The CVS tree there doesn't seem to have it either. So I'm disinclined to want to rely on setting _BSD_SOURCE, as I first thought might be the answer --- it looks to me like only some versions of mingw will respond to that. regards, tom lane