Date: Tue, 22 Oct 1996 22:28:12 -0700 (PDT) From: Mark Diekhans <markd@Grizzly.COM> To: jdp@freefall.freebsd.org Cc: jdp@freefall.freebsd.org, freebsd-bugs@freefall.freebsd.org, jdp@freefall.freebsd.org Subject: Re: bin/1869 Message-ID: <199610230528.WAA05385@osprey.grizzly.com> In-Reply-To: <199610230509.WAA09435@freefall.freebsd.org> (message from John Polstra on Tue, 22 Oct 1996 22:09:42 -0700 (PDT))
next in thread | previous in thread | raw e-mail | index | archive | help
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. >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199610230528.WAA05385>