Re: lang/llvm15 -- Why is flang being built?

From: Dimitry Andric <>
Date: Mon, 30 Jan 2023 18:48:31 UTC
On 30 Jan 2023, at 19:37, Brooks Davis <> wrote:
> On Mon, Jan 30, 2023 at 09:17:07PM +0300, Gleb Popov wrote:
>> On Mon, Jan 30, 2023 at 7:59 PM Steve Kargl
>> <> wrote:
>>> Why does the lang/llvm15 port default to building flang
>>> (ie., the Fortran compiler)?
> In general this is because out of tree builds for llvm components are
> have been awkward over time and building it by default is the most
> sensible way to get it into packages.  I'll likely pull flang out of the
> main llvm ports at some point, but that will complicate updates and
> generally add work I'd rather not do.
> In specific, I hadn't realized the result wasn't usable after the
> frontend changes made upstream between 14 and 15.

Not mention that flang takes a tremendous amount of RAM to compile, even
for llvm standards! That's really an issue for upstream (just a few huge
cpp files seem to cause this), but it's also likely responsible for many
poudriere instances falling over. :)