Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1aLFQU-00077x-M1 for pgsql-hackers@arkaria.postgresql.org; Mon, 18 Jan 2016 19:25:18 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1aLFQT-0001Wj-W9 for pgsql-hackers@arkaria.postgresql.org; Mon, 18 Jan 2016 19:25:18 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1aLFP6-0008Lp-NY for pgsql-hackers@postgresql.org; Mon, 18 Jan 2016 19:23:52 +0000 Received: from mail-pa0-x232.google.com ([2607:f8b0:400e:c03::232]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1aLFP3-0001iG-K4 for pgsql-hackers@postgresql.org; Mon, 18 Jan 2016 19:23:51 +0000 Received: by mail-pa0-x232.google.com with SMTP id uo6so424074474pac.1 for ; Mon, 18 Jan 2016 11:23:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lucee-org.20150623.gappssmtp.com; s=20150623; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-type:content-transfer-encoding; bh=W3jdykS4MbqWDhppedfKICgjhtM4MFqwS/J/AVNl37c=; b=DerdCBODVtkAC5cQgukE1Y1glYlGW7iVM74aVbjiJgZcw3JOzoQsz6VELZqjjmzkyl 4q9dLSpKx0cuRi2kqS4IprEdvEVFevKdhoQIN7jTxp/mjelBf1GIDa/nDk1ZBJv6vTL1 hlPUz34buCxIQ8t82WkMyStlyuIgbS//fpjuerQDkcDaQd0ihWb3b7Blk7000J0do9oJ v5Tqn0hvtQGhjpBdkb+jsVkVi+97CvkZcqU5PpLPPm5h+yxBxsuVbu8a+h5z/f0P49iq z88JV8uI2+xIsEHsLcNT5ETDdC/QZO/zQ4OB9ctthd1iM9EEroU6g3nwE34u/xD/X73h d9SA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=W3jdykS4MbqWDhppedfKICgjhtM4MFqwS/J/AVNl37c=; b=Pe7qFNAulWgYHpTiFKMm7fi8lCltgXsoSqnl563SXvxHXPnP0q9n9Ol3V38b6DipN/ NBkjJuXrnDhZpNGuz5mue8ws0jgWVczxDGubJUrCPc0WkrGqqSWmVZzxJAUUKmvm7sW8 l7HQYZyVzSiqt/sKw0X51+CW6gW3sIUf0BAZDDwPFIQZ3FymFHb7OzyECBMDSOclliNB dDabbQVV2b7FV2kxN+OIYGERhJcNEYMa7tSZ1UUegBujyzkSwU+d/gl4GHuegXyoUw5U DIOznA3YZGIbcIdn1cQla5YCjGO1U+HoExd66s7NHovRyKMGjcW1uTf5/zgit8pE8a9U inGg== X-Gm-Message-State: ALoCoQnoA+itXagt/m9Dhvd4f+Q1GAiNdzmhDfvaDcHlg0/9mFUdJgRFpGYaTVyYKjJR8hcGeE/4f1gNb5+FRbC/GJBEYAEN4g== X-Received: by 10.66.185.225 with SMTP id ff1mr38459240pac.97.1453145028401; Mon, 18 Jan 2016 11:23:48 -0800 (PST) Received: from [192.168.1.11] (cpe-108-185-131-196.socal.res.rr.com. [108.185.131.196]) by smtp.googlemail.com with ESMTPSA id ze5sm35913499pac.32.2016.01.18.11.23.47 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 18 Jan 2016 11:23:47 -0800 (PST) Subject: Re: Cannot find a working 64-bit integer type To: Tom Lane , Robert Haas References: <569BF49E.6030308@lucee.org> <569C1970.7000605@lucee.org> <6490.1453144172@sss.pgh.pa.us> Cc: "pgsql-hackers@postgresql.org" From: "Igal @ Lucee.org" Message-ID: <569D3BB6.7010201@lucee.org> Date: Mon, 18 Jan 2016 11:23:34 -0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 MIME-Version: 1.0 In-Reply-To: <6490.1453144172@sss.pgh.pa.us> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org On 1/18/2016 11:09 AM, Tom Lane wrote: > Robert Haas 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