[build2] libpq build failure
Boris Kolpackov
boris at codesynthesis.com
Tue Oct 1 13:57:39 UTC 2019
Патрушев Данил Андреевич <d.patrushev at prosoftsystems.ru> writes:
> Yes, 'ibpq\version.' exactly.
>
> //msvc
> Microsoft (R) C/C++ 19.16.27034 x64
I am suspecting this has something to do with the language
translation (which is the reason I asked for the complete
`cl` output): to handle generated headers in MSVC we have
to parse the compiler's diagnostics which gets rather hairy
with translations.
If your MSVC is indeed translated (I presume Russian), could
you run the following experiment for me:
> cd libpq-X.Y.Z\libpq
> del version.h
> cl-15 /c /Ipostgresql md5.c >compile.log
The contents of compile.log should look like this:
Microsoft (R) C/C++ Optimizing Compiler Version 19.14.26428.1 for x64
Copyright (C) Microsoft Corporation. All rights reserved.
md5.c
postgresql/pg_config.h(25): fatal error C1083: Cannot open include file: 'libpq/version.h': No such file or directory
If instead you see this diagnostics on the screen, try changing the
command line to:
> cl-15 /c /Ipostgresql md5.c 2>compile.log
Once you have compile.log with the diagnostics, can you gzip it
and email compile.log.gz to me?
> gzip compile.log
It's important that the compiler writes the diagnostics directly
to the file (rather than copy-n-pasting it from the screen) and
the file is gzip'ed (so that the email client doesn't convert it
to UTF-8 or some such) -- I need to see the exact characters as
written by the compiler.
Thanks!
More information about the users
mailing list