Date: Fri, 8 Nov 2002 17:05:23 -0800 From: Brooks Davis <brooks@one-eyed-alien.net> To: "M. Warner Losh" <imp@bsdimp.com> Cc: eischen@pcnet1.pcnet.com, ataraxia@cox.net, current@FreeBSD.ORG Subject: Re: [PATCH] note the __sF change in src/UPDATING Message-ID: <20021108170523.B10496@Odin.AC.HMC.Edu> In-Reply-To: <20021108.161606.79869853.imp@bsdimp.com>; from imp@bsdimp.com on Fri, Nov 08, 2002 at 04:16:06PM -0700 References: <20021108.142609.112624839.imp@bsdimp.com> <Pine.GSO.4.10.10211081806220.10745-100000@pcnet1.pcnet.com> <20021108.161606.79869853.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--SkvwRMAIpAhPCcCJ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Fri, Nov 08, 2002 at 04:16:06PM -0700, M. Warner Losh wrote:
> I'd love for there to be a way to know which binaries use __sF.
The following script run on your bin, sbin, lib, and libexec directories
does a pretty decent job of finding files that contain refrences to __sF
and listing the ports that use them (depend on portupgrade).
-- Brooks
#!/bin/sh
sym=__sF
for file in $*; do
if [ -n "`nm ${file} 2>&1 | egrep " ${sym}$"`" ]; then
echo ${file} `pkg_which $file`
fi
done
--SkvwRMAIpAhPCcCJ
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE9zF9SXY6L6fI4GtQRAouWAKCwpqUIi1XbLeNCxrywYQZTcxdo5ACggEMG
rfA9BFDqJDIu0t1NWcwo4FY=
=Tl1m
-----END PGP SIGNATURE-----
--SkvwRMAIpAhPCcCJ--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021108170523.B10496>