Doing "emerge -pvDu world," I noticed that I needed to update e2fsprogs
and e2fsprogs-libs from 1.14.7 to 1.14.8. These are marked as unstable
versions but they should cause no problems.
Also, util-linux was listed as needing updating from 2.15.1 to 2.16.
Doing "emerge util-linux e2fsprogs-libs e2fsprogs" results in the first
two packages being built but the final package, e2fsprogs, fails. The build
log reports the following:
ERROR: sys-fs/e2fsprogs-1.41.8 failed.
Call stack:
ebuild.sh, line 49: Called src_install
environment, line 2607: Called gen_usr_ldscript '-a' 'e2p' 'ext2fs'
environment, line 1541: Called die
The specific snippet of code:
[[ -z ${tlib} ]] && die "unable to read SONAME from ${lib}";
The die message:
unable to read SONAME from libe2p.so
Now, libe2p.so is supposed to be from the package e2fsprogs-libs, but
a check of this package shows that libe2p was not built. This is probably
why the build of e2fsprogs fails.
But checking the ebuild for e2fsprogs-libs, I notice some other, more
fundamental,
changes. E2fsprogs-libs used to contain libblkid and libuuid, but these
shared libraries are now being taken from the package util-linux, which accounts
for the requirement to update all three of these packages at the same time.
Maybe the fault is with the new util-linux-2.16.
For the time being, I have reverted back to the previous versions of all
three packages.
Before I try to further investigate the problem, I want to inquire if
anyone else has successfully updated these three packages or if anyone
else has encountered this same type of build failure.
Frank Peters
