Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sQxQQ-00CWsc-MA for pgsql-hackers@arkaria.postgresql.org; Mon, 08 Jul 2024 23:05:38 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sQxQP-00ASFW-A8 for pgsql-hackers@arkaria.postgresql.org; Mon, 08 Jul 2024 23:05:37 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sQxQO-00ASFO-Vc for pgsql-hackers@lists.postgresql.org; Mon, 08 Jul 2024 23:05:36 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sQxQM-0016fz-3y; Mon, 08 Jul 2024 23:05:35 +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 468N5Wfq1228649; Mon, 8 Jul 2024 19:05:32 -0400 From: Tom Lane To: Andres Freund cc: pgsql-hackers@postgresql.org, Stephen Frost , "Jonathan S. Katz" Subject: Re: Why do we define HAVE_GSSAPI_EXT_H? In-reply-to: <20240708225659.gmyqoosi7km6ysgn@awork3.anarazel.de> References: <20240708225659.gmyqoosi7km6ysgn@awork3.anarazel.de> Comments: In-reply-to Andres Freund message dated "Mon, 08 Jul 2024 15:56:59 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1228647.1720479932.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Mon, 08 Jul 2024 19:05:32 -0400 Message-ID: <1228648.1720479932@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Andres Freund writes: > configure/meson define HAVE_GSSAPI_EXT_H / HAVE_GSSAPI_GSSAPI_EXT_H - bu= t > afaict we don't use those anywhere? It looks to me like it's just a byproduct of the autoconf macros we use to verify that you have a sane installation: if test "$with_gssapi" =3D yes ; then AC_CHECK_HEADERS(gssapi/gssapi.h, [], [AC_CHECK_HEADERS(gssapi.h, [], [AC_MSG_ERROR([gssapi.h header file is re= quired for GSSAPI])])]) AC_CHECK_HEADERS(gssapi/gssapi_ext.h, [], [AC_CHECK_HEADERS(gssapi_ext.h, [], [AC_MSG_ERROR([gssapi_ext.h header fi= le is required for GSSAPI])])]) fi There might be a variant of AC_CHECK_HEADERS that doesn't have the default define-a-symbol action, not sure. Maybe it's not really necessary to check both gssapi.h and gssapi_ext.h, but I'm not very familiar with all the variants of GSSAPI that are out there. regards, tom lane