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 1msIqU-00084o-PT for pgsql-general@arkaria.postgresql.org; Wed, 01 Dec 2021 06:11:59 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1msIqS-0004na-Ix for pgsql-general@arkaria.postgresql.org; Wed, 01 Dec 2021 06:11:56 +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 1msIqR-0004nQ-FE for pgsql-general@lists.postgresql.org; Wed, 01 Dec 2021 06:11:56 +0000 Received: from out5-smtp.messagingengine.com ([66.111.4.29]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1msIqK-00039u-Dn for pgsql-general@lists.postgresql.org; Wed, 01 Dec 2021 06:11:54 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id BBBA95C006D; Wed, 1 Dec 2021 01:11:45 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Wed, 01 Dec 2021 01:11:45 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=a9gecKp5KS/uLFdctToKThEzNDV2jI6bTGyOK9wD2 I0=; b=n+5YpygeGdt9BgXAqCKU8J4+NQ4JypWNVW3McGcaq0RLzlG7wvb9vX0pl M78f41DgtFqcfBNJW/BscR7raK0kJpC0CKXCElo1D4ifC+dkObmb5Zyx5TVqCjNG Px+gbkC+swykjgmUThXa/gfLJPMlLAXh04YMcSEwJX0I6o182p14wPB6pYwUBOW5 RF9O2wk/7m+A9bA4c1503T1/FGMg6VaKQoWH0mosGJvdtDsy9Soxhp2TOzN7pm5a qWlIraq0UBwwqe1uEktjLL8AzQ53Y2d7T0uGhVzTsARJZN9yyrqQgOf10Xr52PMA jGx4cAsUuCdVIhCI4yp9Ky20cFRRw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvuddriedvgdelfecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefkffggfgfuvfhfhfgjtgfgsehtjeertddtfeejnecuhfhrohhmpefrvghtvghr ucfgihhsvghnthhrrghuthcuoehpvghtvghrrdgvihhsvghnthhrrghuthesvghnthgvrh hprhhishgvuggsrdgtohhmqeenucggtffrrghtthgvrhhnpeefjeegheetuefhveevudel ueeftdejteeiffetvdduhfdtieefgfeutedtveeggfenucevlhhushhtvghrufhiiigvpe dtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehpvghtvghrrdgvihhsvghnthhrrghuthes vghnthgvrhhprhhishgvuggsrdgtohhm X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 1 Dec 2021 01:11:44 -0500 (EST) Message-ID: <5e38102f-4463-6e9e-9256-20ec6a07e8e5@enterprisedb.com> Date: Wed, 1 Dec 2021 07:11:42 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.3.2 Subject: Re: Issues cross-compiling libpq 14.x to MacOS armv8 Content-Language: en-US To: Tom Lane , Daniel Gustafsson Cc: Vincas Dargis , pgsql-general , Magnus Hagander , Michael Paquier References: <0dc14a31-acaf-8cae-0df4-a87339b22bd9@gmail.com> <1628170.1638302387@sss.pgh.pa.us> <47B78E57-3D0F-4616-BF52-C07FA76AF0A7@yesql.se> <1633127.1638306242@sss.pgh.pa.us> From: Peter Eisentraut In-Reply-To: <1633127.1638306242@sss.pgh.pa.us> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 30.11.21 22:04, Tom Lane wrote: > Daniel Gustafsson writes: >>> On 30 Nov 2021, at 20:59, Tom Lane wrote: >>> AFAICS this is the only test in our configure script that is a hard >>> fail when cross-compiling, and I don't see a reason for it to be that. >>> We could just assume that /dev/urandom will be available --- that's no >>> worse than a lot of the other optimistic assumptions that configure >>> makes in that mode. > >> Agreed, I don't see a problem with that. I'm not terribly familiar with >> supporting cross compilation in autoconf, would a reasonable approach be to >> just remove the check altogether like the below sketch? > > It seems like a useful test when *not* cross compiling, which is most > of the time. You still don't know whether the file will exist on the system you are running this on. > (I'm a bit surprised that the AC_CHECK_FILE macro doesn't provide > an action-if-cross-compiling option, but it apparently doesn't.) Because you are only supposed to look for files that you need during the build.