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++/103650] New: [9/10/11/12 Regression] libstdc++ headers defined LT_OBJDIR and STDC_HEADERS
Date: Fri, 10 Dec 2021 14:49:06 +0000	[thread overview]
Message-ID: <bug-103650-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 103650
           Summary: [9/10/11/12 Regression] libstdc++ headers defined
                    LT_OBJDIR and STDC_HEADERS
           Product: gcc
           Version: 11.2.1
            Status: UNCONFIRMED
          Keywords: rejects-valid
          Severity: normal
          Priority: P3
         Component: libstdc++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: redi at gcc dot gnu.org
  Target Milestone: ---

#define LT_OBJDIR 99
#define STDC_HEADERS 99
#include <utility>
#if LT_OBJDIR != 99
# error LT_OBJDIR redefined
#endif
#if STDC_HEADERS != 99
# error STDC_HEADERS redefined
#endif


In file included from /usr/include/c++/11/utility:68,
                 from macros.C:3:
macros.C:4:5: error: token "".libs/"" is not valid in preprocessor expressions
    4 | #if LT_OBJDIR != 99
      |     ^~~~~~~~~
macros.C:8:3: error: #error STDC_HEADERS redefined
    8 | # error STDC_HEADERS redefined
      |   ^~~~~


With GCC 4.1 only STDC_HEADERS was defined:

macros.C:8:3: error: #error STDC_HEADERS redefined

So the definition of LT_OBJDIR in 4.3 and later (I can't check 4.2) is a
regression.

We never asked for those macros, this is libtool and autoconf being "helpful".

             reply	other threads:[~2021-12-10 14:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-10 14:49 redi at gcc dot gnu.org [this message]
2022-01-17  9:01 ` [Bug libstdc++/103650] " rguenth at gcc dot gnu.org
2022-01-17 12:10 ` cvs-commit at gcc dot gnu.org
2022-04-04 11:47 ` [Bug libstdc++/103650] [9/10/11 " cvs-commit at gcc dot gnu.org
2022-04-04 21:22 ` [Bug libstdc++/103650] [9/10 " redi at gcc dot gnu.org
2022-04-26 13:12 ` cvs-commit at gcc dot gnu.org
2022-05-09 16:39 ` [Bug libstdc++/103650] [9 " cvs-commit at gcc dot gnu.org
2022-05-09 16:49 ` 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-103650-4@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).