From owner-freebsd-bugs Tue Oct 22 22:27:46 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA12693 for bugs-outgoing; Tue, 22 Oct 1996 22:27:46 -0700 (PDT) Received: from scruz.net (nic.scruz.net [165.227.1.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA12675; Tue, 22 Oct 1996 22:27:42 -0700 (PDT) Received: from osprey.grizzly.com by scruz.net (8.7.3/1.34) id WAA10321; Tue, 22 Oct 1996 22:27:39 -0700 (PDT) Received: (from markd@localhost) by osprey.grizzly.com (8.7.6/8.7.3) id WAA05385; Tue, 22 Oct 1996 22:28:12 -0700 (PDT) Date: Tue, 22 Oct 1996 22:28:12 -0700 (PDT) Message-Id: <199610230528.WAA05385@osprey.grizzly.com> From: Mark Diekhans To: jdp@freefall.freebsd.org CC: jdp@freefall.freebsd.org, freebsd-bugs@freefall.freebsd.org, jdp@freefall.freebsd.org In-reply-to: <199610230509.WAA09435@freefall.freebsd.org> (message from John Polstra on Tue, 22 Oct 1996 22:09:42 -0700 (PDT)) Subject: Re: bin/1869 Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi John, Confirmed, this only happens on old binaries. Thanks, Mark >Synopsis: ldd/ld.so don't print out missing libraries. > >State-Changed-From-To: open-feedback >State-Changed-By: jdp >State-Changed-When: Tue Oct 22 22:02:19 PDT 1996 >State-Changed-Why: >I need some feedback on this problem. > >I tested this on a recent -current system (from 19 October 1996), and it >works OK. I am not aware of its having been broken at any time recently. >The symptoms sound like what used to happen around 2.0.5 and possibly >even 2.1.0, but the problem was fixed since then. Part of the fix was >in crt0.o, which is linked into the executable. If you are running an >old executable, even under -current, you will see this symptom. > >Could you please confirm whether you're running a pre-2.1.5 executable >when you see this problem? And/or describe a specific test case so that >I can try to duplicate the problem. > > >Responsible-Changed-From-To: freebsd-bugs->jdp >Responsible-Changed-By: jdp >Responsible-Changed-When: Tue Oct 22 22:02:19 PDT 1996 >Responsible-Changed-Why: >Fixed this problem around 2.0.5 or 2.1.0. >