From: "amerey at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug server/26839] Systemtap build failures with clang
Date: Wed, 19 May 2021 21:46:07 +0000 [thread overview]
Message-ID: <bug-26839-6586-3zsMEMO3gE@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26839-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=26839
Aaron Merey <amerey at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #11 from Aaron Merey <amerey at redhat dot com> ---
Thanks for your patience Timm. I've merged your patch set, see the following
commits:
14f04522b5
930b541193
6de815bcaa
0f4bd32197
545535f823
b3a3929751
8e5145ae4c
I also merged a patch to fix a couple more -Wformat-nonliteral and
-Wmismatched-tags I ran into (commit 3e9bcd7b1fcf).
With these patches and CCC_OVERRIDE_OPTIONS="x-flto=auto" I can successfully
build systemtap with clang.
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2021-05-19 21:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 8:27 [Bug server/26839] New: " tbaeder at redhat dot com
2020-11-05 1:11 ` [Bug server/26839] " fche at redhat dot com
2020-11-05 1:23 ` fche at redhat dot com
2020-11-05 9:21 ` tbaeder at redhat dot com
2020-11-23 19:12 ` tstellar at redhat dot com
2020-11-24 7:52 ` tbaeder at redhat dot com
2021-01-18 12:06 ` tbaeder at redhat dot com
2021-01-18 15:10 ` tstellar at redhat dot com
2021-05-11 12:00 ` tbaeder at redhat dot com
2021-05-13 2:17 ` amerey at redhat dot com
2021-05-14 7:57 ` tbaeder at redhat dot com
2021-05-19 21:46 ` amerey at redhat dot com [this message]
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-26839-6586-3zsMEMO3gE@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.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).