public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gcc-zm31 at proton dot me" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/109984] New: FAIL: insn-modes.h: No such file or directory (x86_64-apple-darwin22.4.0) Date: Fri, 26 May 2023 09:39:27 +0000 [thread overview] Message-ID: <bug-109984-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109984 Bug ID: 109984 Summary: FAIL: insn-modes.h: No such file or directory (x86_64-apple-darwin22.4.0) Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: gcc-zm31 at proton dot me Target Milestone: --- When attempting to build GCC with an experimental language frontend, I encounter the following error: In file included from ../../gcc-src/gcc/rinto/rin-system.hpp:30, from ../../gcc-src/gcc/rinto/frontend/backend.hpp:4, from ../../gcc-src/gcc/rinto/frontend/diagnostic.hpp:37, from ../../gcc-src/gcc/rinto/frontend/diagnostic.cc:33: ../../gcc-src/gcc/coretypes.h:458:10: fatal error: insn-modes.h: No such file or directory 458 | #include "insn-modes.h" This only seems to be an issue when passing the -j flag to make. When I otherwise run 'make' on a single processor (without -j), the project compiles. I suspect there might be some oversight on my part, though it could be an issue with the order in which GCC generates header files. The project is configured as follows: ../gcc-src/configure --prefix=/Users/mz/Desktop/gcc-build/../gcc-install --enable-languages=c,c++,rinto --with-sysroot=/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk --disable-nls --enable-checking=release --with-gcc-major-version-only --with-system-zlib And the make command: make -j$(getconf _NPROCESSORS_ONLN) where 'getconf _NPROCESSORS_ONLN; yields 16. Target: x86_64-apple-darwin22.4.0 (though the problem persists on my Ubuntu 22 machine as well). SOURCE-A: https://github.com/rintolang/rinto/tree/main/src/gcc SOURCE-B: https://github.com/rintolang/rinto/tree/main/src/frontend The contents of SOURCE-A are placed in [GCC-ROOT]/gcc/rinto and SOURCE-B in [GCC-ROOT]/gcc/rinto/frontend.
next reply other threads:[~2023-05-26 9:39 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-26 9:39 gcc-zm31 at proton dot me [this message] 2023-05-26 17:25 ` [Bug target/109984] " pinskia 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-109984-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: 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).