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 1jnjgn-0001Wj-B4 for pgsql-bugs@arkaria.postgresql.org; Tue, 23 Jun 2020 14:14:17 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jnjgl-0003vd-0f for pgsql-bugs@arkaria.postgresql.org; Tue, 23 Jun 2020 14:14:15 +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 1jnjgk-0003vV-QG for pgsql-bugs@lists.postgresql.org; Tue, 23 Jun 2020 14:14:14 +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 1jnjgi-0002FB-EL for pgsql-bugs@lists.postgresql.org; Tue, 23 Jun 2020 14:14:14 +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 05NEEAUU2148683; Tue, 23 Jun 2020 10:14:10 -0400 From: Tom Lane To: Patrik Novotny cc: pgsql-bugs@lists.postgresql.org Subject: Re: PostgreSQL always uses own versions of *printf(), but does not export them In-reply-to: References: Comments: In-reply-to Patrik Novotny message dated "Tue, 23 Jun 2020 13:12:03 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2148681.1592921650.1@sss.pgh.pa.us> Date: Tue, 23 Jun 2020 10:14:10 -0400 Message-ID: <2148682.1592921650@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Patrik Novotny writes: > we came across an issue when compiling projects against PostgreSQL > version >=12, as the *printf symbols seems not to be properly > exported. Possibly that external code is failing to link with libpgport? We don't really support external code including our c.h ... but anything that insists on doing so is very likely going to need libpgport and/or libpgcommon. But TBH I'd try to get rid of the inclusion, rather than let the external code get further into bed with Postgres' internal portability hacks. We never have, and we never will, promise that c.h remains stable across PG versions. regards, tom lane