From: Yao Qi <qiyaoltc@gmail.com>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] [PATCH v5 4/4] Add gdb for or1k build
Date: Tue, 04 Apr 2017 22:32:51 +0100 [thread overview]
Message-ID: <86efx76epo.fsf@gmail.com> (raw)
In-Reply-To: <e14cb9c471bb14d29f789b2af4b3bef85317c3dc.1489728533.git.shorne@gmail.com> (Stafford Horne's message of "Fri, 17 Mar 2017 14:43:20 +0900")
Stafford Horne <shorne@gmail.com> writes:
> * ChangeLog:
>
> * configure.ac: remove logic adding gdb to noconfigsdirs for or1k
> * configure: regenerate
Once all the rest of patch series are OK, send this patch to
gcc-patches at . Top-level configure is maintained there, and binutils-gdb
sync from gdb repository manually.
--
Yao (齐尧)
next prev parent reply other threads:[~2017-04-04 21:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-17 5:43 [OpenRISC] [PATCH v5 0/4] OpenRISC gdb port Stafford Horne
2017-03-17 5:43 ` [OpenRISC] [PATCH v5 1/4] gdb: Add OpenRISC or1k and or1knd target support Stafford Horne
2017-03-17 8:48 ` Eli Zaretskii
2017-03-17 9:32 ` Stafford Horne
2017-03-17 9:35 ` Eli Zaretskii
2017-03-17 10:03 ` Stafford Horne
2017-04-04 21:17 ` Yao Qi
2017-04-08 9:36 ` Stafford Horne
2017-03-17 5:43 ` [OpenRISC] [PATCH v5 2/4] gdb: provide openrisc target description XML files Stafford Horne
2017-04-04 21:25 ` Yao Qi
2017-04-08 9:38 ` Stafford Horne
2017-03-17 5:43 ` [OpenRISC] [PATCH v5 3/4] gdb: testsuite: Add or1k l.nop inscruction Stafford Horne
2017-04-04 21:29 ` Yao Qi
2017-03-17 5:43 ` [OpenRISC] [PATCH v5 4/4] Add gdb for or1k build Stafford Horne
2017-04-04 21:32 ` Yao Qi [this message]
2017-03-21 9:14 ` [OpenRISC] [PATCH v5 0/4] OpenRISC gdb port Yao Qi
2017-03-21 14:17 ` Stafford Horne
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=86efx76epo.fsf@gmail.com \
--to=qiyaoltc@gmail.com \
--cc=openrisc@lists.librecores.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.