pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Igal @ Lucee.org <igal@lucee.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Subject: Re: Cannot find a working 64-bit integer type
Date: Mon, 18 Jan 2016 11:23:34 -0800
Message-ID: <569D3BB6.7010201@lucee.org> (raw)
In-Reply-To: <6490.1453144172@sss.pgh.pa.us>
References: <569BF49E.6030308@lucee.org>
	<569C1970.7000605@lucee.org>
	<CA+TgmoY6Y_==twHUzVAk8_EP-tYy5vdfQRUXr1s3zGcqn=WapQ@mail.gmail.com>
	<6490.1453144172@sss.pgh.pa.us>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>

On 1/18/2016 11:09 AM, Tom Lane wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>> The relevant portion of config.log seems to be this:
> I do not think configure pays attention to mere warnings for this type 
> of test. The real problem here seems to be the "permission denied" 
> errors, which to me reek of broken Windows antivirus software. (As far 
> as I'm aware, the word "broken" is redundant in that phrase.)
Thank you both for looking into this.  The only A/V-type software that I 
have running is the "Microsoft Security Essentials".
>
>> I'm a little confused as to why -Wno-cpp fixes any of that, though.
> Most likely, it's pure chance that a retry worked.  Or if it's repeatable,
> maybe no-cpp changes the compiler's file access patterns enough that
> there's no longer a false trip of the AV check.
>
> Short answer is that I wonder how much of the OP's multiple problems
> are being caused by AV bugs.
I did not make any changes other than adding the compiler flags between 
those two runs (nor afterwards).

The reason that I decided to try to add the -Wno-error flag was that I 
searched the net for the error message, and found this
thread from 4 years ago: 
http://postgresql.nabble.com/Setting-Werror-in-CFLAGS-td5118384.html -- 
which showed
a similar error message and a play of the compiler flags.

I will try to run both forms again and report whether it is repeatable.

Thanks again,


Igal



-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers



view thread (78+ messages)  latest in thread

Message-ID: <569D3BB6.7010201@lucee.org>
Permalink:  ../569D3BB6.7010201@lucee.org/
Also on:    postgresql.org/message-id/569D3BB6.7010201@lucee.org

 · 

reply

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-hackers@postgresql.org
  Cc: igal@lucee.org, tgl@sss.pgh.pa.us, robertmhaas@gmail.com
  Subject: Re: Cannot find a working 64-bit integer type
  In-Reply-To: <569D3BB6.7010201@lucee.org>

* 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