Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: oza Pawandeep <oza.pawandeep@gmail.com>
To: Yao Qi <yao@codesourcery.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Makefile.in includes linux-record.c to be common for all arch. (arm-reversible>phase-3)
Date: Thu, 07 Jun 2012 17:20:00 -0000	[thread overview]
Message-ID: <CAK1A=4yHpAXYsBjFGJdEsOq_w6JSwCSjq3hGX=G-rAYcSbZ5OQ@mail.gmail.com> (raw)
In-Reply-To: <4FD0AF8C.2040908@codesourcery.com>

ok. sure will add it there as it is not currently linking.
but on the contrary 'record.o' is also under the same section
COMMON_OBS, which is also not required where no record support.
hence it is confusing.

Regards,
Oza.

On Thu, Jun 7, 2012 at 7:11 PM, Yao Qi <yao@codesourcery.com> wrote:
> On 06/07/2012 11:51 AM, oza Pawandeep wrote:
>> linux-record.o is added under COMMON_OBS, now <arch>-linux-tdep.c compiles.
>> ok to commit ?
>
> I feel it is useless to link linux-record.o for the ports t, hat don't
> support record at all.
>
> If you want to support record in arm-linux, gdb/configure.tgt is the
> right place to modify, IMO.  You need to add "linux-record.o" into
> gdb_target_obs in "arm*-*-linux*)".
>
> --
> Yao (齐尧)


  reply	other threads:[~2012-06-07 17:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-07  3:51 oza Pawandeep
2012-06-07 13:41 ` Yao Qi
2012-06-07 17:20   ` oza Pawandeep [this message]
2012-06-08  6:09     ` Matt Rice
2012-06-08 12:45       ` oza Pawandeep
2012-06-18  9:08         ` oza Pawandeep
2012-06-18  9:24           ` Yao Qi
2012-06-18 11:49             ` oza Pawandeep
2012-06-18 14:22               ` Hui Zhu
     [not found]                 ` <CAK1A=4wdqiGCGGQuQHmDB19O=RfjttaG9M83KpBkuUyQPd=0qQ@mail.gmail.com>
2012-06-18 18:55                   ` oza Pawandeep
2012-06-19  1:35                   ` Hui Zhu
2012-06-19  5:13                     ` oza Pawandeep
2012-06-19 16:03                       ` oza Pawandeep

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='CAK1A=4yHpAXYsBjFGJdEsOq_w6JSwCSjq3hGX=G-rAYcSbZ5OQ@mail.gmail.com' \
    --to=oza.pawandeep@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=yao@codesourcery.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