From: Joel Sherrill <joel.sherrill@oarcorp.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Chung-Ju Wu <jasonwucj@gmail.com>,
Pedro Alves <palves@redhat.com>,
"binutils@sourceware.org" <binutils@sourceware.org>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Wei-Cheng Wang <cole945@gmail.com>,
Kuan-Lin Chen <kuanlinchentw@gmail.com>
Subject: Re: [PATCH, nds32] Exclude building gdb for nds32*-*-* target.
Date: Fri, 05 Sep 2014 19:10:00 -0000 [thread overview]
Message-ID: <540A0A9E.5080709@oarcorp.com> (raw)
In-Reply-To: <20140905170010.GA28404@adacore.com>
On 9/5/2014 12:00 PM, Joel Brobecker wrote:
>>> 2014-09-05 Chung-Ju Wu <jasonwucj@gmail.com>
>>>
>>> * configure.ac (nds32*-*-*): Disable gdb.
>>> * configure: Regenerated.
>> It looks like the part for not building gdb for or1k*-*-rtems* gets moved
>> by this patch. I know there was an issue with the initial submission of
>> that change.
>>
>> Your patch appears to correct that also. I thought the properly regenerated
>> configure had been committed. But I guess not.
>>
>> I am OK with the patch since or1k-rtems is in the same place but wanted
>> to note that the generated file had extra stuff in it for a good reason.
> We really should regenerate configure first, and then apply Chung-Ju's
> patch next. There will come a day when we will be reverting that
> patch, since hopefully GDB will be building for that target, one day.
> We don't want the revert to accidently also revert the bits that
> that resync configure with present-day configure.ac.
>
Please regenerate it and commit it. I posted asking for that a few weeks
ago. It is a top level configure and someone who touches it more routinely
should do it.
--
Joel Sherrill, Ph.D. Director of Research & Development
joel.sherrill@OARcorp.com On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (256) 722-9985
next prev parent reply other threads:[~2014-09-05 19:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-05 7:13 Chung-Ju Wu
2014-09-05 13:51 ` Joel Sherrill
2014-09-05 17:00 ` Joel Brobecker
2014-09-05 19:10 ` Joel Sherrill [this message]
2014-09-05 19:27 ` top-level configure regenerated (was: "Re: [PATCH, nds32] Exclude building gdb for nds32*-*-* target.") Joel Brobecker
2014-09-05 20:10 ` [PATCH, nds32] Exclude building gdb for nds32*-*-* target Chung-Ju Wu
2014-09-05 20:29 ` Joel Brobecker
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=540A0A9E.5080709@oarcorp.com \
--to=joel.sherrill@oarcorp.com \
--cc=binutils@sourceware.org \
--cc=brobecker@adacore.com \
--cc=cole945@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=jasonwucj@gmail.com \
--cc=kuanlinchentw@gmail.com \
--cc=palves@redhat.com \
/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