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/110624] Xcode 15 ld warns about -macosx_version_min
Date: Tue, 11 Jul 2023 14:11:24 +0000 [thread overview]
Message-ID: <bug-110624-4-U33XA34ecj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110624-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110624
--- Comment #5 from Iain Sandoe <iains at gcc dot gnu.org> ---
Created attachment 55523
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55523&action=edit
Patch for testing
I tested this (by bootstrapping GCC with it) on x86_64 darwin21 with Xcode
14.3.
FWIW; The reason I had not done this sooner, is that I do not have a sensible
way to look up the SDK version at the moment (the second parameter), but AFAIK
0.0 is allowed as a "don't know", so we can improve on this at a later time
Here, I will test on some earlier Darwin versions - but would welcome
confirmation that it fixes the XC15 issue.
-----
```
COLLECT_GCC_OPTIONS='-B' 'gcc' '-o' 'hc' '-v' '-save-temps'
'-mmacosx-version-min=12.0.0' '-nodefaultexport' '-mtune=core2' '-dumpdir'
'hc.'
gcc/collect2 -syslibroot
/Library/Developer/CommandLineTools/SDKs/MacOSX12.3.sdk/ -dynamic -arch x86_64
-platform_version macos 12.0.0 0.0 -o hc -Lgcc hc-hello.o -v -lemutls_w -lgcc
-lSystem -no_compact_unwind
collect2 version 14.0.0 20230707 (experimental) [remotes/home/master revision
r14-2384-gbb3b9c1c3ba8]
gcc/collect-ld -syslibroot
/Library/Developer/CommandLineTools/SDKs/MacOSX12.3.sdk/ -dynamic -arch x86_64
-platform_version macos 12.0.0 0.0 -o hc -Lgcc hc-hello.o -v -lemutls_w -lgcc
-lSystem -no_compact_unwind
@(#)PROGRAM:ld PROJECT:ld64-857.1
```
next prev parent reply other threads:[~2023-07-11 14:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 8:57 [Bug target/110624] New: " ro at gcc dot gnu.org
2023-07-11 9:53 ` [Bug target/110624] " iains at gcc dot gnu.org
2023-07-11 9:57 ` ro at CeBiTec dot Uni-Bielefeld.DE
2023-07-11 10:01 ` iains at gcc dot gnu.org
2023-07-11 10:55 ` ro at CeBiTec dot Uni-Bielefeld.DE
2023-07-11 14:11 ` iains at gcc dot gnu.org [this message]
2023-07-11 14:13 ` iains at gcc dot gnu.org
2023-07-13 8:57 ` ro at CeBiTec dot Uni-Bielefeld.DE
2023-07-13 19:15 ` cvs-commit at gcc dot gnu.org
2023-07-13 19:19 ` iains at gcc dot gnu.org
2023-07-19 8:08 ` cvs-commit at gcc dot gnu.org
2024-04-04 18:50 ` 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-110624-4-U33XA34ecj@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).