public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "xry111 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug plugins/110610] File insn-opinit.h not installed ?
Date: Mon, 10 Jul 2023 09:28:04 +0000	[thread overview]
Message-ID: <bug-110610-4-droadzUuvh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110610-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110610

--- Comment #4 from Xi Ruoyao <xry111 at gcc dot gnu.org> ---
(In reply to avieira from comment #2)
> I can't reproduce this but it seems like the modula2 build also suffers from
> the same issue, see PR110284.
> 
> David, what exactly are you trying to build? Can you give us the configure
> command?

The OP is building a GCC plugin, it includes internal-fn.h.  But internal-fn.h
includes insn-opinit.h, and insn-opinit.h is not installed.

See
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/scripts/gcc-plugins/gcc-common.h#n73

  parent reply	other threads:[~2023-07-10  9:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-10  7:04 [Bug plugins/110610] New: " dcb314 at hotmail dot com
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 [this message]
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-droadzUuvh@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).