Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l18za-00010F-R5 for pgsql-bugs@arkaria.postgresql.org; Sun, 17 Jan 2021 14:25:22 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1l18z4-0002mx-Bu for pgsql-bugs@arkaria.postgresql.org; Sun, 17 Jan 2021 14:24:50 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l13Sy-00014Q-Up for pgsql-bugs@lists.postgresql.org; Sun, 17 Jan 2021 08:31:21 +0000 Received: from vimdzmsp-sfwd01.bluewin.ch ([195.186.120.131]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l13Sw-0004uC-3f for pgsql-bugs@lists.postgresql.org; Sun, 17 Jan 2021 08:31:20 +0000 Received: from RobiOne00 ([176.127.231.209]) by vimdzmsp-sfwd01.bluewin.ch Swisscom AG with ESMTPA id 13Sul1RZdcbgy13SulaMro; Sun, 17 Jan 2021 09:31:17 +0100 X-Bluewin-Spam-Analysis: v=2.4 cv=Yep4Wydf c=1 sm=1 tr=0 ts=6003f5d5 a=hfomaf6PJE2z0jEToNtRZQ==:117 a=hfomaf6PJE2z0jEToNtRZQ==:17 a=DAwyPP_o2Byb1YXLmDAA:9 a=pGLkceISAAAA:8 a=epTmVMiNAAAA:8 a=MWnZzYg04SLGaEZui80A:9 a=QEXdDO2ut3YA:10 a=yMhMjlubAAAA:8 a=SSmOFEACAAAA:8 a=RhghFF9ahjGtDfxuGTUA:9 a=vMehaeiciziEglc3:21 a=gKO2Hq4RSVkA:10 a=UiCQ7L4-1S4A:10 a=hTZeC7Yk6K0A:10 a=frz4AuCg-hUA:10 a=ndEWmUVY6Yapc0oHF_P4:22 X-Bluewin-Spam-Score: 0.00 X-FXIT-IP: IPv4[176.127.231.209] Epoch[1610872277] X-Bluewin-AuthAs: robionekenobi@bluewin.ch From: To: =?utf-8?Q?'Juan_Jos=C3=A9_Santamar=C3=ADa_Flecha'?= , "'PostgreSQL mailing lists'" References: <16825-c4f104bcebc67034@postgresql.org> In-Reply-To: Subject: RE: BUG #16825: When building on Windows, cl /? retrun 'x64' not AMD64 and the build does not create x64 environment Date: Sun, 17 Jan 2021 09:31:16 +0100 Message-ID: <000001d6ecab$1f6c43c0$5e44cb40$@bluewin.ch> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_01D6ECB3.81316F10" X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQHazpT/oVZODEpNECH28oXmsAnRQgFXOaWeqhj0WpA= Content-Language: fr-ch X-CMAE-Envelope: MS4xfN/aCi1Omwz0OTMY3fvsXYm6TerFBbyNZ+76EYjr72tnuLyupzqE5KV7/f29JwHM1mzJSuPdMhwyZC65Z5Tj2bqbzwyswgrJbFGN3+INE+xmGtNqDaT6 XeJzfB9VQDwMFE4nILzW23x3VZWivdAQ5OTWcJ3ipCGlXi5AkVaUfDQrWDI0e7BRLwUoTQdFYZNypFRaqEEimqKZ3mQ/HpVWS3uoFQ6ZhuaemKea0L7aeSiC 5gm1Jp8xBxfmCJbJqaxnxg== List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk This is a multipart message in MIME format. ------=_NextPart_000_0001_01D6ECB3.81316F10 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi, =20 Yes, I see =20 Don=E2=80=99t know why when I=E2=80=99m doing the cl /? In the Visual = Studio path of the x64 Native Command Prompt, the response contains all = the help (including the /flavor: =E2=80=A6.) =20 Once I change to the postgresql\src\tools\msvc for to build, the = =E2=80=98cl /?=E2=80=99 Only gives back 2 lines and say invalid option. =20 But I also remarked that if you pass =E2=80=98cl -?=E2=80=99, it works = correctly in both case. Do you think it is possible to change the = =E2=80=98cl /?=E2=80=99 by =E2=80=98cl -?=E2=80=99 ? =20 Thanks for your help =20 Regards Robert =20 =20 From: Juan Jos=C3=A9 Santamar=C3=ADa Flecha = =20 Sent: Saturday, January 16, 2021 10:16 PM To: robionekenobi@bluewin.ch; PostgreSQL mailing lists = Subject: Re: BUG #16825: When building on Windows, cl /? retrun 'x64' = not AMD64 and the build does not create x64 environment =20 =20 =20 On Fri, Jan 15, 2021 at 9:21 AM PG Bug reporting form < = noreply@postgresql.org> wrote: in src\tools\msvc\Solution.pm the following test is not sufficient $self->{platform} =3D ($output =3D~ /^\/favor:<.+AMD64/m) ? 'x64' : 'Win32'; because the cl /? returns: Microsoft (R) C/C++ Optimizing Compiler Version = 19.28.29336 for x64 Copyright (C) Microsoft Corporation. All rights = reserved. =20 I see no bug here, that expression is looking for the line: = "/favor: select processor to optimize for, one = of:", which is one of the first printed options. To make sure this is working in your environment, you should see = "Detected hardware platform: x64" when building. =20 Regards, =20 Juan Jos=C3=A9 Santamar=C3=ADa Flecha =20 =20 =20 ------=_NextPart_000_0001_01D6ECB3.81316F10 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable

Hi,

 

Yes, I see

 

Don=E2=80=99t know why when = I=E2=80=99m doing the cl /? In the Visual Studio path of the x64 Native = Command Prompt, the response contains all the help (including the = /flavor: =E2=80=A6.)

 

Once I change to the = postgresql\src\tools\msvc for to build, the =E2=80=98cl /?=E2=80=99 Only = gives back 2 lines and say invalid option.

 

But I also remarked that if you = pass =E2=80=98cl -?=E2=80=99, it works correctly in both case. Do you = think it is possible to change the =E2=80=98cl /?=E2=80=99 by = =E2=80=98cl -?=E2=80=99 ?

 

Thanks for your = help

 

Regards

Robert

 

 

From: Juan Jos=C3=A9 Santamar=C3=ADa Flecha = <juanjo.santamaria@gmail.com>
Sent: Saturday, January = 16, 2021 10:16 PM
To: robionekenobi@bluewin.ch; PostgreSQL = mailing lists <pgsql-bugs@lists.postgresql.org>
Subject: = Re: BUG #16825: When building on Windows, cl /? retrun 'x64' not AMD64 = and the build does not create x64 environment

 

 

 

On Fri, Jan 15, 2021 at 9:21 AM PG = Bug reporting form <noreply@postgresql.org> = wrote:


in = src\tools\msvc\Solution.pm the following test is not = sufficient
                = $self->{platform} =3D
            =       ($output =3D~ /^\/favor:<.+AMD64/m) ? 'x64' : = 'Win32';
because the cl /? returns:
        =         Microsoft (R) C/C++ Optimizing Compiler = Version 19.28.29336 for x64
            =     Copyright (C) Microsoft Corporation.  All rights = reserved.

 

I see no bug here, that = expression is looking for the line: = "/favor:<blend|AMD64|INTEL64|ATOM> select processor to = optimize for, one of:", which is one of the first printed = options.

To make sure this is working in your environment, you = should see "Detected hardware platform: x64" when = building.

 

Regards,

 

Juan Jos=C3=A9 Santamar=C3=ADa = Flecha

 

 

 

------=_NextPart_000_0001_01D6ECB3.81316F10--