[Buildroot] Problems building iotop

[Buildroot] Problems building iotop

[Linux User]

Hi All,

I am getting,

make iotop
make: *** No rule to make target `iotop'.  Stop.

I added iotop to my /package/ dir. I update Config.in in /package/

But I get above error. The build root version, I have, it doesn't have
iotop, so I grabbed it from the newer buildroot repo. I did the same
exercise with ftop and that builds fine.

Can some one pls help ?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20170511/32a65e11/attachment.html>

[Buildroot] Problems building iotop

[Thomas Petazzoni]

Hello,

On Thu, 11 May 2017 11:45:59 -0400, Linux User wrote:

> I am getting,
> 
> make iotop
> make: *** No rule to make target `iotop'.  Stop.

Most likely you haven't created a Buildroot configuration.

Have you run "make menuconfig", define the Linux system you want to
build, and then run "make" ?

If not, then please read some documentation about Buildroot :-)

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

[Buildroot] Problems building iotop

[Thomas Petazzoni]

Hello,

Please keep the Buildroot mailing list in Cc, thanks.

On Thu, 11 May 2017 13:42:04 -0400, Linux User wrote:
> Oh my buildroot is already setup. I am build everything else just fine but
> iotop.
> 
> Below is the example of ftop working just fine. But iotop wont.

Which Buildroot version are you using?

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

[Buildroot] Problems building iotop

[Linux User]

Hi Thomas,

Posting again, with the maillist in cc.

I am using 2013 version of BR.

Oh my buildroot is already setup. I am build everything else just fine but
iotop.

I brought ftop from latest BR to my BR, added to the package dir, update
the Config.in and life is good. Life is not so good when I do the same with
iotop. I cant figure why.

Below is the example of ftop working just fine. But iotop wont.

 make ftop-dirclean
rm -Rf /home//PNC_Projects/TR3000/Firmware/Analog_IM/platforms/
som/src/output/build/ftop-1.0
@amuscorbld:~/PNC_Projects/TR3000/Firmware/Analog_IM/platforms/som/src$
make ftop-rebuild
rm -f /home//PNC_Projects/TR3000/Firmware/Analog_IM/platforms/
som/src/output/build/ftop-1.0/.stamp_built
rm -f /home//PNC_Projects/TR3000/Firmware/Analog_IM/platforms/
som/src/output/build/ftop-1.0/.stamp_staging_installed
rm -f /home//PNC_Projects/TR3000/Firmware/Analog_IM/platforms/
som/src/output/build/ftop-1.0/.stamp_target_installed
rm -f /home//PNC_Projects/TR3000/Firmware/Analog_IM/platforms/
som/src/output/build/ftop-1.0/.stamp_images_installed
rm -f /home//PNC_Projects/TR3000/Firmware/Analog_IM/platforms/
som/src/output/build/ftop-1.0/.stamp_host_installed
>>> ftop 1.0 Extracting
gzip -d -c /home//PNC_Projects/TR3000/Firmware/Analog_IM/platforms/som/src/dl/ftop-1.0.tar.gz
| tar --strip-components=1 -C /home//PNC_Projects/TR3000/
Firmware/Analog_IM/platforms/som/src/output/build/ftop-1.0  -xf -
>>> ftop 1.0 Patching package//ftop

Applying 0001-overflow.patch using patch:
patching file src/ftop.c
>>> ftop 1.0 Updating config.sub and config.guess
for file in config.guess config.sub; do for i in $(find
/home//PNC_Projects/TR3000/Firmware/Analog_IM/platforms/som/src/output/build/ftop-1.0
-name $file); do cp support/gnuconfig/$file $i; done; done

On Thu, May 11, 2017 at 11:49 AM, Thomas Petazzoni <
thomas.petazzoni@free-electrons.com> wrote:

