Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] toolchain-external: fix gdbserver copying for external arc-2014.12 tools
Date: Wed, 29 Jul 2015 13:01:30 +0000	[thread overview]
Message-ID: <1438174889.16101.0.camel@synopsys.com> (raw)
In-Reply-To: <20150711104535.3b2c1bfd@free-electrons.com>

Thomas, Romain,

On Sat, 2015-07-11 at 10:45 +0200, Thomas Petazzoni wrote:
> Dear Romain Naour,
> 
> On Sat, 11 Jul 2015 09:47:54 +0200, Romain Naour wrote:
> 
> > Le 25/03/2015 09:11, Alexey Brodkin a ?crit :
> > > Historically in pre-built ARC GNU tools gdbserver is located in
> > > top-level "target-bin" folder.
> > > 
> > > Because of that fact if BR2_TOOLCHAIN_EXTERNAL_GDB_SERVER_COPY is
> > > selected Buildroot won't find gdbserver (it looks within
> > > SYSROOT/ARCH_SYSROOT folder).
> > > 
> > > Simplest solution is to use TOOLCHAIN_EXTERNAL_FIXUP_CMDS where copy
> > > gdbserver from "target-bin" folder into SYSROOT/usr/bin.
> > 
> > Since this patch, the arc 2014.12 prebuild toolchain as been marked as broken
> > [1]. This patch is still needed ?
> 
> I'd say no for the moment, I'll mark the patch as Rejected for now.

Indeed this patch is no longer required because in arc-2015.06 toolchain
we put gdbserver in proper place  "sysroot/usr/bin".

-Alexey

      reply	other threads:[~2015-07-29 13:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-25  8:11 [Buildroot] [PATCH v2] toolchain-external: fix gdbserver copying for external arc-2014.12 tools Alexey Brodkin
2015-07-11  7:47 ` Romain Naour
2015-07-11  8:45   ` Thomas Petazzoni
2015-07-29 13:01     ` Alexey Brodkin [this message]

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=1438174889.16101.0.camel@synopsys.com \
    --to=alexey.brodkin@synopsys.com \
    --cc=buildroot@busybox.net \
    /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