Date: Mon, 30 Jan 2023 19:48:31 +0100 From: Dimitry Andric <dim@FreeBSD.org> To: Brooks Davis <brooks@FreeBSD.org> Cc: Gleb Popov <arrowd@freebsd.org>, sgk@troutmask.apl.washington.edu, freebsd-ports@freebsd.org Subject: Re: lang/llvm15 -- Why is flang being built? Message-ID: <5ACAB6B9-CD4C-465C-A98F-8711C4A9024B@FreeBSD.org> In-Reply-To: <Y9gOgWgQURbPeaz0@spindle.one-eyed-alien.net> References: <Y9f3QaK%2BQ/O6KlAi@troutmask.apl.washington.edu> <CALH631m=XPMsNAAkOUM446mEFLf7rRwTnkEPK8qSM0eTDOYX6Q@mail.gmail.com> <Y9gOgWgQURbPeaz0@spindle.one-eyed-alien.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 30 Jan 2023, at 19:37, Brooks Davis <brooks@FreeBSD.org> 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 >> <sgk@troutmask.apl.washington.edu> 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. :) -Dimitry
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5ACAB6B9-CD4C-465C-A98F-8711C4A9024B>