On 3/29/20 10:13 AM, Ken Moffat via blfs-dev wrote:
On Sat, Mar 28, 2020 at 12:48:38AM +0100, Uwe Düffert via blfs-dev wrote:
(changing the subject)
Is there any special reason we would want to upgrade llvm but not rustc?
Both are rather ugly packages with pretty long pretty similar build times,
but recent rustc versions are available way longer than the recent llvm one.
I'd even expect rustc to be easier to upgrade due to fewer stuff to test!?
When I built rustc 1.40.0, 1.41.0 and 1.41.1 I used all 8 cores. It
seemed to me that the install phase was taking a long time, but I
didn't think too much about that.
For the book, we want timings with 4 cores, so I took the siblings
offline. A manual ./x.py build took just under 56 minutes. I then
started the (DESTDIR) install - on 1.39.0 the other day, that took 8
minutes and I was surprised at how quick it seemed. With 1.42.0
that took over 57 minutes (longer than the 'build'). Total is 65
SBU, and the tests took 17 SBU.
The build of 1.42.0 using system llvm was smaller than 1.39.0 with
its shipped llvm. Oh, and while all of the build, install and test
were running (for measuring, I do tests afterwards, to see how the
space changes) from time to time the desktop was unusable, e.g. lost
a few characters when typing a mail.
Did you log the install? Is it doing a complete rebuild? What happens
if we just did
DESTDIR=${PWD}/install python3 ./x.py install
without the build. I know that the tests would not be run until after
the install. Also, do we need --exclude src/tools/miri on the install
line?
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
