public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug plugins/110610] New: File insn-opinit.h not installed ?
Date: Mon, 10 Jul 2023 07:04:39 +0000 [thread overview]
Message-ID: <bug-110610-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110610
Bug ID: 110610
Summary: File insn-opinit.h not installed ?
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: plugins
Assignee: unassigned at gcc dot gnu.org
Reporter: dcb314 at hotmail dot com
Target Milestone: ---
Recent linux kernels seem to think that file insn-opinit.h is available
in a gcc install.
CC /home/dcb38/linuxKernel/linux-6.4/tools/objtool/arch/x86/special.o
In file included from scripts/gcc-plugins/gcc-common.h:73,
from scripts/gcc-plugins/stackleak_plugin.c:30:
/home/dcb38/gcc/results.20230701.valgrind/lib/gcc/x86_64-pc-linux-gnu/14.0.0/plugin/include/internal-fn.h:24:10:
fatal error: insn-opinit.h: No such file or directory
24 | #include "insn-opinit.h"
| ^~~~~~~~~~~~~~~
I found a straightforward copy of the file from a gcc build made the problem
go away:
$ history | grep insn | grep cp
1019 cp /home/dcb38/gcc/working/gcc/insn-opinit.h
/home/dcb38/gcc/results.20230708.asan.ubsan/lib/gcc/x86_64-pc-linux-gnu/14.0.0/plugin/include/
1022 history | grep insn | grep cp
$
I am pretty sure there is a better way than a "cp" command to solve this
problem.
Perhaps the install could do the copy instead ?
next reply other threads:[~2023-07-10 7:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 7:04 dcb314 at hotmail dot com [this message]
2023-07-10 7:42 ` [Bug plugins/110610] " xry111 at gcc dot gnu.org
2023-07-10 8:06 ` avieira at gcc dot gnu.org
2023-07-10 8:57 ` dcb314 at hotmail dot com
2023-07-10 9:28 ` xry111 at gcc dot gnu.org
2023-07-10 9:41 ` avieira at gcc dot gnu.org
2023-07-10 10:13 ` xry111 at gcc dot gnu.org
2023-07-10 10:15 ` avieira at gcc dot gnu.org
2023-07-10 10:24 ` avieira at gcc dot gnu.org
2023-07-10 10:25 ` avieira at gcc dot gnu.org
2023-07-10 21:35 ` pinskia at gcc dot gnu.org
2023-07-11 15:53 ` [Bug plugins/110610] [14 Regression] " pinskia at gcc dot gnu.org
2023-07-17 16:04 ` cvs-commit at gcc dot gnu.org
2023-07-17 16:04 ` avieira 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-110610-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: 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).