public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/112422] Build process does a redundant number of checks ? Date: Tue, 07 Nov 2023 14:17:48 +0000 [thread overview] Message-ID: <bug-112422-4-voc4CwDzmZ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112422-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112422 Eric Gallager <egallager at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |egallager at gcc dot gnu.org Keywords| |build --- Comment #2 from Eric Gallager <egallager at gcc dot gnu.org> --- A lot of that's just the way that autoconf works. You'd probably have to change the upstream implementation of certain autoconf macros to fix this. Alternatively, you could also try configuring with the "-C" flag to your configure script, which should cause configure results to be cached, but that can be rather fragile, as the config.cache files can stop your build if the slightest things to change. I suppose GCC could try sharing its config.cache files more widely between its various subdirectories, but that would be somewhat risky, given that some of the things that configure checks for could change due to the whole bootstrap process (fixincludes changes the headers available, the new compiler getting built changes which compiler should be found, and what features it has, the new runtime libraries getting built change what functions are available, and so on...)
next prev parent reply other threads:[~2023-11-07 14:17 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-07 9:13 [Bug c/112422] New: " dcb314 at hotmail dot com 2023-11-07 12:15 ` [Bug bootstrap/112422] " pinskia at gcc dot gnu.org 2023-11-07 14:17 ` egallager at gcc dot gnu.org [this message] 2023-11-08 3:53 ` sjames at gcc dot gnu.org 2024-06-15 20:00 ` egallager 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-112422-4-voc4CwDzmZ@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: linkBe 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).