Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1aLFhX-0007qa-CM for pgsql-hackers@arkaria.postgresql.org; Mon, 18 Jan 2016 19:42:55 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1aLFhW-0003tt-Fy for pgsql-hackers@arkaria.postgresql.org; Mon, 18 Jan 2016 19:42:54 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1aLFhV-0003tm-SO for pgsql-hackers@postgresql.org; Mon, 18 Jan 2016 19:42:53 +0000 Received: from mail-pa0-x22c.google.com ([2607:f8b0:400e:c03::22c]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1aLFhM-0008Gc-R7 for pgsql-hackers@postgresql.org; Mon, 18 Jan 2016 19:42:52 +0000 Received: by mail-pa0-x22c.google.com with SMTP id uo6so424276892pac.1 for ; Mon, 18 Jan 2016 11:42:43 -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=rb+y9l+XqxduX1PEoATsf7OBto3T/TqRqfh0UEEj+xI=; b=nvNNModf6AXdaRSvCQTYirJB9z88Pu6CoGV8eXd0gKhhm4oeLlALL7qopdhBuUI/x+ gjZUJdCNr4ZiBDvzUVST5Sm9yi66PVCZcQXcpetvSxpVZR4hDcJ0HKAO29Hwmh9DqAQr MQj/5yPPqBn+Gj6v3tdAVyU5duCQClv0LxKOAdVQ1gkpYeai/G6cpImX8iY6owHCYReJ kBwnB27lydkhA+z/4NDir8fHYkJp0jDpzhhKACSixhNH83Efm622N8Ocdo3dlenfu7uI /kB4Wz5YwB3abIbu5HNODG+qJTbIorKCst2JHwec50wFEN/wxVngN+hAQiA8eB96qFa7 NCcQ== 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=rb+y9l+XqxduX1PEoATsf7OBto3T/TqRqfh0UEEj+xI=; b=hzJzeRsHmZmmyAjrh+2QIKWzFD5X1iAGKLMN8XPFJ3cPbRqBIWg12Z7mJUGcS9FLFR iWXO+lGPl1tXWuVWt1v6ybcTiofQya9SlwhGeEorUXrBurR8b3bDTlB5OipTbkioUmBI xtBLxD9T9/EACJkR5LFrC0S4NBgCO1T+IFeV4xv/zhX757uxQ01ddK1fmPdYdeHkZxyI rncJSjC2oG4xEDPWX4jXjE0qfmp7dd5Vh+a88THGaa5tT2N6xdSH2k3ap5S8o4rp6ckP 9gIrTM+GjjIZqIk988tSuk+9RSj4V0aEamvoaG8x6jHD28cnYMxTZCAw9jm8FmL6QhO3 j5Sw== X-Gm-Message-State: ALoCoQkjbwqku4bVUKlVx8toOgV9AuyqUMDv7mJpbHkBTeBkrHPrT+RmtzKi/w1KiyLPmJ8Kdkf4wF3xH5dn24BgUxZvDrhJUw== X-Received: by 10.66.65.203 with SMTP id z11mr38951608pas.152.1453146162066; Mon, 18 Jan 2016 11:42:42 -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 fa3sm24250322pab.45.2016.01.18.11.42.41 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 18 Jan 2016 11:42:41 -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> <569D3BB6.7010201@lucee.org> Cc: "pgsql-hackers@postgresql.org" From: "Igal @ Lucee.org" Message-ID: <569D4023.3060203@lucee.org> Date: Mon, 18 Jan 2016 11:42:27 -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: <569D3BB6.7010201@lucee.org> 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 It looks like Tom is correct. I added the directory tree to an exclude list of Microsoft Security Essentials and ran `configure` without any flags and it completed successfully this time. Thank you both for your time and expertise, Igal On 1/18/2016 11:23 AM, Igal @ Lucee.org wrote: > 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