I did the steps from Linux-PAM once more, this time I did get the right
symlinks in /usr/lib. I realy don't understand what I did wrong, it must
have been a typo. I think I should have just taken a break a bit earlier.
Combined with changing libdir='/lib64' into libdir='/usr/lib64' in
/usr/lib64/libpam{,c,_misc}.la this solved the issue.
Thanks for pointing in the right direction.
2012/2/4 Andrew Benton <b3n...@gmail.com>
> On Sat, 4 Feb 2012 14:43:36 +0100
> Ronnie van Aarle <ronnie.van.aa...@gmail.com> wrote:
>
> > Well, I tried, and it seems my assuptions on the libdir= from
> > libpam_misc.lawas right. I did the same thing again for
> > libpam.la because libpam.so also was not found.
> >
> > However, now I ran into a new problem, and I am not sure how to fix it.
> The
> > issue now is:
> >
> > $ ls -lag /usr/lib/libpam{,misc}.so
> > lrwxrwxrwx 1 blfs 10 feb 3 13:24 /usr/lib/libpam_misc.so -> ../../lib/
> > lrwxrwxrwx 1 blfs 10 feb 3 13:24 /usr/lib/libpam.so -> ../../lib/
> >
> > It seems like both symlinks are pointing to the directory ../../lib.
> >
> > I know some basics on bash, but its still puzzling for me and far from
> > routine. I thought I might have done something wrong so I went on step
> > back, unzipped Linux-PAM again and did these steps over:
> >
> > $ make install
> > $ chmod -v 4755 /lib/security/unix_chkpwd
> >
> > I skipped the tests that had to do with *.la because these files are
> > updated with the new path and allready in place.
> >
> > $ mv -v /lib/security/pam_tally /sbin
> >
> > $ if [ -L /lib/libpam.so ]; then
> > for LINK in libpam{,c,_misc}.so; do
> > ln -v -sf ../../lib/$(readlink /lib/${LINK}) /usr/lib/${LINK} &&
> > rm -v /lib/${LINK}
> > done
> > fi
> >
> > I do have my doubts on this last if-statement for-loop, because I don't
> > realy think it does what it is supposed to do. In my situation, I am
> > building shadow from
> >
> > /sources/security/shadow-4.1.3/
> >
> > So ../../lib does not exist. I suppose that I can just drop the ../../
> > because I think the /lib/libpam{,c,_misc}.so are the files that are
> > required. While I'm writing this email I just decided that that is also
> the
> > next thing I want to try, however, I would realy appreciate some
> > confirmation from someone who has more skills and routine in bash than I
> do.
> >
> > I'm a bit afreight of deviating from the instructions from the book,
> > because in the past, with earlier attempts of installing lfs, I also
> found
> > issues that forced me to attempt solving things myself and I did end up
> > with a broken or incomplete build, which is luckily not the case this
> time.
> >
> > Besides that I'm also a bit paranoid on every package that has to do with
> > security, because in the near future I want to make another lfs build
> that
> > I want to use for website hosting, and I do need to be able to guarantee
> my
> > future users a stable service.
> >
> > This one is on a notebook, with which I want to develop and test the
> > applications and configurations that I want to deploy on the next
> > installation, a server for hosting them.
> >
> > Any assistance is realy appreciated, because I have to rely on the
> quality
> > and stability of the resulting builds in the future.
> >
>
> I'm sorry for your troubles, unfortunately I'm a bit busy at the moment
> and I won't be able to look at this for a day of two.
>
> Andy
> --
> http://linuxfromscratch.org/mailman/listinfo/blfs-support
> FAQ: http://www.linuxfromscratch.org/blfs/faq.html
> Unsubscribe: See the above information page
>
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
