forked frompostgres/postgres
- Notifications
You must be signed in to change notification settings - Fork6
Commitfda3e65
committed
Fix up ecpg's configuration so it handles "long long int" in MSVC builds.
Although configure-based builds correctly define HAVE_LONG_LONG_INT whenappropriate (in both pg_config.h and ecpg_config.h), builds using the MSVCscripts failed to do so. This currently has no impact on the backend,since it uses that symbol nowhere; but it does prevent ecpg fromsupporting "long long int". Fix that.Also, adjust Solution.pm so that in the constructed ecpg_config.h file,the "#if (_MSC_VER > 1200)" covers only the LONG_LONG_INT-related#defines, not the whole file. AFAICS this was a thinko on somebody'spart: ENABLE_THREAD_SAFETY should always be defined in Windows builds,and in branches using USE_INTEGER_DATETIMES, the setting of that shouldn'tdepend on the compiler version either. If I'm wrong, I imagine thebuildfarm will say so.Per bug #15080 from Jonathan Allen; issue diagnosed by Michael Meskesand Andrew Gierth. Back-patch to all supported branches.Discussion:https://postgr.es/m/151935568942.1461.14623890240535309745@wrigleys.postgresql.org1 parentb9dac4a commitfda3e65
2 files changed
+7
-1
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
232 | 232 | | |
233 | 233 | | |
234 | 234 | | |
| 235 | + | |
| 236 | + | |
| 237 | + | |
| 238 | + | |
| 239 | + | |
235 | 240 | | |
236 | 241 | | |
237 | 242 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
426 | 426 | | |
427 | 427 | | |
428 | 428 | | |
| 429 | + | |
429 | 430 | | |
| 431 | + | |
430 | 432 | | |
431 | 433 | | |
432 | | - | |
433 | 434 | | |
434 | 435 | | |
435 | 436 | | |
| |||
0 commit comments
Comments
(0)