From owner-freebsd-questions@FreeBSD.ORG Fri May 22 02:21:33 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BF83F106564A for ; Fri, 22 May 2009 02:21:33 +0000 (UTC) (envelope-from corky1951@comcast.net) Received: from QMTA03.emeryville.ca.mail.comcast.net (qmta03.emeryville.ca.mail.comcast.net [76.96.30.32]) by mx1.freebsd.org (Postfix) with ESMTP id A54268FC19 for ; Fri, 22 May 2009 02:21:33 +0000 (UTC) (envelope-from corky1951@comcast.net) Received: from OMTA08.emeryville.ca.mail.comcast.net ([76.96.30.12]) by QMTA03.emeryville.ca.mail.comcast.net with comcast id uBzH1b0030FhH24A3SMarB; Fri, 22 May 2009 02:21:34 +0000 Received: from comcast.net ([98.203.142.76]) by OMTA08.emeryville.ca.mail.comcast.net with comcast id uSMX1b00C1f6R9u8USMYZM; Fri, 22 May 2009 02:21:33 +0000 Received: by comcast.net (sSMTP sendmail emulation); Thu, 21 May 2009 19:21:30 -0700 Date: Thu, 21 May 2009 19:21:30 -0700 From: Charlie Kester To: freebsd-questions@freebsd.org Message-ID: <20090522022129.GA55071@comcast.net> Mail-Followup-To: freebsd-questions@freebsd.org, Yuri References: <4A15EB1D.2070604@rawbw.com> <20090522002606.GG49013@hal.rescomp.berkeley.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <20090522002606.GG49013@hal.rescomp.berkeley.edu> X-Mailer: Mutt 1.5.x X-Composer: VIM 7.2 User-Agent: Mutt/1.5.18 (2008-05-17) Cc: Yuri Subject: Re: Why so many ports have run-dependencies on non-system gcc versions? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 May 2009 02:21:34 -0000 On Thu 21 May 2009 at 17:26:06 PDT Chris Cowart wrote: > >gcc provides a shared library that some applications link to. Take for >example: > >ccowart dev-aux bin $ ldd sabcmd >sabcmd: > libsablot.so.70 => /usr/local/lib/libsablot.so.70 (0x2807f000) > libiconv.so.3 => /usr/local/lib/libiconv.so.3 (0x28148000) > libexpat.so.6 => /usr/local/lib/libexpat.so.6 (0x2823d000) > libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x2825d000) > libm.so.5 => /lib/libm.so.5 (0x28352000) > libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x28367000) > libc.so.7 => /lib/libc.so.7 (0x28372000) > >I can see this as being a real reason why a particular gcc needs to be >around at runtime. Look at the dynamic linking information with ldd. If >it doesn't depend on a file provided by those versions of gcc, it's >probably an inaccuracy in the port's dependency list. Here's the online documentation for libgcc, which describes what this library provides: http://gcc.gnu.org/onlinedocs/gccint/Libgcc.html Perhaps this lib should be made available as a seperate port that others could list as a dependency, rather than the full-blown compiler suite?