From owner-freebsd-ports@FreeBSD.ORG  Tue Sep 13 07:49:24 2011
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 74CBA106564A
	for <freebsd-ports@FreeBSD.org>; Tue, 13 Sep 2011 07:49:24 +0000 (UTC)
	(envelope-from bf1783@googlemail.com)
Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50])
	by mx1.freebsd.org (Postfix) with ESMTP id DF4618FC1A
	for <freebsd-ports@FreeBSD.org>; Tue, 13 Sep 2011 07:49:23 +0000 (UTC)
Received: by wwe3 with SMTP id 3so302898wwe.31
	for <multiple recipients>; Tue, 13 Sep 2011 00:49:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=googlemail.com; s=gamma;
	h=mime-version:reply-to:date:message-id:subject:from:to:content-type;
	bh=EqBVV21GHuv9srQ9YrEvXArjmTNlJONdwLN8F48uy7A=;
	b=mtUSQ0wIs1yYR9iEBSjP5BskN4FpybjlG1+0ZRvX5AgJZtM9M+QaUf9VXhdaDlQnWJ
	xcG9bgyJtrBXUHcnay61q9HoPvS/H21NISy2l0H4xgZhuIHwS7KS7zknqJhEsV8QdM3/
	OzkD3IOaGPidCDcuLX0ByDrWXODMQ0L31U61s=
MIME-Version: 1.0
Received: by 10.227.11.143 with SMTP id t15mr2648276wbt.107.1315900162682;
	Tue, 13 Sep 2011 00:49:22 -0700 (PDT)
Received: by 10.180.80.234 with HTTP; Tue, 13 Sep 2011 00:49:22 -0700 (PDT)
Date: Tue, 13 Sep 2011 03:49:22 -0400
Message-ID: <CAGFTUwN8FWkKsRO5VkuPA0JYqA2w1PxX+8At4BKDzNVC4MtPSA@mail.gmail.com>
From: "b. f." <bf1783@googlemail.com>
To: Lev Serebryakov <lev@FreeBSD.org>, freebsd-ports@FreeBSD.org
Content-Type: text/plain; charset=ISO-8859-1
Cc: 
Subject: Re: USE_GCC and unnesessary RUN_DENEDS on gcc port (Was: Print
 +REQUIRED_BY as tree?)
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: bf1783@gmail.com
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Sep 2011 07:49:24 -0000

> >  For example, x264 DEPENDS on gcc, (has USE_GCC=4.4+ in Makefile),
> >  but no x264 files are linked with libgcc_s.so or other libraries from
> >  gcc44. It seems, that we need separate USE_GCC_BUILD and USE_GCC_RUN,
> >  as with PERL or PYTHON.
>   Or, maybe automate this, as now port system warns user about
> "possible network servers" -- check all installed binaries and
> libraries for linkage with non-system-gcc libraries and add "run"
> dependency. But I'm not sure it is easy to do, as it should be done
> after installation, when, I afraid, adding RUN_DEPEND at this stage
> doesn't help, so this automatic should make all depends-related work
> (+REQUIRED_BY / +CONTENT) "by hands".

The type of dependency should be established by the maintainer of the
port that relies upon gcc, or by the user who sets USE_GCC in a custom
build.  It does not seem convenient or efficient to conduct a test of
the sort you describe, and there are cases -- such as  a script
calling a gcc binary, or a binary using dlopen to load a gcc library
-- that would complicate matters. There is already a proposal to add
some more flexibility to the USE_GCC construct:

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=ports/155408

, an effort to create lighter runtime-only gcc ports, and some other
simplifications:

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=ports/160507

that will make changes like you describe less of a problem.

b.