From owner-freebsd-ports@FreeBSD.ORG Thu Sep 6 15:13:24 2012 Return-Path: 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 8F3021065670 for ; Thu, 6 Sep 2012 15:13:24 +0000 (UTC) (envelope-from ale@FreeBSD.org) Received: from andxor.it (relay.andxor.it [195.223.2.3]) by mx1.freebsd.org (Postfix) with SMTP id C1F188FC16 for ; Thu, 6 Sep 2012 15:13:22 +0000 (UTC) Received: (qmail 53173 invoked from network); 6 Sep 2012 15:13:14 -0000 Received: from unknown (HELO alex.andxor.it) (192.168.2.30) by andxor.it with SMTP; 6 Sep 2012 15:13:14 -0000 Message-ID: <5048BD8A.80106@FreeBSD.org> Date: Thu, 06 Sep 2012 17:13:14 +0200 From: Alex Dupre User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:15.0) Gecko/20120905 Firefox/15.0 SeaMonkey/2.12 MIME-Version: 1.0 To: "O. Hartmann" References: <50488937.8050604@mail.zedat.fu-berlin.de> In-Reply-To: <50488937.8050604@mail.zedat.fu-berlin.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Ports FreeBSD Subject: Re: RUN_DEPENDS=: not respected? Bug? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Sep 2012 15:13:24 -0000 O. Hartmann ha scritto: > Working on a small port for OpenCL support for CPUs via "freeocl", > I run into a problem (runing FreeBSD 10.0-CURRENT). > > The port requires devel/libatomic_ops, which installs a static library > /usr/lcoal/lib/libatomic_ops.a. > > Following the instructions in the Porter's Handbook for FreeBSD, I added > a line > > RUN_DEPENDS= > ${LOCALBASE}/lib/libatomic_ops.a:${PORTSDIR}/devel/libatomic_ops It seems strange to me that a port requires a static library at runtime. You should use BUILD_DEPENDS if the library is needed to build the port. And you shouldn't put if after inclusion of bsd.port.pre.mk. RUN_DEPENDS is for things required at runtime and so usually installed in the install step. -- Alex Dupre