From: Mark Wielaard <mark@klomp.org>
To: Nick Clifton <nickc@redhat.com>
Cc: annobin@sourceware.org
Subject: Re: ☠ Buildbot (Sourceware): annobin - failed compile (failure) (master)
Date: Mon, 4 Mar 2024 23:41:13 +0100 [thread overview]
Message-ID: <20240304224113.GC12540@gnu.wildebeest.org> (raw)
In-Reply-To: <7e8ddfe1-4fb1-433b-b610-59f13b456193@redhat.com>
Hi Nick,
On Mon, Mar 04, 2024 at 10:48:23AM +0000, Nick Clifton wrote:
> >This one does have clang++ but fails with:
> >
> >make[1]: Leaving directory '/home/builder/shared/bb3/worker/annobin-rawhide-x86_64/build/clang-plugin'
> >annobin.cpp:15:10: fatal error: 'clang/Frontend/FrontendPluginRegistry.h' file not found
> > 15 | #include "clang/Frontend/FrontendPluginRegistry.h"
>
> >Is there a missing package?
>
> Yes: clang-devel
OK, found it. For Fedora based distros you now need:
clang clang-devel llvm-devel
And for Debian based distros you need:
clang libclang-dev llvm
But on Deban based systems the headers and libraries are installed in
an llvm version specific location. You can find them using
llvm-config. Luckily this also works for the unversioned llvm on
Fedora bases systems:
(debian) llvm-config --cxxflags
-I/usr/lib/llvm-14/include -std=c++14 -fno-exceptions -D_GNU_SOURCE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS
(debian) llvm-config --ldflags --system-libs
-L/usr/lib/llvm-14/lib
(fedora) llvm-config --cxxflags
-I/usr/include -std=c++17 -fno-exceptions -funwind-tables -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS
(fedora) llvm-config --ldflags --system-libs
-L/usr/lib64
I don't know how hard that is to incorporate in the configure/automake
scripts.
Cheers,
Mark
next prev parent reply other threads:[~2024-03-04 22:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 19:11 builder
2024-03-01 22:48 ` Mark Wielaard
2024-03-04 10:48 ` Nick Clifton
2024-03-04 22:41 ` Mark Wielaard [this message]
2024-03-05 16:47 ` Nick Clifton
2024-04-23 20:33 builder
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=20240304224113.GC12540@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=annobin@sourceware.org \
--cc=nickc@redhat.com \
/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).