From owner-freebsd-ports@FreeBSD.ORG Sun Jan 6 14:24:24 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 923A2DA1; Sun, 6 Jan 2013 14:24:24 +0000 (UTC) (envelope-from erik@cederstrand.dk) Received: from csmtp3.one.com (csmtp3.one.com [91.198.169.23]) by mx1.freebsd.org (Postfix) with ESMTP id 5D3F01DF; Sun, 6 Jan 2013 14:24:24 +0000 (UTC) Received: from [192.168.1.44] (unknown [176.222.238.90]) by csmtp3.one.com (Postfix) with ESMTPA id A04F124067A3; Sun, 6 Jan 2013 14:16:05 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: LLVM 3.2: official stable port is still LLVM 3.1. Basesystem missing important LLVM pieces! From: Erik Cederstrand In-Reply-To: <50E97457.7050809@zedat.fu-berlin.de> Date: Sun, 6 Jan 2013 15:16:11 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <0900DD62-3A21-4D77-8B5B-7976ACB3921B@cederstrand.dk> References: <50E97457.7050809@zedat.fu-berlin.de> To: O. Hartmann X-Mailer: Apple Mail (2.1499) Cc: Current FreeBSD , Ports FreeBSD X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Jan 2013 14:24:24 -0000 Den 06/01/2013 kl. 13.55 skrev O. Hartmann = : > While FreeBSD's > base system already has LLVM/CLANG, it is missing some important LLVM > pieces, like llvm-config and others. llvm-config is a build dependency that spits out some lib paths that you = can just hard-code for FreeBSD. So what in "others" does your port need? I think the real problem is that LLVM and the related tools are build in = one go, so you can't easily build llvm-config and others for the base = version of LLVM. llvm-config needs shared libraries that are not = installed in base because they supposedly require a prohibitive amount = of build time. The LLVM port could be split up instead. There could be a = devel/llvm-libs port that installed the shared libs for the base LLVM, = and then a devel/llvm-config, devel/scan-build or devel/mclinker port = that depends on the former port. This might require that a larger part = of the LLVM source tree is imported into src/contrib, though. Erik