Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] buildroot: toolchain: Allow to build gdbserver when external toolchain is selected.
Date: Tue, 14 Aug 2012 14:25:40 +0200	[thread overview]
Message-ID: <20120814142540.7b0ade51@skate> (raw)
In-Reply-To: <05E9E85E39C35B4D96ED3A3190E35A10C3D786052C@LIMKCMBX1.ad.analog.com>

Hello,

Le Tue, 14 Aug 2012 12:06:38 +0100,
"Henderson, Stuart" <Stuart.Henderson@analog.com> a ?crit :

> >Well, my personal experience (and I've heard this experience from several other people has well)
> >is that to avoid problems the gdbserver version you're using should be the same as the cross-gdb
> >used to connect to this gdbserver. Therefore, it makes sense for a toolchain to provide both cross-gdb
> >*and* gdbserver, or none of them, but it doesn't make much sense to offer just cross-gdb without a
> >gdbserver. As I was mentioning before, Linaro toolchains, Sourcery CodeBench toolchains do that.
> 
> This seems reasonable, however we only support matching releases of the toolchain/u-boot/linux, so the result is much the same.
> i.e. The 2012R1 release of the toolchain is used to build the 2012R1 release of u-boot and linux.  The latter of which contains the correct version of gdbserver for the 2012R1 release of the toolchain.

I am not sure to understand: why would gdbserver be part of your
"linux" release? Linux is the kernel, was does it has to do with
gdbserver.

> However, like I said, I certainly don't have any strong objections to having gdbserver in the toolchain package as well.  I'll take a look at how other people package it and see what Sonic's thoughts are on it when we're doing the next release.

Ok, thanks!

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  parent reply	other threads:[~2012-08-14 12:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-06 11:17 [Buildroot] [PATCH 1/3] buildroot: target: Add Blackfin architecture support in configuration Sonic Zhang
2012-08-06 11:17 ` [Buildroot] [PATCH 2/2] buildroot:package: Avoids prefix absolute compiler path when external toolchain path is empty Sonic Zhang
2012-08-06 12:50   ` Thomas Petazzoni
2012-08-06 11:17 ` [Buildroot] [PATCH 3/3] buildroot: toolchain: Allow to build gdbserver when external toolchain is selected Sonic Zhang
2012-08-06 12:54   ` Thomas Petazzoni
     [not found]     ` <DB904C5425BA6F4E8424B3B51A1414D1714D28600B@NWD2CMBX1.ad.analog.com>
2012-08-08  2:39       ` Sonic Zhang
     [not found]         ` <05E9E85E39C35B4D96ED3A3190E35A10C3D77B0E41@LIMKCMBX1.ad.analog.com>
2012-08-08 19:23           ` Thomas Petazzoni
     [not found]             ` <05E9E85E39C35B4D96ED3A3190E35A10C3D786052C@LIMKCMBX1.ad.analog.com>
2012-08-14 12:25               ` Thomas Petazzoni [this message]
2012-08-06 12:36 ` [Buildroot] [PATCH 1/3] buildroot: target: Add Blackfin architecture support in configuration Thomas Petazzoni
     [not found]   ` <DB904C5425BA6F4E8424B3B51A1414D1714D286001@NWD2CMBX1.ad.analog.com>
2012-08-08  2:42     ` Sonic Zhang

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=20120814142540.7b0ade51@skate \
    --to=thomas.petazzoni@free-electrons.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