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] Problems building iotop
Date: Fri, 12 May 2017 21:19:10 +0200	[thread overview]
Message-ID: <20170512211910.4919fb79@free-electrons.com> (raw)
In-Reply-To: <CA+12NBL_ABjQZETEs4xUVZf8kcCW4+Qm1KEafXxbZi7o1VzK1g@mail.gmail.com>

Hello,

On Fri, 12 May 2017 13:31:57 -0400, Linux User wrote:

> I do understand that. But for 1 package, I dont want to upgrade to entire
> BR. What I am trying to do should be possible. Isn't it ? If you can give
> me some pointers, I dont mind, working on it.

Well, you can certainly backport the package. But beware that a simple
copy of package/iotop/ will most likely not work. Indeed between a
Buildroot of ~2013 (that you are using) and a Buildroot of 2015 (which
has iotop), we most likely made some changes in the package
infrastructure. So you will have to re-adapt iotop.mk.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

      parent reply	other threads:[~2017-05-12 19:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-11 15:45 [Buildroot] Problems building iotop Linux User
2017-05-11 15:49 ` Thomas Petazzoni
     [not found]   ` <CA+12NBKMFcGUA_ipbN-FOBgXDcS_aVPiziRmt2k9Q9C17SE++Q@mail.gmail.com>
2017-05-11 20:15     ` Thomas Petazzoni
2017-05-12 13:51   ` Linux User
2017-05-12 14:13     ` Thomas Petazzoni
2017-05-12 17:31       ` Linux User
2017-05-12 19:10         ` Steve Kenton
2017-05-12 19:19         ` 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=20170512211910.4919fb79@free-electrons.com \
    --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