From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] long compiles
Date: Mon, 11 Sep 2023 21:46:54 +0200 [thread overview]
Message-ID: <CAEdtoraZKj=OhZy8qdTV+shW0VF2TfLCVZbbRCThASFUcrpbfw@mail.gmail.com> (raw)
In-Reply-To: <c283c95b-97f6-3707-a157-77d14b164a74@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1331 bytes --]
qtwebengine! yes that one took forever also. It also said my 16G of RAM was
smaller than the 16G it needed. Weird.
Anyways I enabled a swapfile and left it to run overnight
Alan
On Mon, Sep 11, 2023 at 9:31 PM Dale <rdalek1967@gmail.com> wrote:
> Alan McKinnon wrote:
>
> 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
>
>
>
> I have some software you don't likely use that takes a while but one that
> is common is qtwebengine or something. If it's not that one, it's qtweb
> something. It takes about 4 hours, sometimes 5 or so.
>
> I think the software takes longer to compile so that we will build new
> rigs. ROFL
>
> Dale
>
> :-) :-)
>
--
Alan McKinnon
alan dot mckinnon at gmail dot com
[-- Attachment #2: Type: text/html, Size: 2474 bytes --]
next prev parent reply other threads:[~2023-09-11 19:47 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 [this message]
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 ` [gentoo-user] " Kristian Poul Herkild
2023-09-13 21:20 ` [gentoo-user] " 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='CAEdtoraZKj=OhZy8qdTV+shW0VF2TfLCVZbbRCThASFUcrpbfw@mail.gmail.com' \
--to=alan.mckinnon@gmail.com \
--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