Date: Sat, 6 Feb 1999 00:50:36 +0000 (GMT) From: Terry Lambert <tlambert@primenet.com> To: jdp@polstra.com (John Polstra) Cc: kaleb@ics.com, hackers@FreeBSD.ORG Subject: Re: ldconfig and libraries Message-ID: <199902060050.RAA21166@usr02.primenet.com> In-Reply-To: <199902041920.LAA19846@vashon.polstra.com> from "John Polstra" at Feb 4, 99 11:20:04 am
next in thread | previous in thread | raw e-mail | index | archive | help
> Not at all. On the contrary, you're the fellow demanding that > "ldconfig must die" and then looking to the FreeBSD development team > to make the change (against the loudly expressed wishes of the vast > majority of our users) and take the heat for it. As an interesting side not to this, I was shot in the head by the a.out ld.so just recently. What happenend was several machines were upgraded from a.out to a stabilized version of 3.0, and some a.out programs ran, while others did not. The failure, in all cases, was an FP exception on the a.out executable being run. Attempting to ldd the binary in question also resulted in an FP exception, while on the binaries that ran, ldd ran fine. Installing the missing a.out shared libraries fixed both the ldd problem and the execution problem. Looks like a nasty bug in the a.out compatability ld.so. The problem was a bit more insidious, as well. The ldconfig that was run at the start didn't find the missing libraries (for the obvious reasons). So even when the libraries were really there, that ld.so didn't fall back to paths when it failed to find hashed data required that ldconfig be rerun. Just an interesting data point that might explain some FP exception complaints... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199902060050.RAA21166>