Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] gdbserver located outside *SYSROOT
Date: Mon, 16 Mar 2015 15:45:22 +0000	[thread overview]
Message-ID: <1426520722.19530.26.camel@synopsys.com> (raw)

Hi Thomas,

I just realized that in pre-built ARC GNU tools gdbserver resides
outside of SYSROOT_DIR/ARCH_SYSROOT_DIR.

Historically we put gdbserver in top-level "target-bin" folder.

And I'm wondering how to deal with it to get proper copy of it onto
target if BR2_TOOLCHAIN_EXTERNAL_GDB_SERVER_COPY is selected.

 [1] Do we really need to re-consider placement of gdbserver for our
next release of GNU tools for ARC? Then what could be the best location?

 [2] Will setup of TOOLCHAIN_EXTERNAL_FIXUP_CMDS to cp gdbserver to some
related location be a good solution of the problem (if so then maybe
forget about [1] at least until we have multilibbed tools for ARC)?

-Alexey

             reply	other threads:[~2015-03-16 15:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-16 15:45 Alexey Brodkin [this message]
2015-03-16 17:05 ` [Buildroot] gdbserver located outside *SYSROOT Yann E. MORIN

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=1426520722.19530.26.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