Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ebphh-0000vl-T7 for pgsql-hackers@arkaria.postgresql.org; Wed, 17 Jan 2018 15:32:41 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ebphh-0008Mc-7V for pgsql-hackers@arkaria.postgresql.org; Wed, 17 Jan 2018 15:32:41 +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_2) (envelope-from ) id 1ebphg-0008MN-Tt for pgsql-hackers@lists.postgresql.org; Wed, 17 Jan 2018 15:32:41 +0000 Received: from mx.wagner.pp.ru ([78.46.190.96]) by makus.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1ebphX-0000ea-GP for pgsql-hackers@lists.postgresql.org; Wed, 17 Jan 2018 15:32:38 +0000 Received: from fafnir.local.vm (unknown [93.174.131.141]) by mx.wagner.pp.ru (Postfix) with ESMTPSA id 8E3D9E0043 for ; Wed, 17 Jan 2018 18:32:30 +0300 (MSK) Date: Wed, 17 Jan 2018 18:32:29 +0300 From: Victor Wagner To: pgsql-hackers@lists.postgresql.org Subject: Re: master make check fails on Solaris 10 Message-ID: <20180117183229.2bbc6eb7@fafnir.local.vm> In-Reply-To: <16720.1516201657@sss.pgh.pa.us> References: <0d3a9fa264cebe1cb9966f37b7c06e86@postgrespro.ru> <20180111173938.jimybeayp2u5mmup@alap3.anarazel.de> <31a342fa6a025a8bdfc5b8b19c29d56d@postgrespro.ru> <1232.1515780057@sss.pgh.pa.us> <15299.1515867055@sss.pgh.pa.us> <18209.1516059711@sss.pgh.pa.us> <90ab676392c8f9c84431976147097cf0@postgrespro.ru> <16720.1516201657@sss.pgh.pa.us> X-Mailer: Claws Mail 3.14.1 (GTK+ 2.24.31; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Wed, 17 Jan 2018 10:07:37 -0500 Tom Lane wrote: > Marina Polyakova writes: > Yeah, I can work with this. What I propose to do is use a somewhat > stripped-down version of this test as an AC_RUN_IFELSE test normally, > but if cross-compiling, fall back to just seeing if we can link. I'd suggest to add a configure option to switch off 128-bit support (--disable-int128), especially for these cross-compile cases where link test cannot give us enough information to decide automatically. --