Red Hat Bugzilla – Bug 112717
lib64 libraries not in a default loader path
Last modified: 2007-11-30 17:10:34 EST
Description of problem:
A fresh installation of FC1 (prerelease) on x86_64 has troubles
booting into any other level but 1. The immediate reason is
that PAM libraries cannot be found but this is caused by that
that /lib64 locations, or /usr/lib64, or both, are not searched
by a loader. A workaround is to boot single, edit accordingly
/etc/ld.so.conf and rerun ldconfig. There are no troubles
after that; but one would think that "lib64" directories should
be looked at by default on that platform.
Version-Release number of selected component (if applicable):
They are looked by default, unless you install 32-bit /sbin/ldconfig.
Only 64-bit /sbin/ldconfig handles both.
rpm ATM doesn't handle arch preferences too well, so you (or the installer)
need to make sure that glibc-2.3.*.x86_64.rpm is installed after
This is (probably) because the header list doesn't have an ordering
for every package in it. Then, we fall back to calling ts.order which
makes no guarantee on how arches get ordered. Note that the exact
nevra must be the same since pkgorder is indexed by nevra instead of
just name these days. So pkgorder needs to be run once all of the
final packages which are going to be in the tree are in there, then
genhdlist with the pkgorder file.
CC'ing Justin and I'll double check the hdlist later to verify it.
It depends on when the image was downloaded. The initial preview
release had an error in which I did not add --fileorder to the
genhdlist. This has been corrected, and should appear on the newest
boot.iso for preview, and work correctly on test1 when it is released.
This should be fixed in test1 when it is released.