public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mckelvey at maskull dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/104217] New: gcc-12-20220123 failure to build on Cygwin due to lack of secure_getenv
Date: Mon, 24 Jan 2022 23:50:35 +0000 [thread overview]
Message-ID: <bug-104217-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104217
Bug ID: 104217
Summary: gcc-12-20220123 failure to build on Cygwin due to lack
of secure_getenv
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: bootstrap
Assignee: unassigned at gcc dot gnu.org
Reporter: mckelvey at maskull dot com
Target Milestone: ---
Created attachment 52283
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52283&action=edit
Tarball of attempted build
This bug has been around for a few snapshots so I'm reporting it now.
In file included from ../../../.././libstdc++-v3/src/c++17/fs_ops.cc:58:
../../../.././libstdc++-v3/src/c++17/../filesystem/ops-common.h: In function
‘const char* std::filesystem::get_temp_directory_from_env(std::error_code&)’:
../../../.././libstdc++-v3/src/c++17/../filesystem/ops-common.h:640:25: error:
‘::secure_getenv’ has not been declared
640 | auto tmpdir = ::secure_getenv(env);
^~~~~~~~~~~~~
make[6]: *** [Makefile:585: fs_ops.lo] Error 1
Configured as: ./configure --enable-languages=c,c++ --enable-threads=posix
Run under up-to-date Cygwin using gcc-11-20220122.
cygcheck (cygwin) 3.3.3
next reply other threads:[~2022-01-24 23:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 23:50 mckelvey at maskull dot com [this message]
2022-01-24 23:54 ` [Bug bootstrap/104217] " pinskia at gcc dot gnu.org
2022-01-24 23:55 ` mckelvey at maskull dot com
2022-01-24 23:55 ` pinskia at gcc dot gnu.org
2022-01-24 23:57 ` pinskia at gcc dot gnu.org
2022-01-25 0:01 ` mckelvey at maskull dot com
2022-01-25 0:07 ` [Bug libstdc++/104217] [12 Regression] " pinskia at gcc dot gnu.org
2022-01-25 0:11 ` pinskia at gcc dot gnu.org
2022-01-25 8:10 ` rguenth at gcc dot gnu.org
2022-01-25 10:00 ` redi at gcc dot gnu.org
2022-01-25 10:02 ` redi at gcc dot gnu.org
2022-01-25 21:09 ` cvs-commit at gcc dot gnu.org
2022-02-22 17:40 ` redi at gcc dot gnu.org
2022-05-09 21:44 ` cvs-commit 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-104217-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).