All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] gdbserver located outside *SYSROOT
Date: Mon, 16 Mar 2015 18:05:53 +0100	[thread overview]
Message-ID: <20150316170553.GE4271@free.fr> (raw)
In-Reply-To: <1426520722.19530.26.camel@synopsys.com>

Alexey, All,

On 2015-03-16 15:45 +0000, Alexey Brodkin spake thusly:
> 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?

Well, other toolchains usually put gdbserver in the sysroot or the
arch-sysroot, so it looks like a proper location to put it.

crosstool-NG toolchains put it in a specific directory, 'debug-root',
which stands side-by-side with the sysroot (not necessarily the best
move I did with that, but that's supported by Buildroot).

gdbserver, being a target executable, really has no place in the
top-level bin/ directory. It would be good to move it out of there.

>  [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)?

Yes, using _FIXUP_CMDS is a good solution, and is made exactly for this
kind of situation. Just copy in into sysroot/bin/ and you're done.

Regards,
Yann E. MORIN.

> -Alexey
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

      reply	other threads:[~2015-03-16 17:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-16 15:45 [Buildroot] gdbserver located outside *SYSROOT Alexey Brodkin
2015-03-16 17:05 ` Yann E. MORIN [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=20150316170553.GE4271@free.fr \
    --to=yann.morin.1998@free.fr \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.