From: Martin Goodson <kaemaril@googlemail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-general@lists.postgresql.org
Subject: Re: Help? Unexpected PostgreSQL compilation failure using generic compile script
Date: Sun, 12 Mar 2023 22:01:55 +0000
Message-ID: <7000dc94-7668-3e87-ac2b-63aa3a5455ec@googlemail.com> (raw)
In-Reply-To: <1617244.1678657926@sss.pgh.pa.us>
References: <7b739123-a8d4-0f3d-4572-a5b9dbfd7c79@googlemail.com>
<1617244.1678657926@sss.pgh.pa.us>
On 12/03/2023 21:52, Tom Lane wrote:
> Martin Goodson <kaemaril@googlemail.com> writes:
>> So I simply removed the --with-gssapi, and tried again.
>> AND IT FAILED AGAIN.
>> This time it failed claiming it couldn't find the ldap library. Which is
>> most -definitely- present.
> Hard to debug this sort of thing remotely when you don't supply the exact
> error messages. But ... do you have openldap-devel installed, or just
> the base openldap package?
>
>> The compile step and make world steps work perfectly if the script is
>> run under root.
> That is odd. Permissions problems on the libraries, maybe?
>
> regards, tom lane
Hi, Tom.
Sorry, I can get the complete log tomorrow - it's on my work PC, not my
home. I clearly made insufficient notes, for which I apologize :(
Not sure about permissions on libraries. We just open up a session under
root and execute yum install <blah blah>, and that has always worked in
the past. Not sure what I'd need to check? I can perhaps ask our
friendly neighbourhood UNIX sysadmin to check those?
We did install openldap and openldap-devel, however:
yum install pam-devel
yum install libxml2-devel
yum install libxslt-devel
yum install openldap
yum install openldap-devel
yum install uuid-devel
yum install readline-devel
yum install openssl-devel
yum install libicu-devel
yum install uuid-devel
yum install gcc
yum install make
Regards,
M.
--
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."
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: kaemaril@googlemail.com, tgl@sss.pgh.pa.us
Subject: Re: Help? Unexpected PostgreSQL compilation failure using generic compile script
In-Reply-To: <7000dc94-7668-3e87-ac2b-63aa3a5455ec@googlemail.com>
References: <7b739123-a8d4-0f3d-4572-a5b9dbfd7c79@googlemail.com> <1617244.1678657926@sss.pgh.pa.us> <7000dc94-7668-3e87-ac2b-63aa3a5455ec@googlemail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox