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 1ntf1r-0006un-Hu for pgsql-bugs@arkaria.postgresql.org; Wed, 25 May 2022 00:37:35 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1ntf1q-0002jD-0m for pgsql-bugs@arkaria.postgresql.org; Wed, 25 May 2022 00:37:34 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ntf1p-0002j4-4s for pgsql-bugs@lists.postgresql.org; Wed, 25 May 2022 00:37:33 +0000 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ntf1m-0001tt-Nq for pgsql-bugs@lists.postgresql.org; Wed, 25 May 2022 00:37:32 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 0AF555C02B7; Tue, 24 May 2022 20:37:29 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Tue, 24 May 2022 20:37:29 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= cc:cc:content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm1; t=1653439049; x=1653525449; bh=xonrr+yun/ HhFrs7q4btt/Hts77S4LTq7EzMLpJEhZ4=; b=kDgFgEIaT6DEOsJSuwT4qTRReu m7iKEVla13chV+eAQLXvEpPO+AB1urCjiKiodKJivsJWQIfg9KwQI6EXc2Pqg82r WoLkEDCUlffJPRhfwTdBOQXEtzQWQ+jfc1SzcjVgkwNyRj0WqgEp1VZO/UiaL5rW WwtolkbwU2rDLrtKnhr2Aedp5p8IZCUz5ZpKdNz/BVBFjGUAna5CXt9OB6Sdm8Y9 wCDa5fOpzovM4L/d8Rm0w4I55cxzca/ACP3jFYTch0zOxjuHdt4pynhjLg6n0nue B3+lr6+IgtuXkAzYgNeK9aoMsTVseKyjv7xExHPdKDa/jmeg7ojff3TygIAA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:date:date:feedback-id :feedback-id:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; t=1653439049; x=1653525449; bh=xonrr+yun/HhFrs7q4btt/Hts77S 4LTq7EzMLpJEhZ4=; b=mpXt7uFu8Hh3Q+A00T+fKhXklX4UQ0cR7orsYRRb8gCa DW+/w92DpoSDBif6nEtlsgpUrzT+GSKttBygMkEKYiCCavTTCHiHzp+F+zu7P0Pv h0q4FtwawChwzQQEannvQorEdHKSC6gHTB7Z8p6uTYV1SdBiBFGFRlwAh9x/8W8c R37TY5s1BVJjRsNhbq1W/rs1GwSUwgn3GjEmJ149kfzjw4lDU7dnbYBTGAub7V6X lmPYCNGt1x0ia/zIpUE/nUbyEFXoDyeXN98BiVFI1lsMtmXqXnapms8MGw+2hIUi LKxvd3eB4t29rRefPxJMWs+oi2QwC8WVss07ffYvuQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrjeeggdefiecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenfg hrlhcuvffnffculdefhedmnecujfgurhepfffhvfevuffkfhggtggujgesghdtreertddt udenucfhrhhomhepofhitghhrggvlhcurfgrqhhuihgvrhcuoehmihgthhgrvghlsehprg hquhhivghrrdighiiiqeenucggtffrrghtthgvrhhnpefghfelfedvhefgieeghedutedt jeeugfeltdehfedtfeetleelgfejgeehgffggfenucffohhmrghinhepphhoshhtghhrvg hsqhhlrdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhf rhhomhepmhhitghhrggvlhesphgrqhhuihgvrhdrgiihii X-ME-Proxy: Feedback-ID: i0fe9450f:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 24 May 2022 20:37:27 -0400 (EDT) Date: Wed, 25 May 2022 09:37:23 +0900 From: Michael Paquier To: Juan =?iso-8859-1?Q?Jos=E9_Santamar=EDa?= Flecha Cc: v-yayan8@microsoft.com, PostgreSQL mailing lists Subject: Re: BUG #17492: error MSB4126: The specified solution configuration "Release|arm64" is invalid Message-ID: References: <17492-91d0c5da777750e4@postgresql.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="z3XI19ah3g6gkVwo" Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --z3XI19ah3g6gkVwo Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, May 24, 2022 at 01:00:55PM +0200, Juan Jos=E9 Santamar=EDa Flecha w= rote: > There is an open item in the current commitfest [1] to add support for > this configuration, maybe you can contribute by reviewing it. >=20 > [1] https://commitfest.postgresql.org/38/3561/ Another thing that you may be interested in in the long-term is to contribute a buildfarm member, so as we can know in live that this configuration still works after any commits happening in the code tree, of course once the patch to add this compatibility gets merged: https://buildfarm.postgresql.org/index.html https://wiki.postgresql.org/wiki/PostgreSQL_Buildfarm_Howto I don't think that we are completely in the clear with Arm64 regarding the handling is ASLR, something visibly mandatory when compiling with MSVC in this architecture, but we could move on with considering the support as experimental, which is something Thomas Munro has mentioned on the other thread. -- Michael --z3XI19ah3g6gkVwo Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmKNekMACgkQnvQgOdby QH0JSA/+OpkdVwPqC1GAMy6oYXvBJCVZtXEGJcwShqvql7gZfcZuo2apNsXVtzx7 LKWpqOeeaF95WT0fgkIqwFj+cnDCDs2tt8JOh4QnwtDvGeu0E0ym1352IPvIxZvB YcTRvgrKaYKrHKcHFvvfkMrkyEJ5/VBexTQqwULQMJ63xvYu89+zmUSPJB73hCaN 625LuCg+7NRBbxgzpgoCPneEgKBblungwUuq1b9VCn5BhpnSOefI1LHCo6Ms/Q58 04+U0r2iUuTzQgz4tead2BRKvl4sPgbQTM8HKF8+psfBt7RW+Gt7UJU6D2LCB+zK 4e5C70QUGrr5GEniijKGJhYlc5VjC29NtrHqTNwqUSXmN2u54DU7k9MRrsYXuVvT NB82kB01ORBLJ8fw4PF2/iJ2ngSNjqM+4EXL3wTnJYvlQKDt+0WA6BjC35arwb51 PTrQCsYsZ5Ggktl7lFX928S5LA5PkspOsqsqWLFsALHnpla9KX5yAHlJcUUFaP8C qeTxMc1VYgys63hP9qFnfjDSQLRa+tI0CocadgKpiLDTfkpIfXO/352OWybSNk7d ImXNaWOq+spePeUOwzAzmKm1utrwkDrBgWn17Z5cfmlvPIyhzc8I1I4J/1RARsmT afrvYmej8HIhu3Y3IQFldjglCO3xWyhrk/GFdZ+r6IFUVv6UQ8E= =QsNj -----END PGP SIGNATURE----- --z3XI19ah3g6gkVwo--