Date: Thu, 4 Sep 2003 01:36:17 -0700 From: "David O'Brien" <obrien@FreeBSD.org> To: Peter Wemm <peter@FreeBSD.org> Cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/share/mk bsd.lib.mk Message-ID: <20030904083617.GA56261@dragon.nuxi.com> In-Reply-To: <200309040429.h844TBhD058678@repoman.freebsd.org> References: <200309040429.h844TBhD058678@repoman.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Sep 03, 2003 at 09:29:11PM -0700, Peter Wemm wrote: > peter 2003/09/03 21:29:11 PDT > > FreeBSD src repository > > Modified files: > share/mk bsd.lib.mk > Log: > Emergency backout of rev 1.152. This is a 100% guaranteed way to totally > 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. GCC should have additional changes then. It is going to confuse other things to have the symlink in one directory and the real libs in another. > 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. There are other changes that cause the ports versions of gcc to be broken on -current, so that alone doesn't matter.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030904083617.GA56261>