public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c/102025] New: "COMMON_LVB_REVERSE_VIDEO" was not declared in this scope (pretty-print.c) while compiling gcc 11.2.0
@ 2021-08-23 14:40 harun.bozaci at hotmail dot com
  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
  0 siblings, 2 replies; 3+ messages in thread
From: harun.bozaci at hotmail dot com @ 2021-08-23 14:40 UTC (permalink / raw)
  To: gcc-bugs

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?

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug middle-end/102025] "COMMON_LVB_REVERSE_VIDEO" was not declared in this scope (pretty-print.c) while compiling gcc 11.2.0
  2021-08-23 14:40 [Bug c/102025] New: "COMMON_LVB_REVERSE_VIDEO" was not declared in this scope (pretty-print.c) while compiling gcc 11.2.0 harun.bozaci at hotmail dot com
@ 2021-08-23 22:51 ` pinskia at gcc dot gnu.org
  2021-08-24  7:48 ` harun.bozaci at hotmail dot com
  1 sibling, 0 replies; 3+ messages in thread
From: pinskia at gcc dot gnu.org @ 2021-08-23 22:51 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
So it looks like COMMON_LVB_REVERSE_VIDEO is defined sometimes but not in all
versions of the header files.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug middle-end/102025] "COMMON_LVB_REVERSE_VIDEO" was not declared in this scope (pretty-print.c) while compiling gcc 11.2.0
  2021-08-23 14:40 [Bug c/102025] New: "COMMON_LVB_REVERSE_VIDEO" was not declared in this scope (pretty-print.c) while compiling gcc 11.2.0 harun.bozaci at hotmail dot com
  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
  1 sibling, 0 replies; 3+ messages in thread
From: harun.bozaci at hotmail dot com @ 2021-08-24  7:48 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #2 from Harun BOZACI <harun.bozaci at hotmail dot com> ---
(In reply to Andrew Pinski from comment #1)
> So it looks like COMMON_LVB_REVERSE_VIDEO is defined sometimes but not in
> all versions of the header files.

Should I create a manual patch for this symbolic names or should I
upgrade/downgrade toolchain I am using for compiling (I meant gcc which is
provided by mingw)?

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2021-08-24  7:48 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-08-23 14:40 [Bug c/102025] New: "COMMON_LVB_REVERSE_VIDEO" was not declared in this scope (pretty-print.c) while compiling gcc 11.2.0 harun.bozaci at hotmail dot com
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

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