From: Yao Qi <qiyaoltc@gmail.com>
To: Yan-Ting Lin <currygt52@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2] AndesTech NDS32 port
Date: Mon, 09 May 2016 08:15:00 -0000 [thread overview]
Message-ID: <861t5bd4vi.fsf@gmail.com> (raw)
In-Reply-To: <3561f390-ea41-2ee3-a5a9-d870429497c3@gmail.com> (Yan-Ting Lin's message of "Thu, 5 May 2016 15:16:30 +0800")
Yan-Ting Lin <currygt52@gmail.com> writes:
> diff --git a/configure b/configure
> index 35f231e..67f71fa 100755
> --- a/configure
> +++ b/configure
> @@ -3938,7 +3938,7 @@ case "${target}" in
> noconfigdirs="$noconfigdirs gprof"
> ;;
> nds32*-*-*)
> - noconfigdirs="$noconfigdirs gdb"
> + noconfigdirs="$noconfigdirs"
> ;;
> nvptx*-*-*)
> noconfigdirs="$noconfigdirs target-libssp target-libstdc++-v3 target-libobjc"
> diff --git a/configure.ac b/configure.ac
> index 74bf58a..f7427b5 100644
> --- a/configure.ac
> +++ b/configure.ac
> @@ -1274,7 +1274,7 @@ case "${target}" in
> noconfigdirs="$noconfigdirs gprof"
> ;;
> nds32*-*-*)
> - noconfigdirs="$noconfigdirs gdb"
> + noconfigdirs="$noconfigdirs"
> ;;
> nvptx*-*-*)
> noconfigdirs="$noconfigdirs target-libssp target-libstdc++-v3 target-libobjc"
top-level configure changes should be submitted to gcc-patches list.
Once it is approved there, you can commit it to gcc repository and sync
configure and configure.ac to binutils-gdb repository.
--
Yao (齐尧)
next prev parent reply other threads:[~2016-05-09 8:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-05 7:16 Yan-Ting Lin
2016-05-05 23:46 ` Kevin Buettner
2016-05-06 11:00 ` Yao Qi
2016-05-06 16:09 ` Kevin Buettner
2016-05-09 8:15 ` Yao Qi [this message]
2016-05-10 8:45 ` Yan-Ting Lin
2016-05-09 18:33 ` Pedro Alves
2016-05-10 9:31 ` Yan-Ting Lin
2016-05-15 9:39 ` Yan-Ting Lin
2016-06-01 11:28 ` Yao Qi
2016-06-06 15:13 ` Yan-Ting Lin
2016-06-07 15:34 ` Yao Qi
2016-06-07 16:30 ` Eli Zaretskii
2016-06-08 8:17 ` Yao Qi
2016-06-17 8:08 ` Yan-Ting Lin
2016-06-13 14:12 ` Pedro Alves
2016-06-15 8:44 ` Yan-Ting Lin
2016-06-15 10:07 ` Pedro Alves
2016-06-01 10:52 ` Yao Qi
2016-06-01 11:00 ` Yao Qi
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=861t5bd4vi.fsf@gmail.com \
--to=qiyaoltc@gmail.com \
--cc=currygt52@gmail.com \
--cc=gdb-patches@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