aboutsummaryrefslogtreecommitdiff
path: root/src/tutorial/funcs_new.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2017-08-17 13:15:15 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2017-08-17 13:15:15 -0400
commit4f862351d20bb1c592aa76cfa692e4e8c51b4123 (patch)
tree7ef7bdfb7a09677a8bfd5edf62fd45ea020f749e /src/tutorial/funcs_new.c
parentbd502753af5d4cc7be58a8e3fea6bc55d1e7b3a5 (diff)
downloadpostgresql-4f862351d20bb1c592aa76cfa692e4e8c51b4123.tar.gz
postgresql-4f862351d20bb1c592aa76cfa692e4e8c51b4123.zip
Further tweaks to compiler flags for PL/Perl on Windows.
It now emerges that we can only rely on Perl to tell us we must use -D_USE_32BIT_TIME_T if it's Perl 5.13.4 or later. For older versions, revert to our previous practice of assuming we need that symbol in all 32-bit Windows builds. This is not ideal, but inquiring into which compiler version Perl was built with seems far too fragile. In any case, we had not previously had complaints about these old Perl versions, so let's assume this is Good Enough. (It's still better than the situation ante commit 5a5c2feca, in that at least the effects are confined to PL/Perl rather than the whole PG build.) Back-patch to all supported versions, like 5a5c2feca and predecessors. Discussion: https://postgr.es/m/CANFyU97OVQ3+Mzfmt3MhuUm5NwPU=-FtbNH5Eb7nZL9ua8=rcA@mail.gmail.com
Diffstat (limited to 'src/tutorial/funcs_new.c')
0 files changed, 0 insertions, 0 deletions