public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <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: Thu, 22 Feb 2024 12:06:30 +0000 [thread overview] Message-ID: <bug-114049-4-AablW88jBg@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 #2 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> --- > --- Comment #1 from Iain Sandoe <iains at gcc dot gnu.org> --- > /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/Kernel.framework/Headers > should be a symlink to > /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/Kernel.framework/Versions/A/Headers More or less: the symlink is to Versions/Current/Headers. > so either that's broken or we're failing to follow a symlink somehow. I've checked: the original invocation is /private/var/gcc/regression/master/14-gcc/build/gcc/xgcc -B/private/var/gcc/regression/master/14-gcc/build/gcc/ /vol/gcc/src/hg/master/darwin/gcc/testsuite/gcc.dg/framework-1.c -fdiagnostics-plain-output -F. -S -o framework-1.s with cc1 called like /private/var/gcc/regression/master/14-gcc/build/gcc/cc1 -quiet -v -F. -iprefix /private/var/gcc/regression/master/14-gcc/build/gcc/../lib/gcc/x86_64-apple-darwin23.3.0/14.0.1/ -isystem /private/var/gcc/regression/master/14-gcc/build/gcc/include -isystem /private/var/gcc/regression/master/14-gcc/build/gcc/include-fixed -D__DYNAMIC__ /vol/gcc/src/hg/master/darwin/gcc/testsuite/gcc.dg/framework-1.c -fPIC -quiet -dumpbase framework-1.c -dumpbase-ext .c -mmacosx-version-min=14.0.0 -mtune=core2 -version -fdiagnostics-color=never -fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers -fdiagnostics-urls=never -fdiagnostics-path-format=separate-events -fdiagnostics-text-art-charset=none -o framework-1.s After the usual messages about nonexistant directories, we get to #include <...> search starts here: . /private/var/gcc/regression/master/14-gcc/build/gcc/include /private/var/gcc/regression/master/14-gcc/build/gcc/include-fixed /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks End of search list. /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/Kernel.framework/Headers/string.h has #include <machine/trap.h> which lives in /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/Kernel.framework/Versions/A/Headers/machine/trap.h Given the above search list, "machine/trap.h" should work, but <machine/trap.h> doesn't. When using the bundled clang, I get $ 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> ^ In file included from /vol/gcc/src/hg/master/darwin/gcc/testsuite/gcc.dg/framework-1.c:4: In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/Kernel.framework/Headers/string.h:55: /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/Kernel.framework/Headers/machine/trap.h:32:10: fatal error: 'i386/trap.h' file not found #include "i386/trap.h" ^~~~~~~~~~~~~ 2 errors generated.
next prev parent reply other threads:[~2024-02-22 12:06 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 [this message] 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 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-AablW88jBg@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).