public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug sim/13160] bfin simulator does not build on Darwin
Date: Tue, 10 Mar 2015 14:04:00 -0000 [thread overview]
Message-ID: <bug-13160-4717-5VEzydIPkw@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13160-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=13160
--- Comment #8 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Michael Frysinger
<vapier@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=6defcd57e9df4f61cd0c59e3d9b66b6b071af808
commit 6defcd57e9df4f61cd0c59e3d9b66b6b071af808
Author: Mike Frysinger <vapier@gentoo.org>
Date: Tue Mar 10 01:41:48 2015 -0400
sim: bfin: fix up linux-fixed-code.h generation more [PR sim/13160]
Add a trailing semi-colon to the sed print command as the BSD sed
implementation wants it. It's a nop otherwise and works fine on
GNU/etc... implementations too.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2015-03-10 5:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-07 0:20 [Bug build/13160] New: " chrisj at rtems dot org
2015-03-09 3:52 ` [Bug sim/13160] " vapier at gentoo dot org
2015-03-09 6:08 ` vapier at gentoo dot org
2015-03-10 2:18 ` chrisj at rtems dot org
2015-03-10 3:47 ` vapier at gentoo dot org
2015-03-10 4:33 ` chrisj at rtems dot org
2015-03-10 5:09 ` vapier at gentoo dot org
2015-03-10 5:42 ` chrisj at rtems dot org
2015-03-10 5:44 ` vapier at gentoo dot org
2015-03-10 14:04 ` cvs-commit at gcc dot gnu.org [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-13160-4717-5VEzydIPkw@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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).