Date: Sun, 6 Jan 2013 15:16:11 +0100 From: Erik Cederstrand <erik@cederstrand.dk> To: O. Hartmann <ohartman@zedat.fu-berlin.de> Cc: Current FreeBSD <freebsd-current@FreeBSD.org>, Ports FreeBSD <freebsd-ports@freebsd.org> Subject: Re: LLVM 3.2: official stable port is still LLVM 3.1. Basesystem missing important LLVM pieces! Message-ID: <0900DD62-3A21-4D77-8B5B-7976ACB3921B@cederstrand.dk> In-Reply-To: <50E97457.7050809@zedat.fu-berlin.de> References: <50E97457.7050809@zedat.fu-berlin.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Den 06/01/2013 kl. 13.55 skrev O. Hartmann = <ohartman@zedat.fu-berlin.de>: > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0900DD62-3A21-4D77-8B5B-7976ACB3921B>