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/105474] GCC fails to bootstrap with --disable-libstdcxx
Date: Mon, 01 Apr 2024 16:15:20 +0000	[thread overview]
Message-ID: <bug-105474-4-0l5IudVW5E@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105474-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105474

Eric Gallager <egallager at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://gcc.gnu.org/bugzill
                   |                            |a/show_bug.cgi?id=102665
                 CC|                            |egallager at gcc dot gnu.org

--- Comment #5 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #4)
> Something like should provided an error while configuring so much earlier:
> ```
> case "$enable_bootstrap:${noconfigdirs}" in
>   yes:*target-libstdc++-v3*)
>     AC_MSG_ERROR([cannot also disable libstdcxx if bootstrapping]) ;;
>     ;;
> esac
> 
> ```
> 
> Let me test that out and submit it for GCC 15.

Related: bug 102665

      parent reply	other threads:[~2024-04-01 16:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-04  8:50 [Bug bootstrap/105474] New: " creatorsmithmdt at gmail dot com
2022-05-04  9:25 ` [Bug bootstrap/105474] " rguenth at gcc dot gnu.org
2022-05-04  9:38 ` jakub at gcc dot gnu.org
2022-12-04  6:31 ` creatorsmithmdt at gmail dot com
2024-04-01  5:21 ` pinskia at gcc dot gnu.org
2024-04-01 16:15 ` egallager at gcc dot gnu.org [this message]

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-105474-4-0l5IudVW5E@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).