On Friday 14 June 2013 16:05:26 William Harrington wrote:
> Did you use CLFS for your build and pure 64 bit? If that's the case
> then you have no lib64 and CBLFS installs shadow and yes you need --
> libdir=/lib
I actually tried both (which both worked for shadow ) i.e. /lib and
/usr/lib; i
On Jun 14, 2013, at 9:03 AM, lux-integ wrote:
if one installs LinuxPAM-1.1.6 on an pure64-bit (non-multilib) setup
using the
blfs instructions
Did you use CLFS for your build and pure 64 bit? If that's the case
then you have no lib64 and CBLFS installs shadow and yes you need --
libdir=/
On 06/14/2013 04:03 PM, lux-integ wrote:
>
> if one installs LinuxPAM-1.1.6 on an pure64-bit (non-multilib) setup using the
> blfs instructions
> http://www.linuxfromscratch.org/blfs/view/svn/postlfs/linux-pam.html
> (i.e. no --libdir specified ) it puts the libraries in /lib64 and then shadow
> c
if one installs LinuxPAM-1.1.6 on an pure64-bit (non-multilib) setup using the
blfs instructions
http://www.linuxfromscratch.org/blfs/view/svn/postlfs/linux-pam.html
(i.e. no --libdir specified ) it puts the libraries in /lib64 and then shadow
cant find the pam-libraries
to compile linuxPAM,