Date: Sat, 15 Feb 2020 23:10:44 +0100 From: Palle Girgensohn <girgen@FreeBSD.org> To: Konstantin Belousov <kostikbel@gmail.com> Cc: freebsd-hackers@freebsd.org, Kirill Ponomarev <kp@krion.cc> Subject: Re: Why is not llvm-config executable included? Message-ID: <F28BE55B-3E33-4B7A-AD58-8B0A0077513C@FreeBSD.org> In-Reply-To: <20200215185821.GV4808@kib.kiev.ua> References: <D1A947BC-BCD9-4BAE-9D1B-EB1B433C1452@FreeBSD.org> <20200215185821.GV4808@kib.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
> 15 feb. 2020 kl. 19:58 skrev Konstantin Belousov = <kostikbel@gmail.com>: >=20 > On Sat, Feb 15, 2020 at 07:35:29PM +0100, Palle Girgensohn wrote: >> Hi! >>=20 >> I try to build postgresql with llvm from base in 13.0-CURRENT, but = although it seems to me that llvm is indeed included in base, the = executable `llvm-config` is not. PostgreSQL's build process expects to = be able to use this to configure itself when building with llvm. >>=20 >> Any ideas how to deal with this, apart from installing devel/llbm90 = which seems a bit bonkers? >=20 > If you need llvm you must install it from ports. The fact that = /usr/bin/cc > is clang with llvm behind it is somewhat accidental. >=20 > One of the reason why llvm in base should not be used as llvm = infrastructure > is because llvm API and ABI is not stable across llvm releases, and = exposing > that would make compiler updates in stable impossible due to the = stable > branches guarantee of ABI stability. >=20 > Another reason is that we generally do not want to make base depended = on > specific on llvm or any other compiler' internals. It should stay as > (reasonably portable) C+gnu ext project. Ah, OK, makes sense. So if postgresql depends on llvm, it simply has to = depend on the port, right? Palle
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F28BE55B-3E33-4B7A-AD58-8B0A0077513C>