public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "daniel.f.starke at freenet dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/100460] New: [11/12 Regression] mingw build broken due to use of unsupported open() flags
Date: Thu, 06 May 2021 20:04:41 +0000 [thread overview]
Message-ID: <bug-100460-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100460
Bug ID: 100460
Summary: [11/12 Regression] mingw build broken due to use of
unsupported open() flags
Product: gcc
Version: 11.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: daniel.f.starke at freenet dot de
Target Milestone: ---
GCC 11.1.0 fails to build with C++ under MinGW due to unsupported open() flags
S_IRUSR|S_IWUSR|S_IRGRP|S_IWGRP|S_IROTH|S_IWOTH in function
finish_module_processing() within gcc/cp/module.cc.
I suggest to remove these flags.
MinGW will not fix this due to unforseen side effects:
https://sourceforge.net/p/mingw/mailman/mingw-users/thread/znzrt579.fsf@wanadoo.es/
next reply other threads:[~2021-05-06 20:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-06 20:04 daniel.f.starke at freenet dot de [this message]
2021-05-07 7:15 ` [Bug target/100460] [11/12 Regression][modules] " rguenth at gcc dot gnu.org
2021-07-28 7:06 ` rguenth at gcc dot gnu.org
2022-04-21 7:49 ` rguenth at gcc dot gnu.org
2022-07-26 13:37 ` [Bug c++/100460] [11/12/13 " rguenth at gcc dot gnu.org
2022-07-26 14:25 ` schwab@linux-m68k.org
2022-12-07 17:29 ` pinskia at gcc dot gnu.org
2022-12-07 17:36 ` pinskia at gcc dot gnu.org
2023-05-29 10:04 ` [Bug c++/100460] [11/12/13/14 " jakub 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-100460-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).