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 1pcaqR-00062P-Ex for pgsql-general@arkaria.postgresql.org; Wed, 15 Mar 2023 23:47:47 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pcaqO-0007ln-Uv for pgsql-general@arkaria.postgresql.org; Wed, 15 Mar 2023 23:47:44 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pcaqO-0007le-AJ for pgsql-general@lists.postgresql.org; Wed, 15 Mar 2023 23:47:44 +0000 Received: from mail-wr1-x42f.google.com ([2a00:1450:4864:20::42f]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1pcaqJ-0002na-EJ for pgsql-general@lists.postgresql.org; Wed, 15 Mar 2023 23:47:43 +0000 Received: by mail-wr1-x42f.google.com with SMTP id l12so10495088wrm.10 for ; Wed, 15 Mar 2023 16:47:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20210112; t=1678924057; h=content-transfer-encoding:in-reply-to:from:references:to:subject :user-agent:mime-version:date:message-id:from:to:cc:subject:date :message-id:reply-to; bh=M+ZUXFHZEppEeAp0fifBs68oaBHF1uDSjoFoRZa9sws=; b=FmrEbbdu/zJ5ZpTbeOo8dLvteN34ljZTMpSt3/IdMSvAnkj7yNzC4lUq4lBNqne9lE /ZpAPXDZR+P0iSqaXwp8TB2RuycPD9Hp66I+1IsP529crkUfI2b5PJYcUz/rGEgnaIdX 8XKb1XfSULZ71NNzEEwyVBdrMen1ccaXhLvGbMzWeDInPRPy16203gEw3j0J3GFQSz8j 6fzTlLQqorItxoHtVXg73Q87O++/B1OUbFcG0mPVcqRHFrDvHnsjNSsfCP7nudurbtG9 f8HpiWt94mEP9Tccpa0RkbeU/mYuQMTl12RxWK9xN8NeWWySVQNbO6pTkBnRXBQ+0Tyw 8zfQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678924057; h=content-transfer-encoding:in-reply-to:from:references:to:subject :user-agent:mime-version:date:message-id:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=M+ZUXFHZEppEeAp0fifBs68oaBHF1uDSjoFoRZa9sws=; b=rZEzQBR3x01QScOyaaWB6pSWHpQo8l3igrv6BoOyrRcxfIH9/r5eCqHF9NdB2h+d0f x1maoCk/5QC0i54zOZ8ELFc2+vksUA1Tl3eTFNovVWzX5zHr/621UtVcHW+vI2OzDEZF /6wDwa2dii0a7U53aYTkUWzOVG0EbD1ZG6nTlTulaRiiJ7mbfdojJ9Q5U/KpN8Iy378O iIr969Gj2zlrXe+BCup4k2G7VPe+A1pCxbFIhMIDcw8oZbM6OPsyLArE7tg2DbqWydcK hC2KKOMFkrmr+5POq2zC8cjH9q89pZg9JkA6W8vDJamjZb8zTt+s2lpnK2RjMt5t2p1A 2SDw== X-Gm-Message-State: AO0yUKUEsiBZ15PbNKDKBkByPpEW6NxGR1YrWVJy4wYbdWCVAUI+vZsN cdh+lwzw08KAiCgZFn92PEFGehKW8g== X-Google-Smtp-Source: AK7set/1k59SDjOKCm7QtMd17MNTuiBoRNYW7UZOcU8O72PLedp9kGb3qMI6VI8+shazJZQjpB+aRg== X-Received: by 2002:a5d:6146:0:b0:2ce:a8f0:5e1f with SMTP id y6-20020a5d6146000000b002cea8f05e1fmr2965431wrt.71.1678924057268; Wed, 15 Mar 2023 16:47:37 -0700 (PDT) Received: from [192.168.2.3] ([5.80.192.140]) by smtp.gmail.com with ESMTPSA id k18-20020a056000005200b002c71dd1109fsm5873327wrx.47.2023.03.15.16.47.36 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 15 Mar 2023 16:47:36 -0700 (PDT) Message-ID: <3d8ed0d4-b20e-6e6f-a683-bc328e29230b@googlemail.com> Date: Wed, 15 Mar 2023 23:47:35 +0000 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.8.0 Subject: Re: Help? Unexpected PostgreSQL compilation failure using generic compile script To: Adrian Klaver , pgsql-general@lists.postgresql.org References: <7b739123-a8d4-0f3d-4572-a5b9dbfd7c79@googlemail.com> <1f4191e7-6e6f-c27a-6bcf-d74adb85fc56@aklaver.com> From: Martin Goodson In-Reply-To: <1f4191e7-6e6f-c27a-6bcf-d74adb85fc56@aklaver.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 13/03/2023 00:02, Adrian Klaver wrote: > On 3/12/23 14:43, Martin Goodson wrote: >> Hello. >> >> For reasons I won't bore you with, we compile PostgreSQL from source >> rather than use the standard packages for some of our databases. >> > > >> So a fairly basic script that has been used for years suddenly fails >> on a fairly generic RHEL 7.9 server. >> >> I am no compilation expert. Obviously. Have I mised something basic? >> As I said, we've not seen problems like this before. Could there be >> some sort of issue on the box's configuration? If it works for root >> but not our usual build user could there be a user config with our >> account? Can anyone offer any insight on what I need to check? At the >> moment it all seems somewhat ... mystifying. > > SELinux issues? > > Have you looked at the system logs to see if they shed any light? > Apologies for the delay in replying, it's been a busy week. After a spot more testing today I found the problem, and an embarrassing one it was too. Can't believe I didn't spot it earlier. One of my colleagues had earlier used our 'generic build account' to install an older version of PostgreSQL on the same server, and had set the account's PATH and LD_LIBRARY_PATH to point to that version in the .bash_profile script.  That's something we don't normally do - our 'build account' is deliberately left as a clean slate, as it were. Bit bizarre it was somehow only causing problems with the compile check on the gssapi and ldap libraries, but there you go. Feel a bit of a twit now, but definitely something I'll be explicitly checking beforehand on future compiles :( -- Martin Goodson. "Have you thought up some clever plan, Doctor?" "Yes, Jamie, I believe I have." "What're you going to do?" "Bung a rock at it."