public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "harun.bozaci at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/102025] New: "COMMON_LVB_REVERSE_VIDEO" was not declared in this scope (pretty-print.c) while compiling gcc 11.2.0
Date: Mon, 23 Aug 2021 14:40:39 +0000	[thread overview]
Message-ID: <bug-102025-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 102025
           Summary: "COMMON_LVB_REVERSE_VIDEO" was not declared in this
                    scope (pretty-print.c) while compiling gcc 11.2.0
           Product: gcc
           Version: 11.2.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: harun.bozaci at hotmail dot com
  Target Milestone: ---
              Host: i686-pc-mingw32
            Target: x86_64-pc-elf
             Build: i686-pc-mingw32

Hi, all. I am trying to build gcc 11.2.0 from scratch for Windows, at some step
of build process, it exits because of some errors. I searched for this issue
and try to find macro in gcc sources but I have nothing at the end of day.

" ../../gcc-11.2.0/gcc/pretty-print.c:644:24: error: 'COMMON_LVB_REVERSE_VIDEO'
was not declared in this scope
       if (attrib_add & COMMON_LVB_REVERSE_VIDEO) "

Is there any one who faced with this problem and managed to solve it? Could you
please help me about this one?

             reply	other threads:[~2021-08-23 14:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-23 14:40 harun.bozaci at hotmail dot com [this message]
2021-08-23 22:51 ` [Bug middle-end/102025] " pinskia at gcc dot gnu.org
2021-08-24  7:48 ` harun.bozaci at hotmail dot com

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-102025-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).