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] Fwd: How to enable Oprofile while using external tool chain?
Date: Wed, 25 May 2011 11:53:08 +0200	[thread overview]
Message-ID: <20110525115308.30f1c7a2@surf> (raw)
In-Reply-To: <BANLkTik7bUHUein61uU18019RGZKeVw2qw@mail.gmail.com>

Hello Beno?t,

Please keep the Buildroot list in Cc for Buildroot-related messages
(or, alternatively, use french for send me private messages ! :-)).

On Wed, 25 May 2011 11:40:10 +0200
Beno?t Mauduit <benoit.mauduit@gmail.com> wrote:

> > Your patch says that it builds a host-binutils, but it's wrong:
> > what it builds is binutils for the target.
> 
> That's why I put quotes on "host" in my commit message.

Yes, that's what I understood from your quotes.

> > Otherwise, would be great to have a proper patch that makes this
> > possible, and that we could merge into Buildroot.
> 
> I've made this patch quickly and know it is ugly. Anyway, i will try
> to update it when i have the time and post it here.

No problem with ugly preliminary patches. I do the same for new
features / complex features. And solving that binutils problem is not
that simple.

Regards,

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:[~2011-05-25  9:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-25  7:31 [Buildroot] How to enable Oprofile while using external tool chain? Bob Liu
     [not found] ` <BANLkTik5J8hTD_OvXrTZ3KYgHGUGPZqGqg@mail.gmail.com>
2011-05-25  8:28   ` [Buildroot] Fwd: " Benoît Mauduit
2011-05-25  8:46     ` Thomas Petazzoni
     [not found]       ` <BANLkTik7bUHUein61uU18019RGZKeVw2qw@mail.gmail.com>
2011-05-25  9:53         ` Thomas Petazzoni [this message]
2011-05-25  8:30 ` [Buildroot] " Thomas Petazzoni

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=20110525115308.30f1c7a2@surf \
    --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