From owner-freebsd-security@FreeBSD.ORG Mon Feb 2 16:55:07 2015 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 782F6780; Mon, 2 Feb 2015 16:55:07 +0000 (UTC) Received: from mx5.roble.com (mx5.roble.com [206.40.34.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx5.roble.com", Issuer "mx5.roble.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 669C1FBC; Mon, 2 Feb 2015 16:55:07 +0000 (UTC) Date: Mon, 2 Feb 2015 08:55:06 -0800 (PST) From: Roger Marquis To: freebsd-security@freebsd.org, freebsd-pkg@freebsd.org Subject: Re: Enumerating glibc dependencies In-Reply-To: <20150202164319.GL11558@ivaldir.etoilebsd.net> References: <20150202150721.E8553209@hub.freebsd.org> <20150202152243.GA29176@in-addr.com> <20150202164319.GL11558@ivaldir.etoilebsd.net> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Feb 2015 16:55:07 -0000 > Please note that the glibc has nothing to do with glib. Is FreeBSD glib always linked to libc (vs glibc)? # ldd /usr/local/lib/libglib* 2>/dev/null| grep libc | sort -u libc.so.7 => /lib/libc.so.7 (0x800648000) Roger