public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "brechtsanders at users dot sourceforge.net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/105858] New: MinGW-w64 64-bit build with --libstdcxx-pch: fatal error: cannot write PCH file: required memory segment unavailable
Date: Sun, 05 Jun 2022 19:13:06 +0000	[thread overview]
Message-ID: <bug-105858-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 105858
           Summary: MinGW-w64 64-bit build with --libstdcxx-pch: fatal
                    error: cannot write PCH file: required memory segment
                    unavailable
           Product: gcc
           Version: 12.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: brechtsanders at users dot sourceforge.net
  Target Milestone: ---

When building the Windows 64-bit version of GCC 12.1.0 against MinGW-w64 build
with --libstdcxx-pch the following error occurs:

In file included from
R:/winlibs64_stage/gcc-12.1.0/libstdc++-v3/include/precompiled/extc++.h:82:
R:/winlibs64_stage/gcc-12.1.0/build_mingw/x86_64-w64-mingw32/libstdc++-v3/include/ext/enc_filebuf.h:63:1:
fatal error: cannot write PCH file: required memory segment unavailable
   63 | } // namespace
      | ^
compilation terminated.

This error does not happen when building the 32-bit version.

             reply	other threads:[~2022-06-05 19:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-05 19:13 brechtsanders at users dot sourceforge.net [this message]
2022-07-04  9:18 ` [Bug pch/105858] " brechtsanders at users dot sourceforge.net
2022-07-25  9:32 ` brechtsanders at users dot sourceforge.net
2022-08-06 10:02 ` brechtsanders at users dot sourceforge.net
2022-09-04  7:58 ` brechtsanders at users dot sourceforge.net
2022-09-04 13:53 ` brechtsanders at users dot sourceforge.net
2022-12-24  1:56 ` egor.pugin at gmail dot com
2022-12-26 15:02 ` brechtsanders at users dot sourceforge.net
2022-12-30 13:26 ` brechtsanders at users dot sourceforge.net

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