From: "630dr7+9vgtozzjuj0gg at sharklasers dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/21063] dtrace script causes mysterious build failures due to improper forming of gcc command line
Date: Wed, 18 Jan 2017 22:03:00 -0000 [thread overview]
Message-ID: <bug-21063-6586-TZXws32E0o@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-21063-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=21063
Kinston Hughes <630dr7+9vgtozzjuj0gg at sharklasers dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://bugzilla.redhat.com
| |/show_bug.cgi?id=1413762
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2017-01-18 22:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 22:03 [Bug runtime/21063] New: " 630dr7+9vgtozzjuj0gg at sharklasers dot com
2017-01-18 22:03 ` 630dr7+9vgtozzjuj0gg at sharklasers dot com [this message]
2017-01-21 7:33 ` [Bug runtime/21063] " fche at redhat dot com
2017-01-21 22:36 ` 630dr7+9vgtozzjuj0gg at sharklasers dot com
2017-01-21 23:00 ` fche at redhat dot com
2017-01-22 22:22 ` 630dr7+9vgtozzjuj0gg at sharklasers dot com
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-21063-6586-TZXws32E0o@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).