> Hello,
>
> On Thu, 11 May 2017 11:45:59 -0400, Linux User wrote:
>
> > I am getting,
> >
> > make iotop
> > make: *** No rule to make target `iotop'.  Stop.
>
> Most likely you haven't created a Buildroot configuration.
>
> Have you run "make menuconfig", define the Linux system you want to
> build, and then run "make" ?
>
> If not, then please read some documentation about Buildroot :-)
>
> Thomas
> --
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux and Kernel engineering
> http://free-electrons.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20170512/d4287852/attachment.html>

[Buildroot] Problems building iotop

[Thomas Petazzoni]

Hello,

On Fri, 12 May 2017 09:51:57 -0400, Linux User wrote:

> Posting again, with the maillist in cc.
> 
> I am using 2013 version of BR.
> 
> Oh my buildroot is already setup. I am build everything else just fine but
> iotop.

Buildroot 2013 is really old. The iotop package was added in Buildroot
2015.05.

Best regards,

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

[Buildroot] Problems building iotop

[Linux User]

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.

On Fri, May 12, 2017 at 10:13 AM, Thomas Petazzoni <
thomas.petazzoni@free-electrons.com> wrote:

> Hello,
>
> On Fri, 12 May 2017 09:51:57 -0400, Linux User wrote:
>
> > Posting again, with the maillist in cc.
> >
> > I am using 2013 version of BR.
> >
> > Oh my buildroot is already setup. I am build everything else just fine
> but
> > iotop.
>
> Buildroot 2013 is really old. The iotop package was added in Buildroot
> 2015.05.
>
> Best regards,
>
> Thomas
> --
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux and Kernel engineering
> http://free-electrons.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20170512/64d92946/attachment.html>

[Buildroot] Problems building iotop

[Steve Kenton]

Be aware that the dependencies can be quite complex. I have had problems 
even when slipstreaming things like xorriso-1.4.2 to to xorriso-1.4.4.

To add a package do something along these lines:

Construct a directory for the package formatted like those already in 
packages directory, see the Buildroot documentation. In the example 
below it contains only Config.in  and libltc.mk because the hash file 
can be omitted for testing.

Add it to the packages/Config.in file doing something like the below:

# My attempt to add libltc as a buildroot package for future use
# Note that libltc has not yet been submitted to upstream buildroot
sed --in-place '/    source "package\/liblo\/Config.in"/a \ source 
"package/libltc/Config.in"' package/Config.in
rm --recursive --force package/libltc
mv ../libltc package/


make menuconfig should now allow you to select it.

Good luck.

Steve Kenton



On 05/12/2017 05:31 PM, 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.
>
> On Fri, May 12, 2017 at 10:13 AM, Thomas Petazzoni 
> <thomas.petazzoni@free-electrons.com 
> <mailto:thomas.petazzoni@free-electrons.com>> wrote:
>
>     Hello,
>
>     On Fri, 12 May 2017 09:51:57 -0400, Linux User wrote:
>
>     > Posting again, with the maillist in cc.
>     >
>     > I am using 2013 version of BR.
>     >
>     > Oh my buildroot is already setup. I am build everything else
>     just fine but
>     > iotop.
>
>     Buildroot 2013 is really old. The iotop package was added in Buildroot
>     2015.05.
>
>     Best regards,
>
>     Thomas
>     --
>     Thomas Petazzoni, CTO, Free Electrons
>     Embedded Linux and Kernel engineering
>     http://free-electrons.com
>     <https://urldefense.proofpoint.com/v2/url?u=http-3A__free-2Delectrons.com&d=DwMFaQ&c=qKdtBuuu6dQK9MsRUVJ2DPXW6oayO8fu4TfEHS8sGNk&r=XPAqbAKvOH6479pBB2izug&m=gs4abqpaeB6ilihhJKXUWlbNxCBfs1ajB_PcNyC4kg4&s=YdV0uqzu2uAKfmQa1aln7P7qKzKP4l76AYL7JkiCFUw&e=>
>
>
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20170512/c5fea06f/attachment.html>

[Buildroot] Problems building iotop

[Thomas Petazzoni]

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