eb7f25e17e
hose your system. You end up with just about everything statically linked
(except for libpam.so), which then causes all the pam users to fail.
eg: login, sshd, su etc all stop working because dlopen no longer works
because there is no libc.so in memory anymore.
gcc passes -L/usr/lib to ld. The /usr/lib/libxxx.so symlink is *not* a
compatability link. It is actually the primary link. There should be no
symlinks in /lib at all. Only /lib/libXX.so.Y.
peter@daintree[9:27pm]/usr/bin-104> file yppasswd
yppasswd: setuid ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), for FreeBSD 5.1.1, dynamically linked (uses shared libs), stripped
peter@daintree[9:27pm]/usr/bin-105> ldd yppasswd
yppasswd:
libpam.so.2 => /usr/lib/libpam.so.2 (0x280d1000)
peter@daintree[9:28pm]/usr/bin-106>
Note no libc.so.5. Hence libpam.so.2 has unresolved dependencies.
I believe this is also the cause of the recent buildworld failures when
pam_krb5.so references -lcrypto stuff etc and when librpcsvc.so references
des_setparity() etc.
This change could not possibly have worked, unless there are other missing
changes to the gcc configuration. It won't work with ports versions of
gcc either.
|
||
|---|---|---|
| .. | ||
| bsd.cpu.mk | ||
| bsd.dep.mk | ||
| bsd.doc.mk | ||
| bsd.files.mk | ||
| bsd.incs.mk | ||
| bsd.info.mk | ||
| bsd.init.mk | ||
| bsd.kmod.mk | ||
| bsd.lib.mk | ||
| bsd.libnames.mk | ||
| bsd.links.mk | ||
| bsd.man.mk | ||
| bsd.nls.mk | ||
| bsd.obj.mk | ||
| bsd.own.mk | ||
| bsd.port.mk | ||
| bsd.port.post.mk | ||
| bsd.port.pre.mk | ||
| bsd.port.subdir.mk | ||
| bsd.prog.mk | ||
| bsd.README | ||
| bsd.subdir.mk | ||
| bsd.sys.mk | ||
| Makefile | ||
| sys.mk | ||