From: Andrew Gierth <andrew@tao11.riddles.org.uk>
To: Michael Meskes <meskes@postgresql.org>
Cc: jallen@americansavingslife.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #15080: ecpg on windows doesn't define HAVE_LONG_LONG_INT
Date: Sat, 24 Feb 2018 19:09:15 +0000
Message-ID: <877er2nr8c.fsf@news-spur.riddles.org.uk> (raw)
In-Reply-To: <1519483386.2654.291.camel@postgresql.org>
References: <151935568942.1461.14623890240535309745@wrigleys.postgresql.org>
<1519483386.2654.291.camel@postgresql.org>
>>>>> "Michael" == Michael Meskes <meskes@postgresql.org> writes:
Michael> ECPG does not use pg_config.h, try making your change in
Michael> ecpg_config.h instead.
Aha.
Solution.pm has this:
if (IsNewer(
'src/interfaces/ecpg/include/ecpg_config.h',
'src/interfaces/ecpg/include/ecpg_config.h.in'))
{
print "Generating ecpg_config.h...\n";
open(my $o, '>', 'src/interfaces/ecpg/include/ecpg_config.h')
|| confess "Could not open ecpg_config.h";
print $o <<EOF;
#if (_MSC_VER > 1200)
#define HAVE_LONG_LONG_INT_64 1
#define ENABLE_THREAD_SAFETY 1
EOF
print $o "#endif\n";
close($o);
}
from which HAVE_LONG_LONG_INT seems to be suspiciously missing?
--
Andrew (irc:RhodiumToad)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: andrew@tao11.riddles.org.uk, meskes@postgresql.org, jallen@americansavingslife.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #15080: ecpg on windows doesn't define HAVE_LONG_LONG_INT
In-Reply-To: <877er2nr8c.fsf@news-spur.riddles.org.uk>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox