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/114049] gcc.dg/framework-1.c FAILs with Xcode 15.3 beta 3 Date: Fri, 23 Feb 2024 11:03:49 +0000 [thread overview] Message-ID: <bug-114049-4-WeZPBrVo6p@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114049-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114049 --- Comment #6 from Iain Sandoe <iains at gcc dot gnu.org> --- I'm still finding this a bit confusing. - we have not altered the code in this area (at least not the Darwin parts) during the gcc-14 cycle. - apparently, it works with previous Xcode versions/SDKs - from your comment #2 "$ clang /vol/gcc/src/hg/master/darwin/gcc/testsuite/gcc.dg/framework-1.c -F. -S -o framework-1.s In file included from /vol/gcc/src/hg/master/darwin/gcc/testsuite/gcc.dg/framework-1.c:4: /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/Kernel.framework/Headers/string.h:55:10: error: 'machine/trap.h' file not found with <angled> include; use "quotes" instead #include <machine/trap.h> " that seems to be an error, not a warning (even if it diagnoses better than we do). - even if it tries to fall back to the "" version, that still should not find the header according to the information in comment #5 - since we so not add any paths below Library/Frameworks .. so 'machine' is only a top level include directory in /usr/include (and it does not contain trap.h).
next prev parent reply other threads:[~2024-02-23 11:03 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-22 9:56 [Bug target/114049] New: " ro at gcc dot gnu.org 2024-02-22 9:57 ` [Bug target/114049] " ro at gcc dot gnu.org 2024-02-22 10:40 ` iains at gcc dot gnu.org 2024-02-22 12:06 ` ro at CeBiTec dot Uni-Bielefeld.DE 2024-02-22 13:14 ` iains at gcc dot gnu.org 2024-02-22 13:28 ` ro at CeBiTec dot Uni-Bielefeld.DE 2024-02-22 13:55 ` iains at gcc dot gnu.org 2024-02-23 11:03 ` iains at gcc dot gnu.org [this message] 2024-03-07 16:52 ` fxcoudert at gcc dot gnu.org 2024-03-16 15:51 ` iains at gcc dot gnu.org 2024-03-19 13:00 ` cvs-commit at gcc dot gnu.org 2024-03-19 16:02 ` iains at gcc dot gnu.org 2024-04-04 18:36 ` cvs-commit at gcc dot gnu.org 2024-04-21 13:03 ` cvs-commit at gcc dot gnu.org 2024-04-29 14:18 ` cvs-commit at gcc dot gnu.org 2024-04-29 14:41 ` iains 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-114049-4-WeZPBrVo6p@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: linkBe 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).