On Jul 13, 2014, at 6:04 PM, James Richard Tyrer wrote:

After continuing with several more upgrades with no success, I upgraded Glibc. I hate doing this because if it doesn't work, it is not easy to fix. But it was the answer to the problem.

Replacing Glibc should not be an issue as the versioned symbols should exist for all previous Glibc versions so that your binaries will run. However, if replacing Glibc with an older version than the system was built with, the versioned symbols will not be the newer ones the binaries require and thus you will get failures.

I've tested this multiple times but you do need to be careful depending on the version upgrade.

2.14 to 2.16 for example, not much issue

2.4 2.16 well you may run into something, but I remember upgrading the running LFS livecd from Glibc 2.4 to 2.16 and overwriting current Glibc with no issues whatsoever.

The chance of failure is minimal unless you use a patched version of Glibc which may affect things. I do build Libtirpc, as well before Linux-PAM, and that is an option dependency.

As far as disabling obsolete rpc headers with Glibc during install, I install PAM all of the time with my builds and never encounter issues because of it. The failures from Pam usually occur because I messed up a pam configuration file.



Sincerely,

William Harrington
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to