On 12/1/20 3:02 PM, Tim Tassonis via blfs-dev wrote:
On 12/1/20 5:33 PM, Bruce Dubbs via blfs-dev wrote:
On 12/1/20 7:48 AM, Tim Tassonis via blfs-dev wrote:
Hi all
When re-building pam version 1.5.1, I noticed that it links against
bdb, because I had installed bdb since my last pam build.
On 12/1/20 5:33 PM, Bruce Dubbs via blfs-dev wrote:
On 12/1/20 7:48 AM, Tim Tassonis via blfs-dev wrote:
Hi all
When re-building pam version 1.5.1, I noticed that it links against
bdb, because I had installed bdb since my last pam build.
As I'm not really fond of including bdb in all insta
On 12/1/20 7:48 AM, Tim Tassonis via blfs-dev wrote:
Hi all
When re-building pam version 1.5.1, I noticed that it links against bdb,
because I had installed bdb since my last pam build.
As I'm not really fond of including bdb in all installations using pam,
I found out that by specifying
On 12/1/20 7:48 AM, Tim Tassonis via blfs-dev wrote:
Hi all
When re-building pam version 1.5.1, I noticed that it links against
bdb, because I had installed bdb since my last pam build.
As I'm not really fond of including bdb in all installations using
pam, I found out that by specifying
Hi all
When re-building pam version 1.5.1, I noticed that it links against bdb,
because I had installed bdb since my last pam build.
As I'm not really fond of including bdb in all installations using pam,
I found out that by specifying
--enable-db=no
at configure time, pam will be build
