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/107136] New: File cp-trait.def not found in kernel build
Date: Mon, 03 Oct 2022 18:14:38 +0000	[thread overview]
Message-ID: <bug-107136-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 107136
           Summary: File cp-trait.def not found in kernel build
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: plugins
          Assignee: unassigned at gcc dot gnu.org
          Reporter: dcb314 at hotmail dot com
  Target Milestone: ---

I've just been having a go at compiling the new linux-6.0 kernel
with a recent trunk gcc. I get

/home/dcb/gcc/results.20221003/lib/gcc/x86_64-pc-linux-gnu/13.0.0/plugin/include/c-family/c-common.h:172:10:
fatal error: cp/cp-trait.def: No such file or directory

but

$ find /home/dcb/gcc/results.20221003 -name cp-trait.def -print
$

so it looks like that file isn't installed. But

[/home/dcb/gcc/trunk.git] $ find . -name cp-trait\* -print
./gcc/cp/cp-trait.def
[/home/dcb/gcc/trunk.git] $ 

so the file does exist in trunk.

             reply	other threads:[~2022-10-03 18:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-03 18:14 dcb314 at hotmail dot com [this message]
2022-10-03 18:15 ` [Bug plugins/107136] " dcb314 at hotmail dot com
2022-10-03 18:19 ` pinskia at gcc dot gnu.org
2022-10-03 18:20 ` [Bug c++/107136] [13 Regression] File cp/cp-trait.def file not installed for plugin suport pinskia at gcc dot gnu.org
2022-10-03 18:22 ` pinskia at gcc dot gnu.org
2022-10-03 18:26 ` dcb314 at hotmail dot com
2022-10-04  0:33 ` ppalka at gcc dot gnu.org
2022-10-04  0:38 ` ppalka at gcc dot gnu.org
2022-10-04  0:43 ` ppalka at gcc dot gnu.org
2022-10-04 16:25 ` cvs-commit at gcc dot gnu.org
2022-10-04 16:31 ` ppalka 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-107136-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).