public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/107008] Combine config/os/*/error_constants.h into one file
Date: Thu, 22 Sep 2022 10:38:32 +0000	[thread overview]
Message-ID: <bug-107008-4-mCeQYvTsUL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107008-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
In theory the existing per-target error_constants.h allows an out-of-tree port
for a new OS to use its own error_constants.h more easily. Meh. They would
still need to edit configure.host to overrride ${error_constants_dir}, so they
can just edit the error_constants.h file instead. Adding a couple of #ifdef
conditions in there seems easier than providing a whole new file anyway.

  reply	other threads:[~2022-09-22 10:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-22 10:33 [Bug libstdc++/107008] New: " redi at gcc dot gnu.org
2022-09-22 10:38 ` redi at gcc dot gnu.org [this message]
2022-09-22 10:44 ` [Bug libstdc++/107008] " redi at gcc dot gnu.org
2022-09-22 10:45 ` redi 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-107008-4-mCeQYvTsUL@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).