public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kclifford at tranaptic dot ca" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/110385] New: Build of MinGW g++ 13.1.0 fails due to absence of a header file.
Date: Sat, 24 Jun 2023 00:35:45 +0000	[thread overview]
Message-ID: <bug-110385-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 110385
           Summary: Build of MinGW g++ 13.1.0 fails due to absence of a
                    header file.
           Product: gcc
           Version: 13.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: kclifford at tranaptic dot ca
  Target Milestone: ---

I was building g++ after building newlib. The build failed because a header
file wasn't found.

Build system: CYGWIN_NT-10.0-19045 Keith-PC 3.4.6-1.x86_64 2023-02-14 13:23 UTC
x86_64 Cygwin
Target: arm-eabi, m68k-elf, and powerpc-eabi

Using built-in specs.
COLLECT_GCC=arm-eabi-gcc
COLLECT_LTO_WRAPPER=C:/gcc/MinGW-arm-eabi-13.1.0/bin/../libexec/gcc/arm-eabi/13.1.0/lto-wrapper.exe
Target: arm-eabi
Configured with: /home/cross-gcc/gcc/configure --build=i686-w64-mingw32
--host=i686-w64-mingw32 --target=arm-eabi --enable-__cxa_atexit
--with-pkgversion=Tranaptic-2023/06/16-04:39:28 --with-bugurl=none
--enable-languages=c,c++ --enable-interwork --enable-multilib --with-gcc
--with-gnu-ld --with-gnu-as --with-stabs --disable-shared --disable-threads
--disable-win32-registry --disable-nls --with-newlib
--with-gmp=/home/cross-gcc/13.1.0/cross-local
--with-mpfr=/home/cross-gcc/13.1.0/cross-local
--with-mpc=/home/cross-gcc/13.1.0/cross-local
--with-isl=/home/cross-gcc/13.1.0/cross-local
--prefix=/home/cross-gcc/13.1.0/arm-eabi -v
Thread model: single
Supported LTO compression algorithms: zlib
gcc version 13.1.0 (Tranaptic-2023/06/16-04:39:28)


I modified the following files as follows to get the build to work:

diff --git a/libgcc/configure b/libgcc/configure
index be5d45f1755..4e75ece8e24 100755
--- a/libgcc/configure
+++ b/libgcc/configure
@@ -5700,6 +5700,7 @@ case $target_thread_file in
     vxworks)   thread_header=config/gthr-vxworks.h ;;
     win32)     thread_header=config/i386/gthr-win32.h ;;
     mcf)       thread_header=config/i386/gthr-mcf.h ;;
+    *) thread_header=gthr-single.h ;;
 esac


diff --git a/libstdc++-v3/configure b/libstdc++-v3/configure
index 68ee94c9e28..7c51d3cee87 100755
--- a/libstdc++-v3/configure
+++ b/libstdc++-v3/configure
@@ -15810,6 +15810,7 @@ case $target_thread_file in
     vxworks)   thread_header=config/gthr-vxworks.h ;;
     win32)     thread_header=config/i386/gthr-win32.h ;;
     mcf)       thread_header=config/i386/gthr-mcf.h ;;
+    *) thread_header=gthr-single.h ;;
 esac

             reply	other threads:[~2023-06-24  0:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-24  0:35 kclifford at tranaptic dot ca [this message]
2023-06-24  0:43 ` [Bug c++/110385] " pinskia at gcc dot gnu.org
2023-06-24  0:45 ` [Bug bootstrap/110385] " pinskia 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-110385-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).