From owner-freebsd-ports@FreeBSD.ORG Mon Sep 12 19:58:42 2011 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BAF481065670; Mon, 12 Sep 2011 19:58:42 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id 803D58FC18; Mon, 12 Sep 2011 19:58:42 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:2d7d:e6bb:877a:7b03]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 58EE34AC1C; Mon, 12 Sep 2011 23:58:41 +0400 (MSD) Date: Mon, 12 Sep 2011 23:58:33 +0400 From: Lev Serebryakov Organization: FreeBSD X-Priority: 3 (Normal) Message-ID: <181642832.20110912235833@serebryakov.spb.ru> To: Doug Barton In-Reply-To: <4E6E60C7.90304@FreeBSD.org> References: <503309410.20110912205856@serebryakov.spb.ru> <865325899.20110912230621@serebryakov.spb.ru> <4E6E60C7.90304@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: ports@FreeBSD.org Subject: Re: Print +REQUIRED_BY as tree? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lev@FreeBSD.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Sep 2011 19:58:42 -0000 Hello, Doug. You wrote 12 =D1=81=D0=B5=D0=BD=D1=82=D1=8F=D0=B1=D1=80=D1=8F 2011 =D0=B3.,= 23:43:03: > It's not as easy to represent the data in the way you describe as you > might think. Something like gcc is going to have multiple entry points > in a graph, which is really hard to represent in a (sort of) > 1-dimensional structure like a tree. Forest will be Ok, too :) It seems, that root of gcc44 dependency is x264, but I'm not sure, that it is ONLY root. > I would imagine that all of the ones you compiled with it do since they > are almost certainly linked with the libgcc that comes with gcc44. [many bad words skipped]. WHY, OH, WHY libgcc is not used as static library?! It is only implementation of some intrinsics, am I right? And now gcc4 is DEPRECATED, so I need to rebuild ANY port, which is depend on it (via some wired paths, whose I cannot not easily track) to update it to gcc45?! Ouch. How could I determine which ports are directly lined with libgcc from gcc44? ldd? But x264 itself (yes, it is built with GCC44 option) is not linked to libgcc: blob# ldd /usr/local/bin/x264 /usr/local/bin/x264: libgpac.so.1 =3D> /usr/local/lib/libgpac.so.1 (0x800812000) libz.so.5 =3D> /lib/libz.so.5 (0x800be3000) libm.so.5 =3D> /lib/libm.so.5 (0x800cf8000) libthr.so.3 =3D> /lib/libthr.so.3 (0x800e18000) libc.so.7 =3D> /lib/libc.so.7 (0x800f31000) libssl.so.6 =3D> /usr/lib/libssl.so.6 (0x801172000) libcrypto.so.6 =3D> /lib/libcrypto.so.6 (0x8012c5000) libjpeg.so.11 =3D> /usr/local/lib/libjpeg.so.11 (0x801565000) libpng.so.6 =3D> /usr/local/lib/libpng.so.6 (0x80169b000) I could check all binaries and shared libs, of course, (find, xargs, ldd), but it is not what I call "user friendly" :( --=20 // Black Lion AKA Lev Serebryakov