public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/109077] Analyzer headers not installed
Date: Tue, 28 Nov 2023 08:21:11 +0000 [thread overview]
Message-ID: <bug-109077-4-JqyFk4GKNR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109077-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109077
--- Comment #3 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by David Malcolm <dmalcolm@gcc.gnu.org>:
https://gcc.gnu.org/g:594ef1ff707866bcdc1f077c5d078a5bd250320f
commit r14-5899-g594ef1ff707866bcdc1f077c5d078a5bd250320f
Author: David Malcolm <dmalcolm@redhat.com>
Date: Tue Nov 28 03:20:02 2023 -0500
analyzer: install header files for use by plugins [PR109077]
PLUGIN_ANALYZER_INIT was added in r11-5583-g66dde7bc64b75d, but we
haven't been installing the analyzer's headers files.
Fixed thusly.
gcc/ChangeLog:
PR analyzer/109077
* Makefile.in (PLUGIN_HEADERS): Add analyzer headers.
(install-plugin): Keep the directory structure for files in
"analyzer".
Signed-off-by: David Malcolm <dmalcolm@redhat.com>
next prev parent reply other threads:[~2023-11-28 8:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 9:33 [Bug analyzer/109077] New: Analyzer header " pierrick.philippe at irisa dot fr
2023-11-27 22:04 ` [Bug analyzer/109077] " dmalcolm at gcc dot gnu.org
2023-11-27 22:11 ` [Bug analyzer/109077] Analyzer headers " dmalcolm at gcc dot gnu.org
2023-11-28 8:21 ` cvs-commit at gcc dot gnu.org [this message]
2023-11-28 8:31 ` dmalcolm at gcc dot gnu.org
2024-04-14 5:07 ` [Bug analyzer/109077] [11/12/13 Regression] " pinskia at gcc dot gnu.org
2024-05-13 11:34 ` rguenth 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-109077-4-JqyFk4GKNR@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).