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 1nHPbZ-0004N6-Tr for pgsql-bugs@arkaria.postgresql.org; Tue, 08 Feb 2022 12:28:21 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nHPbY-0004oM-NH for pgsql-bugs@arkaria.postgresql.org; Tue, 08 Feb 2022 12:28:20 +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 1nHPbY-0004oD-FF for pgsql-bugs@lists.postgresql.org; Tue, 08 Feb 2022 12:28:20 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nHPbU-0008Ha-7f for pgsql-bugs@lists.postgresql.org; Tue, 08 Feb 2022 12:28:20 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 218CS9e41176584; Tue, 8 Feb 2022 07:28:10 -0500 From: Tom Lane To: "=?utf-8?B?V2VpIFN1bg==?=" <936739278@qq.com> cc: "=?utf-8?B?cGdzcWwtYnVncw==?=" , "=?utf-8?B?aWxtYXJp?=" Subject: Re: Build error in Solaris In-reply-to: References: Comments: In-reply-to "=?utf-8?B?V2VpIFN1bg==?=" <936739278@qq.com> message dated "Tue, 08 Feb 2022 18:52:50 +0800" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1176582.1644323289.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Tue, 08 Feb 2022 07:28:09 -0500 Message-ID: <1176583.1644323289@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk "=3D?utf-8?B?V2VpIFN1bg=3D=3D?=3D" <936739278@qq.com> writes: > When I built the latest code for branch REL_10_STABLE on the Solairs, = > the following error occurred: > ------------------------------------------------------ > "plperl.c", line 669: syntax error before or at: if > "plperl.c", line 669: undefined symbol: _sv > "plperl.c", line 669: left operand of "->" must be pointer to struct/= union > "plperl.c", line 669: warning: improper pointer/integer combination: arg= #2 > "plperl.c", line 669: syntax error before or at: else > "plperl.c", line 670: warning: statement not reached > "plperl.c", line 678: cannot recover from previous errors > cc: acomp failed for plperl.c > gmake: *** [plperl.o] Error 2 > ------------------------------------------------------ Hm. I saw something similar on my old dinosaur pademelon, but wrote it off as "they don't care about pre-C99 compilers anymore". But now I dug into ppport.h a bit more, and I think it's actually busted for non-gcc compilers: eval_pv expands into something that tries to use STMT_START/STMT_END inside a plain parenthesized expression (via croak_sv). Maybe the bleeding edge Devel::PPPort would do better? I see Revision history for Devel-PPPort = 3.64 - 2022-02-01 * Fix: better support for STMT_START / STMT_END definition * Fix: Only use '-Wdeclaration-after-statement' if possible which if not a smoking gun is at least firearm-adjacent. regards, tom lane