public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/109051] Configure takes long time for multibuild of run-time libraries
Date: Tue, 07 Mar 2023 12:41:25 +0000 [thread overview]
Message-ID: <bug-109051-4-o9yn35a2Q5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109051-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109051
--- Comment #3 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #2)
> Are you sure it's not really stuck? Is it linking many target libs in
> parallel?
Dunno, it's slow even on a reasonably fast machine, so I can imagine it can
take hours on a slow builder. It's not linking, it's running configure
serially.
next prev parent reply other threads:[~2023-03-07 12:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 12:32 [Bug bootstrap/109051] New: " marxin at gcc dot gnu.org
2023-03-07 12:34 ` [Bug bootstrap/109051] " marxin at gcc dot gnu.org
2023-03-07 12:38 ` rguenth at gcc dot gnu.org
2023-03-07 12:41 ` marxin at gcc dot gnu.org [this message]
2023-03-07 13:30 ` schwab@linux-m68k.org
2023-03-29 23:55 ` pinskia at gcc dot gnu.org
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=bug-109051-4-o9yn35a2Q5@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).