Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cYfqa-0003RY-0E for pgsql-admin@arkaria.postgresql.org; Tue, 31 Jan 2017 21:20:16 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cYfqZ-0002r6-51 for pgsql-admin@arkaria.postgresql.org; Tue, 31 Jan 2017 21:20:15 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cYfor-0000qV-IE for pgsql-admin@postgresql.org; Tue, 31 Jan 2017 21:18:29 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cYfop-0001vM-1A for pgsql-admin@postgresql.org; Tue, 31 Jan 2017 21:18:28 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id v0VLINA0019201; Tue, 31 Jan 2017 16:18:23 -0500 From: Tom Lane To: John Scalia cc: "pgsql-admin@postgresql.org" Subject: Re: building 9.6.1 with a different value for krb-srvnam In-reply-to: References: Comments: In-reply-to John Scalia message dated "Tue, 31 Jan 2017 14:19:44 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <19199.1485897503.1@sss.pgh.pa.us> Date: Tue, 31 Jan 2017 16:18:23 -0500 Message-ID: <19200.1485897503@sss.pgh.pa.us> X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org John Scalia writes: > Quick question. I just built a new edition of 9.6.1 using > --with-krb-srvnam=POSTGRES in my configure line. Everything seemed to build > properly, however, after installation, I ran pg_config and the line for > CONFIGURE shows every option I used except --with-krb-srvnam, So, I'm > wondering if the new setting actually made it in there, i.e., it did not, > or I just found a bug in pg_config. Hm, worksforme. Are you sure you're checking the right copy of pg_config? regards, tom lane -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin