From: Kristian Poul Herkild <kristian@herkild.dk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] long compiles
Date: Wed, 13 Sep 2023 23:15:25 +0200 [thread overview]
Message-ID: <d1b80a4a-820d-470e-e029-80384019514e@herkild.dk> (raw)
In-Reply-To: <CAEdtorbR26rPuFNLpkab6-2i9-OsPMH5UzbMJjKVZp5VVWr2rw@mail.gmail.com>
Hi.
Nothing compares to Chromium (browser) in terms of compilation times. On
my system with 12 core threads it takes about 8 hours to compile - which
is 4 times longer than 10 years ago with 2 core threads ;)
Libreoffice takes a few hours, but less than half of chromium. Nothing
gets close to Chromium. But otherwise webkitgtk and qtwebengine are to
big ones - but still about a quarter of Chromium.
Kristian Poul Herkild
Den 11.09.2023 kl. 21.19 skrev Alan McKinnon:
> After my long time away from Gentoo, I thought perhaps some packages
> that always took ages to compile would have improved. I needed to change
> to ~amd64 anyway (dumb n00b mistake leaving it at amd64). So that's what
> I did and let emerge do it's thing.
>
> chromium has been building since 10:14, it's now 21:16 and still going
> so 9 hours at least on this machine to build a browser - almost as bad
> as openoffice at it's worst (regularly took 12 hours). Nodejs also took
> a while, but I didn't record time.
>
>
> What other packages have huge build times?
>
> --
> Alan McKinnon
> alan dot mckinnon at gmail dot com
next prev parent reply other threads:[~2023-09-13 21:15 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 19:19 [gentoo-user] long compiles Alan McKinnon
2023-09-11 19:31 ` Dale
2023-09-11 19:33 ` Siddhanth Rathod
2023-09-11 19:46 ` Alan McKinnon
2023-09-12 21:08 ` Wol
2023-09-13 11:28 ` Peter Humphrey
2023-09-13 11:50 ` Wols Lists
2023-09-13 12:38 ` Frank Steinmetzger
2023-09-13 12:41 ` Peter Humphrey
2023-09-13 15:14 ` Michael
2023-09-14 9:49 ` Peter Humphrey
2023-09-14 12:24 ` Michael
2023-09-11 19:42 ` Ramon Fischer
2023-09-11 19:46 ` Ramon Fischer
2023-09-11 20:05 ` Neil Bothwick
2023-09-11 20:21 ` Alan McKinnon
2023-09-11 21:22 ` Michael
2023-09-11 21:46 ` Alan McKinnon
2023-09-11 23:04 ` Ramon Fischer
2023-09-12 8:57 ` Alan McKinnon
2023-09-12 10:14 ` Peter Humphrey
2023-09-12 10:57 ` Jacques Montier
2023-09-12 9:26 ` [gentoo-user] " Nikos Chantziaras
2023-09-12 9:19 ` Nikos Chantziaras
2023-09-12 19:01 ` Alan McKinnon
2023-09-12 19:30 ` Nuno Silva
2023-09-12 22:11 ` Neil Bothwick
2023-09-13 21:15 ` Kristian Poul Herkild [this message]
2023-09-13 21:20 ` Grant Edwards
2023-09-13 21:37 ` Neil Bothwick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d1b80a4a-820d-470e-e029-80384019514e@herkild.dk \
--to=kristian@herkild.dk \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox