After upgrading to shadow-220.127.116.11, screen complains:
screen: error while loading shared libraries: libshadow.so.0: cannot open shared object file: No such file or directory
shadow contains only these in /usr/lib:
Portage 2.0.50_pre19 (default-x86-1.4, gcc-3.3.2, glibc-2.3.3_pre20040117-r0, 2.4.20-gentoo-r8)
System uname: 2.4.20-gentoo-r8 i686 Pentium III (Coppermine)
Gentoo Base System version 18.104.22.168
CFLAGS="-march=pentium3 -O3 -pipe -fomit-frame-pointer -fprefetch-loop-arrays -ffast-math -fforce-addr -falign-functions=4 -mfpmath=sse"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/alias /var/qmail/control"
CXXFLAGS="-march=pentium3 -O3 -pipe -fomit-frame-pointer -fprefetch-loop-arrays -ffast-math -fforce-addr -falign-functions=4 -mfpmath=sse"
FEATURES="autoaddcvs ccache fixpackages sandbox sfperms userpriv usersandbox"
GENTOO_MIRRORS=" http://gentoo.oregonstate.edu http://distro.ibiblio.org/pub/linux/distributions/gentoo/distfiles"
USE="acl adns apache2 berkdb crypt curl gd gdbm gif gpm imap innodb java jpeg ldap libg++ libwww maildir memlimit ncurses nls noauthcram oss pam pdflib pg-hier pg-intdatetime pg-vacuumdelay png python readline samba slang slp spell sse ssl tcpd tiff truetype x86 xml xml2 zlib"
Anyway... I've rebuilt screen, and everything seems to fine now.... but this shouldn't have happened, I guess..
see bug 37725 for more information as to why .so went away
Hmm.. I don't really care if shadow provides a .so or an .a
All I want is my system not to be screwed up my changes like these...
This causes issues with KDE apps as well (including but not limited to kuser). For the record, this is persistent with versions of shadow both as x86, and ~x86, and likely for other arches as well.
This affects courier also.
Maybe someone could add a note to the postinst of the ebuild on the off chance that a user will actually see it.
The thing is that I might miss such a comment if I update many packages at once... maybe the comments for all packages should be displayed after all the packages got emerged... but I guess that's another problem.
spanky, comment #2 doesn't make sense to me. I don't see why libshadow.so went away. I made shadow-4.0.3-r10.ebuild which enables the shared object. It appears that my changes were reverted in the version bump.
i know aron and i was giving a link to another bug about why the .so was being added/removed
i dont really care whether .so exists or not so long as my stuff doesnt break when i upgrade
Aron, because we cannot move login, etc. Best bet is with the -fPIC fix.
ok, not going to provide libshadow.so