Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 9 Feb 2022 21:48:44 +0100
From:      =?UTF-8?B?VMSzbA==?= Coosemans <tijl@FreeBSD.org>
To:        Christoph Moench-Tegeder <cmt@burggraben.net>
Cc:        Brooks Davis <brooks@freebsd.org>, ports-committers@freebsd.org, dev-commits-ports-all@freebsd.org, dev-commits-ports-main@freebsd.org
Subject:   Re: git: b00578b9b208 - main - devel/llvm13: update to 13.0.1
Message-ID:  <20220209214844.496d6cf5@FreeBSD.org>
In-Reply-To: <YgQbeJnoyMxhkqzO@elch.exwg.net>
References:  <202202080034.2180YY67045739@gitrepo.freebsd.org> <YgQbeJnoyMxhkqzO@elch.exwg.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 9 Feb 2022 20:52:24 +0100 Christoph Moench-Tegeder
<cmt@burggraben.net> wrote:
> Hi,
> 
> ## Brooks Davis (brooks@FreeBSD.org):
> 
>> Subject: git: b00578b9b208 - main - devel/llvm13: update to 13.0.1  
> 
> what's your opinion on folding devel/wasi-compiler-rt13 and
> devel/wasi-libcxx into the main llvm13 port?
> As it stands now, we have to chase the llvm updates (luckily,
> there are only a few updates) in the wasi-ports to keep firefox
> building; and we can only build firefox with the llvm for which
> we have the wasi-libcxx port.
> On the llvm side, the wasi ports are already build from the llvm
> source, and the additional install size isn't that much when
> compared to the rest of the llvm package.

An alternative would be to create separate devel/wasi-libc<version> and
devel/wasi-libcxx<version> ports for each llvm<version>.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20220209214844.496d6cf5>