Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Alan Hayward <Alan.Hayward@arm.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: Philipp Rudo <prudo@linux.vnet.ibm.com>,
	"gdb-patches@sourceware.org"	<gdb-patches@sourceware.org>,
	nd <nd@arm.com>
Subject: Re: [PATCH] Move arch/tdesc.h to common/common-tdesc.h
Date: Wed, 07 Feb 2018 10:31:00 -0000	[thread overview]
Message-ID: <DF317962-DAFE-494A-A3D2-BB40DB216D80@arm.com> (raw)
In-Reply-To: <CAH=s-PNhQ_s5PhoFZQqcutao_GZXt75OX5GitaFKv-gOGdbEag@mail.gmail.com>



> On 7 Feb 2018, at 09:32, Yao Qi <qiyaoltc@gmail.com> wrote:
> 
> On Wed, Feb 7, 2018 at 9:02 AM, Philipp Rudo <prudo@linux.vnet.ibm.com> wrote:
>> Hi Yao,
>> 
>> sorry, i misunderstood you.  You are right cleaning up gdbservers Makefile
>> would be better.  I'm currently pretty occupied, but I can give it a try later
>> on.  Let's see what I can do.
>> 
> 
> Never mind, I do think I misread email everyday :)
> 
> FAOD, both GDB and GDBserver needs clean up.  Something had already
> happened on this topic,
> 
>  f38307f [RFC] Replicate src dir in build dir
> 
> we have arch/ directory in gdb and gdbserver build tree after this patch.  This
> patch was written in a way that is easy to create other directories.  I didn't
> follow up this patch to create nat/ target/ etc directories in gdb and gdbserver
> build tree because of other assignments.  Later, Tom changed it
> 
>  b22c88c A simpler way to make the "arch" build directory
> 
> I didn't follow that patch series, so I don't know how to extend existing
> mechanism to create other directories.  Note that Tom's patch only changes
> gdb, gdbserver still uses the approach added in f38307f.  I hope both gdb
> and gdbserver have the same approach ultimately.
> 

Agree with the discussion above. Having a common/ dir in the build directory
Would be nice.
Been taking a quick look at this today, and I think I’ve got something working.
Will post as a new patch a bit later.

Alan.



  reply	other threads:[~2018-02-07 10:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-31 13:40 Alan Hayward
2018-02-01 11:19 ` Philipp Rudo
2018-02-01 13:19   ` Alan Hayward
2018-02-06 16:28     ` Yao Qi
2018-02-06 17:56       ` Philipp Rudo
2018-02-06 21:24         ` Yao Qi
2018-02-07  9:02           ` Philipp Rudo
2018-02-07  9:32             ` Yao Qi
2018-02-07 10:31               ` Alan Hayward [this message]
2018-02-20 11:56                 ` Alan Hayward
2018-02-21 12:27                   ` Philipp Rudo
2018-02-22 14:17                   ` Yao Qi
2018-02-27 12:13                   ` 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=DF317962-DAFE-494A-A3D2-BB40DB216D80@arm.com \
    --to=alan.hayward@arm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=nd@arm.com \
    --cc=prudo@linux.vnet.ibm.com \
    --cc=qiyaoltc@gmail.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