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 c++/107511] New: [13 Regression] gcc-13-20221030 failure to build on Cygwin due to lack of secure_getenv
Date: Wed, 02 Nov 2022 20:22:26 +0000 [thread overview]
Message-ID: <bug-107511-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107511
Bug ID: 107511
Summary: [13 Regression] gcc-13-20221030 failure to build on
Cygwin due to lack of secure_getenv
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: mckelvey at maskull dot com
Target Milestone: ---
Created attachment 53822
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53822&action=edit
Build log
libtool: compile:
/home/McKelvey/gcc-13-20221030/host-x86_64-pc-cygwin/gcc/xgcc -shared-libgcc
-B/home/McKelvey/gcc-13-20221030/host-x86_64-pc-cygwin/gcc -nostdinc++
-L/home/McKelvey/gcc-13-20221030/x86_64-pc-cygwin/libstdc++-v3/src
-L/home/McKelvey/gcc-13-20221030/x86_64-pc-cygwin/libstdc++-v3/src/.libs
-L/home/McKelvey/gcc-13-20221030/x86_64-pc-cygwin/libstdc++-v3/libsupc++/.libs
-B/usr/local/x86_64-pc-cygwin/bin/ -B/usr/local/x86_64-pc-cygwin/lib/ -isystem
/usr/local/x86_64-pc-cygwin/include -isystem
/usr/local/x86_64-pc-cygwin/sys-include -fno-checking
-I/home/McKelvey/gcc-13-20221030/libstdc++-v3/../libgcc
-I/home/McKelvey/gcc-13-20221030/x86_64-pc-cygwin/libstdc++-v3/include/x86_64-pc-cygwin
-I/home/McKelvey/gcc-13-20221030/x86_64-pc-cygwin/libstdc++-v3/include
-I/home/McKelvey/gcc-13-20221030/libstdc++-v3/libsupc++ -D_GLIBCXX_SHARED
-fno-implicit-templates -Wall -Wextra -Wwrite-strings -Wcast-qual -Wabi=2
-fdiagnostics-show-location=once -ffunction-sections -fdata-sections
-frandom-seed=eh_alloc.lo -g -O2 -c
../../.././libstdc++-v3/libsupc++/eh_alloc.cc -o eh_alloc.o
../../.././libstdc++-v3/libsupc++/eh_alloc.cc: In constructor
‘{anonymous}::pool::pool()’:
../../.././libstdc++-v3/libsupc++/eh_alloc.cc:190:27: error: ‘::secure_getenv’
has not been declared
190 | const char* str = ::secure_getenv("GLIBCXX_TUNABLES");
$ g++ -v
Using built-in specs.
COLLECT_GCC=g++
COLLECT_LTO_WRAPPER=/usr/local/libexec/gcc/x86_64-pc-cygwin/13.0.0/lto-wrapper.exe
Target: x86_64-pc-cygwin
Configured with: ./configure --enable-languages=c,c++ --enable-threads=posix
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 13.0.0 20221030 (experimental) (GCC)
$ uname
CYGWIN_NT-10.0-19044
Windows 10
See 105540 and 104217 for gcc-11 and 12 fixes.
next reply other threads:[~2022-11-02 20:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 20:22 mckelvey at maskull dot com [this message]
2022-11-02 20:28 ` [Bug libstdc++/107511] " pinskia at gcc dot gnu.org
2022-11-02 20:31 ` pinskia at gcc dot gnu.org
2022-11-02 20:31 ` pinskia at gcc dot gnu.org
2022-11-02 20:34 ` redi at gcc dot gnu.org
2022-11-03 11:43 ` redi at gcc dot gnu.org
2022-11-04 14:05 ` cvs-commit at gcc dot gnu.org
2022-11-04 14:06 ` redi 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-107511-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).