public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/107568] Darwin: Bootstrap fails with macOS13 sdk because sprintf and friends are deprecated in the SDK.
Date: Mon, 02 Jan 2023 17:12:28 +0000 [thread overview]
Message-ID: <bug-107568-4-KKyjV8U7MX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107568-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107568
--- Comment #12 from Iain Sandoe <iains at gcc dot gnu.org> ---
with Xcode 14.1 CLT and the macOS13 SDK, the build fails without the
work-around and works for this:
time nice make -j10 BOOT_CFLAGS="-O2 -g -Wno-error=deprecated-declarations"
>b.txt 2>e.txt
(jftr) configure line is:
/src-local/gcc-master/configure
--prefix=/opt/iains/x86_64-apple-darwin21/gcc-13-0-0
--build=x86_64-apple-darwin21
--with-sysroot=/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk
CC=x86_64-apple-darwin19-gcc CXX=x86_64-apple-darwin19-g++
--enable-languages=all >conf.txt
and the source is current master.
(OK, so the differences are [1] I am on macOS12 and [2] I'm using Xcode 14.1
CLT,but the fail and fix are completely repeatable here).
Next, I guess I'll pick up the xc 14.2 release.
next prev parent reply other threads:[~2023-01-02 17:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 11:47 [Bug bootstrap/107568] New: Bootstrap failure on macOS 12.6 (monterey) simon at pushface dot org
2022-11-08 13:34 ` [Bug bootstrap/107568] " rguenth at gcc dot gnu.org
2022-11-08 13:37 ` jakub at gcc dot gnu.org
2022-11-08 15:59 ` [Bug target/107568] " pinskia at gcc dot gnu.org
2022-11-09 8:47 ` sam at gentoo dot org
2022-11-20 19:13 ` iains at gcc dot gnu.org
2022-12-13 10:24 ` iains at gcc dot gnu.org
2022-12-13 11:20 ` [Bug target/107568] Darwin: Bootstrap fails with macOS13 sdk because sprintf and friends are deprecated in the SDK pinskia at gcc dot gnu.org
2023-01-02 12:34 ` juergen.reuter at desy dot de
2023-01-02 12:44 ` iains at gcc dot gnu.org
2023-01-02 14:00 ` juergen.reuter at desy dot de
2023-01-02 14:09 ` iains at gcc dot gnu.org
2023-01-02 17:12 ` iains at gcc dot gnu.org [this message]
2023-01-02 19:24 ` juergen.reuter at desy dot de
2023-01-21 17:08 ` cvs-commit at gcc dot gnu.org
2023-04-26 6:57 ` rguenth at gcc dot gnu.org
2023-05-16 19:05 ` cvs-commit at gcc dot gnu.org
2023-05-16 19:11 ` iains at gcc dot gnu.org
2023-05-21 18:55 ` cvs-commit at gcc dot gnu.org
2023-05-21 19:06 ` iains at gcc dot gnu.org
2024-04-04 18:51 ` 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-107568-4-KKyjV8U7MX@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).