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 1sQyMB-00CcFf-OB for pgsql-hackers@arkaria.postgresql.org; Tue, 09 Jul 2024 00:05:20 +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 1sQyMA-00ArqN-4y for pgsql-hackers@arkaria.postgresql.org; Tue, 09 Jul 2024 00:05:18 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sQyM8-00Arp3-Aw for pgsql-hackers@lists.postgresql.org; Tue, 09 Jul 2024 00:05:17 +0000 Received: from fhigh4-smtp.messagingengine.com ([103.168.172.155]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sQyM4-00182s-Nt; Tue, 09 Jul 2024 00:05:15 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailfhigh.nyi.internal (Postfix) with ESMTP id 430FC11410DC; Mon, 8 Jul 2024 20:05:10 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Mon, 08 Jul 2024 20:05:10 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=anarazel.de; h= cc:cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:subject :subject:to:to; s=fm2; t=1720483510; x=1720569910; bh=KbKdz0/s/6 HzxVONpj647Yu9+5W1ODEUnPIiPvc7QBU=; b=d/RhnkLzMQ7ol3wfqX+2JO4vTw d+pRQJTQQSKZ6TFxZCQUYhJxnl2rLiTfNSopPxUjVGOY7KDp1osSm5GYtle+jdWH WZDxarWSZBBqgan4+gkp6ghq4R2RUTC4LRGnA4XsfZj6wO0wYmzWjP4mRmJb6aUq pOichb34b7Buu7avMYXRaEznmKuHKCtVgoLWNWnzr3GKbZEq89Iw2HHMwUaKrsWL H75fI+ySHOvir7xvVn8vbDsrYRbUDeboGau4Xs3By2DO/XLsKnU+NLkd8E8ZMvBY HcdvwoMuISiEj6PgJW2DZUXTOVFm9J6+1gizoUxKNpJsBPGYfAc9Ireatqgw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; t=1720483510; x=1720569910; bh=KbKdz0/s/6HzxVONpj647Yu9+5W1 ODEUnPIiPvc7QBU=; b=R7A5GeMroiGeUzcKJprbtVRDDBO+CQdGcGtvkm5+zFfv Y+MlmBaxt/VNgs/3Y98oQTwtWQ1tM2dWHtZS6FoJ0v/C1naKw6aaEbvDjmSiQbBZ B89HCbTQ0TnxGsIR0BhBGs6UquK/rIq2mRlXhWyuaxt8x5yzrg4fIb3GkFVc/E+q aDUmdnxjMc96EUIg1m56J7pqa+2gDh+30OLjcTeg/PN+cfH438MRG2fNX7vBk+ju L5EZpNXGz/hM9nzx/Aw7ka1yA+zeLwIoRvMPlMk9gXZRlkPxr1JLaGoAe4IxPgPP 89DJyE/v7hygY0DkMxglGhROYeJ8HZ8c4UVe+312JQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeftddrvdekgddvlecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpeffhffvvefukfhfgggtuggjsehttdertddttddvnecuhfhrohhmpeetnhgurhgv shcuhfhrvghunhguuceorghnughrvghssegrnhgrrhgriigvlhdruggvqeenucggtffrrg htthgvrhhnpedvffefvefhteevffegieetfefhtddvffejvefhueetgeeludehteevudei tedtudenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpe grnhgurhgvshesrghnrghrrgiivghlrdguvg X-ME-Proxy: Feedback-ID: id4a34324:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 8 Jul 2024 20:05:09 -0400 (EDT) Date: Mon, 8 Jul 2024 17:05:07 -0700 From: Andres Freund To: Tom Lane Cc: pgsql-hackers@postgresql.org, Stephen Frost , "Jonathan S. Katz" Subject: Re: Why do we define HAVE_GSSAPI_EXT_H? Message-ID: <20240709000507.5zn5z5ankjplgn6c@awork3.anarazel.de> References: <20240708225659.gmyqoosi7km6ysgn@awork3.anarazel.de> <1228648.1720479932@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1228648.1720479932@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, On 2024-07-08 19:05:32 -0400, Tom Lane wrote: > Andres Freund writes: > > configure/meson define HAVE_GSSAPI_EXT_H / HAVE_GSSAPI_GSSAPI_EXT_H - but > > 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" = yes ; then > AC_CHECK_HEADERS(gssapi/gssapi.h, [], > [AC_CHECK_HEADERS(gssapi.h, [], [AC_MSG_ERROR([gssapi.h header file is required for GSSAPI])])]) > AC_CHECK_HEADERS(gssapi/gssapi_ext.h, [], > [AC_CHECK_HEADERS(gssapi_ext.h, [], [AC_MSG_ERROR([gssapi_ext.h header file 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. Yep, the singular version doesn't. That's what my attached patch uses... > 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. Me neither. I think it's fine to check both, I am just suggesting not to define a pg_config.h symbol for both... Greetings, Andres Freund