pg.ddx.io pgsql-bugs@postgresql.org mailing list archivehelp / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Wei Sun <936739278@qq.com>
Cc: pgsql-bugs <pgsql-bugs@lists.postgresql.org>
Cc: ilmari <ilmari@ilmari.org>
Subject: Re: Build error in Solaris
Date: Tue, 08 Feb 2022 07:28:09 -0500
Message-ID: <1176583.1644323289@sss.pgh.pa.us> (raw)
In-Reply-To: <tencent_2EFCC8BA0107B6EC0F97179E019A8A43C806@qq.com>
References: <tencent_2EFCC8BA0107B6EC0F97179E019A8A43C806@qq.com>
"=?utf-8?B?V2VpIFN1bg==?=" <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
view thread (3+ messages) latest in thread
Message-ID: <1176583.1644323289@sss.pgh.pa.us> Permalink: ../1176583.1644323289@sss.pgh.pa.us/ Also on: postgresql.org/message-id/1176583.1644323289@sss.pgh.pa.us ·
reply
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Reply to all the recipients using the --to and --cc options: reply via email To: pgsql-bugs@postgresql.org Cc: tgl@sss.pgh.pa.us, 936739278@qq.com, pgsql-bugs@lists.postgresql.org, ilmari@ilmari.org Subject: Re: Build error in Solaris In-Reply-To: <1176583.1644323289@sss.pgh.pa.us> * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox