From: "Nuno Silva" <nunojsilva@ist.utl.pt>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: long compiles
Date: Tue, 12 Sep 2023 20:30:39 +0100 [thread overview]
Message-ID: <udqe53$jcg$1@ciao.gmane.io> (raw)
In-Reply-To: CAEdtorZfw823tzNc2Pi2m5=yFfCTJT2mgkiitd0FG3Zu2+-Y9g@mail.gmail.com
On 2023-09-12, Alan McKinnon wrote:
[...]
> But anyways, this is not really about how to deal with long compiles, I was
> asking what current packages take a long time after a 5 year absence.
>
> The answer is what it was always - browsers and libreoffice. I do recall
> icu being a bit of a beast back then
I remember insn-attrtab.c making the GCC compilation swap a lot :-)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=29442
--
Nuno Silva
next prev parent reply other threads:[~2023-09-12 19:28 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 [this message]
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='udqe53$jcg$1@ciao.gmane.io' \
--to=nunojsilva@ist.utl.pt \
--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