From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Fix external toolchain gdbserver copy path for using buildroot-generated toolchain
Date: Thu, 21 Mar 2013 09:26:09 +0100 [thread overview]
Message-ID: <20130321092609.2f9e9aeb@skate> (raw)
In-Reply-To: <B5EF724456FFB24A8C8AE88E26CE8F4B6D7F0889@G9W0753.americas.hpqcorp.net>
Dear Worth, Kevin,
On Wed, 20 Mar 2013 22:27:08 +0000, Worth, Kevin wrote:
> Thanks- I figured I could at least offer some approach to fix it, even if it wasn't ideal. :)
Sure, your investigation was very nice, it clearly showed where the
problem was.
> This approach saves me a lot of time not having to rebuild toolchains, and is relatively easy to manage.
Of course.
I'll try to remember to Cc you when I come up with a patch that fixes
this.
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2013-03-21 8:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 17:25 [Buildroot] [PATCH] Fix external toolchain gdbserver copy path for using buildroot-generated toolchain Worth, Kevin
2013-03-20 20:54 ` Thomas Petazzoni
2013-03-20 22:27 ` Worth, Kevin
2013-03-21 8:26 ` Thomas Petazzoni [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=20130321092609.2f9e9aeb@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