On Mon, Mar 27, 2017 at 11:41:40AM +0200, Dimitry Andric wrote: > On 26 Mar 2017, at 23:36, Mark Millard <markmi_at_dsl-only.net> wrote: > > ... > > Also interesting was: > > > > Installed packages to be REMOVED: > > llvm40-4.0.0.r4 > > > > Number of packages to be removed: 1 > > > > The operation will free 49 GiB. > > Yes, this is big. But there is no real need to build the llvm ports > with debug information, unless you want to hack on llvm itself. Cc'ing jmd_at_ and rezny_at_. I've been watching increasing size of our LLVM packages with increasing worry. This is from my tinderbox cache: $ % env LANG=C ls -lh llvm3* -rw-r--r-- 1 root wheel 17M Jan 29 2016 llvm35-3.5.2_1.txz -rw-r--r-- 1 root wheel 18M Mar 7 2016 llvm36-3.6.2_2.txz -rw-r--r-- 1 root wheel 27M Feb 28 01:05 llvm37-3.7.1_4.txz -rw-r--r-- 1 root wheel 207M Jan 19 18:20 llvm38-3.8.1_5.txz -rw-r--r-- 1 root wheel 244M Mar 23 16:42 llvm39-3.9.1_2.txz Dimitry, do you know what had causes such a huge bump in 37 -> 38? They take lots of time to build and package. And given that llvm is indirect dependency of any X11-related port, it pessimises their build times as well (devel/libclc now requires devel/llvm40 after r437268). With 49 GiB llvm40, I guess I won't be able to build-test post as my hardware would just not be capable enough. ./danfeReceived on Thu Mar 30 2017 - 15:06:49 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:11 UTC