basic recipe building - iperf

basic recipe building - iperf

[jfabernathy]

[-- Attachment #1: Type: text/plain, Size: 5578 bytes --]

I needed to do some network performance testing on a Crownbay board and 
needed iperf in that environment.  Since I had the core-image-sato-sdk 
image created, I just booted that and took the tarball from Sourceforge 
and built it  per the readme file instructions:

./configure
make
make install

After I completed my test, I thought about why not put that in my list 
of personal recipes.  I found the previous version of iperf in the 
openembedded collection of benchmark recipes and just copied it over.  
It built and worked fine.  There were a lot of items in the .bb that I 
didn't understand, so I thought for fun I'd just try to build a recipe 
for iperf 2.0.5 and see what happened.  My recipe is simple, mostly 
taken from the openembedded 2.0.4 version had stripped down:
-----------------------------
DESCRIPTION = "Iperf is a tool to measure maximum TCP bandwidth, 
allowing the tuning of various parameters and UDP characteristics"
HOMEPAGE = "http://dast.nlanr.net/Projects/Iperf/"
SECTION = "console/network"
LICENSE = "NewBSD"
LIC_FILES_CHKSUM = "file://COPYING;md5=e8478eae9f479e39bc34975193360298"

SRC_URI = " \
     ${SOURCEFORGE_MIRROR}/iperf/iperf-${PV}.tar.gz \
            "
SRC_URI[md5sum] = "44b5536b67719f4250faed632a3cd016"
SRC_URI[sha256sum] = 
"636b4eff0431cea80667ea85a67ce4c68698760a9837e1e9d13096d20362265b"

inherit autotools*
*
-----------------------
A lot of it worked, but I seem to have an install error on the man 
files.  Can anyone see what is wrong based on the log below:

DEBUG: SITE files ['endian-little', 'bit-32', 'ix86-common', 
'common-linux', 'common-glibc', 'i586-linux', 'common']
ERROR: Function failed: do_install (see 
/build/crownbay-denzil/tmp/work/core2-poky-linux/iperf-2.0.5-r0/temp/log.do_install.12443 
for further information)
NOTE: make -j 8 
DESTDIR=/build/crownbay-denzil/tmp/work/core2-poky-linux/iperf-2.0.5-r0/image 
install
Making install in compat
make[1]: Entering directory 
`/build/crownbay-denzil/tmp/work/core2-poky-linux/iperf-2.0.5-r0/iperf-2.0.5/compat'
make[2]: Entering directory 
`/build/crownbay-denzil/tmp/work/core2-poky-linux/iperf-2.0.5-r0/iperf-2.0.5/compat'
make[2]: Nothing to be done for `install-exec-am'.
make[2]: Nothing to be done for `install-data-am'.
make[2]: Leaving directory 
`/build/crownbay-denzil/tmp/work/core2-poky-linux/iperf-2.0.5-r0/iperf-2.0.5/compat'
make[1]: Leaving directory 
`/build/crownbay-denzil/tmp/work/core2-poky-linux/iperf-2.0.5-r0/iperf-2.0.5/compat'
Making install in doc
make[1]: Entering directory 
`/build/crownbay-denzil/tmp/work/core2-poky-linux/iperf-2.0.5-r0/iperf-2.0.5/doc'
make[2]: Entering directory 
`/build/crownbay-denzil/tmp/work/core2-poky-linux/iperf-2.0.5-r0/iperf-2.0.5/doc'
make[2]: Nothing to be done for `install-exec-am'.
make[2]: Nothing to be done for `install-data-am'.
make[2]: Leaving directory 
`/build/crownbay-denzil/tmp/work/core2-poky-linux/iperf-2.0.5-r0/iperf-2.0.5/doc'
make[1]: Leaving directory 
`/build/crownbay-denzil/tmp/work/core2-poky-linux/iperf-2.0.5-r0/iperf-2.0.5/doc'
Making install in include
make[1]: Entering directory 
`/build/crownbay-denzil/tmp/work/core2-poky-linux/iperf-2.0.5-r0/iperf-2.0.5/include'
make[2]: Entering directory 
`/build/crownbay-denzil/tmp/work/core2-poky-linux/iperf-2.0.5-r0/iperf-2.0.5/include'
make[2]: Nothing to be done for `install-exec-am'.
make[2]: Nothing to be done for `install-data-am'.
make[2]: Leaving directory 
`/build/crownbay-denzil/tmp/work/core2-poky-linux/iperf-2.0.5-r0/iperf-2.0.5/include'
make[1]: Leaving directory 
`/build/crownbay-denzil/tmp/work/core2-poky-linux/iperf-2.0.5-r0/iperf-2.0.5/include'
Making install in src
make[1]: Entering directory 
`/build/crownbay-denzil/tmp/work/core2-poky-linux/iperf-2.0.5-r0/iperf-2.0.5/src'
make[2]: Entering directory 
`/build/crownbay-denzil/tmp/work/core2-poky-linux/iperf-2.0.5-r0/iperf-2.0.5/src'
test -z "/usr/bin" || /bin/mkdir -p 
"/build/crownbay-denzil/tmp/work/core2-poky-linux/iperf-2.0.5-r0/image/usr/bin"
make[2]: Nothing to be done for `install-data-am'.
   /usr/bin/install -c iperf 
'/build/crownbay-denzil/tmp/work/core2-poky-linux/iperf-2.0.5-r0/image/usr/bin'
make[2]: Leaving directory 
`/build/crownbay-denzil/tmp/work/core2-poky-linux/iperf-2.0.5-r0/iperf-2.0.5/src'
make[1]: Leaving directory 
`/build/crownbay-denzil/tmp/work/core2-poky-linux/iperf-2.0.5-r0/iperf-2.0.5/src'
Making install in man
make[1]: Entering directory 
`/build/crownbay-denzil/tmp/work/core2-poky-linux/iperf-2.0.5-r0/iperf-2.0.5/man'
make[2]: Entering directory 
`/build/crownbay-denzil/tmp/work/core2-poky-linux/iperf-2.0.5-r0/iperf-2.0.5/man'
make[2]: Nothing to be done for `install-exec-am'.
test -z "/usr/share/man/man1" || /bin/mkdir -p 
"/build/crownbay-denzil/tmp/work/core2-poky-linux/iperf-2.0.5-r0/image/usr/share/man/man1"
  /usr/bin/install -c -m 644 iperf.1 iperf.1 
'/build/crownbay-denzil/tmp/work/core2-poky-linux/iperf-2.0.5-r0/image/usr/share/man/man1'
*/usr/bin/install: will not overwrite just-created 
`/build/crownbay-denzil/tmp/work/core2-poky-linux/iperf-2.0.5-r0/image/usr/share/man/man1/iperf.1' 
with `iperf.1'
make[2]: *** [install-man1] Error 1*
make[2]: Leaving directory 
`/build/crownbay-denzil/tmp/work/core2-poky-linux/iperf-2.0.5-r0/iperf-2.0.5/man'
make[1]: *** [install-am] Error 2
make[1]: Leaving directory 
`/build/crownbay-denzil/tmp/work/core2-poky-linux/iperf-2.0.5-r0/iperf-2.0.5/man'
make: *** [install-recursive] Error 1
ERROR: oe_runmake failed

[-- Attachment #2: Type: text/html, Size: 6653 bytes --]

Re: basic recipe building - iperf

[Marc Ferland]

[-- Attachment #1: Type: text/plain, Size: 996 bytes --]

jfabernathy <jfabernathy@gmail.com> writes:

>    I needed to do some network performance testing on a Crownbay board and
>    needed iperf in that environment.  Since I had the core-image-sato-sdk
>    image created, I just booted that and took the tarball from Sourceforge
>    and built it  per the readme file instructions:
>    ./configure
>    make
>    make install
>    After I completed my test, I thought about why not put that in my list
>    of personal recipes.  I found the previous version of iperf in the
>    openembedded collection of benchmark recipes and just copied it over.
>    It built and worked fine.  There were a lot of items in the .bb that I
>    didn't understand, so I thought for fun I'd just try to build a recipe
>    for iperf 2.0.5 and see what happened.  My recipe is simple, mostly
>    taken from the openembedded 2.0.4 version had stripped down:

Hi JF,

I add the same problem you had with the man page stuff, try this patch.

Marc

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: patch --]
[-- Type: text/x-diff, Size: 257 bytes --]

diff --git iperf-2.0.5/man/Makefile.am iperf-2.0.5/man/Makefile.am
index ed97bc6..728873f 100644
--- iperf-2.0.5/man/Makefile.am
+++ iperf-2.0.5/man/Makefile.am
@@ -1,2 +1 @@
-man_MANS = iperf.1
-dist_man_MANS = $(man_MANS)
+dist_man_MANS = iperf.1

Re: basic recipe building - iperf

[jfabernathy]

On 06/18/2012 05:21 PM, Marc Ferland wrote:
> jfabernathy<jfabernathy@gmail.com>  writes:
>
>>     I needed to do some network performance testing on a Crownbay board and
>>     needed iperf in that environment.  Since I had the core-image-sato-sdk
>>     image created, I just booted that and took the tarball from Sourceforge
>>     and built it  per the readme file instructions:
>>     ./configure
>>     make
>>     make install
>>     After I completed my test, I thought about why not put that in my list
>>     of personal recipes.  I found the previous version of iperf in the
>>     openembedded collection of benchmark recipes and just copied it over.
>>     It built and worked fine.  There were a lot of items in the .bb that I
>>     didn't understand, so I thought for fun I'd just try to build a recipe
>>     for iperf 2.0.5 and see what happened.  My recipe is simple, mostly
>>     taken from the openembedded 2.0.4 version had stripped down:
> Hi JF,
>
> I add the same problem you had with the man page stuff, try this patch.
>
> Marc
thanks, that patch fixed it from a build point of view. now I'll build 
the image again and see what happens on the hardware.

Jim A

Re: basic recipe building - iperf

[James Abernathy]

[-- Attachment #1: Type: text/plain, Size: 1497 bytes --]

On Mon, Jun 18, 2012 at 5:29 PM, jfabernathy <jfabernathy@gmail.com> wrote:

>  On 06/18/2012 05:21 PM, Marc Ferland wrote:
>
>> jfabernathy<jfabernathy@gmail.**com <jfabernathy@gmail.com>>  writes:
>>
>>    I needed to do some network performance testing on a Crownbay board and
>>>    needed iperf in that environment.  Since I had the core-image-sato-sdk
>>>    image created, I just booted that and took the tarball from
>>> Sourceforge
>>>    and built it  per the readme file instructions:
>>>    ./configure
>>>    make
>>>    make install
>>>    After I completed my test, I thought about why not put that in my list
>>>    of personal recipes.  I found the previous version of iperf in the
>>>    openembedded collection of benchmark recipes and just copied it over.
>>>    It built and worked fine.  There were a lot of items in the .bb that I
>>>    didn't understand, so I thought for fun I'd just try to build a recipe
>>>    for iperf 2.0.5 and see what happened.  My recipe is simple, mostly
>>>    taken from the openembedded 2.0.4 version had stripped down:
>>>
>> Hi JF,
>>
>> I add the same problem you had with the man page stuff, try this patch.
>>
>> Marc
>>
> thanks, that patch fixed it from a build point of view. now I'll build the
> image again and see what happens on the hardware.
>
> Jim A
>
> As expected the new image booted and ran the iperf 2.0.5 just fine.  Are
there any plans to add this tool to the Yocto project??

Jim A

[-- Attachment #2: Type: text/html, Size: 2121 bytes --]

Re: basic recipe building - iperf

[Khem Raj]

[-- Attachment #1: Type: text/plain, Size: 1656 bytes --]

On Monday, June 18, 2012, James Abernathy <jfabernathy@gmail.com> wrote:
>
>
> On Mon, Jun 18, 2012 at 5:29 PM, jfabernathy <jfabernathy@gmail.com>
wrote:
>>
>> On 06/18/2012 05:21 PM, Marc Ferland wrote:
>>>
>>> jfabernathy<jfabernathy@gmail.com>  writes:
>>>
>>>>    I needed to do some network performance testing on a Crownbay board
and
>>>>    needed iperf in that environment.  Since I had the
core-image-sato-sdk
>>>>    image created, I just booted that and took the tarball from
Sourceforge
>>>>    and built it  per the readme file instructions:
>>>>    ./configure
>>>>    make
>>>>    make install
>>>>    After I completed my test, I thought about why not put that in my
list
>>>>    of personal recipes.  I found the previous version of iperf in the
>>>>    openembedded collection of benchmark recipes and just copied it
over.
>>>>    It built and worked fine.  There were a lot of items in the .bb
that I
>>>>    didn't understand, so I thought for fun I'd just try to build a
recipe
>>>>    for iperf 2.0.5 and see what happened.  My recipe is simple, mostly
>>>>    taken from the openembedded 2.0.4 version had stripped down:
>>>
>>> Hi JF,
>>>
>>> I add the same problem you had with the man page stuff, try this patch.
>>>


>>> Marc
>>
>> thanks, that patch fixed it from a build point of view. now I'll build
the image again and see what happens on the hardware.
>>
>> Jim A
>>
> As expected the new image booted and ran the iperf 2.0.5 just fine.  Are
there any plans to add this tool to the Yocto project??
>

You could have just looked into meta-oe/recipes-benchmarks
> Jim A
>

[-- Attachment #2: Type: text/html, Size: 2263 bytes --]

Re: basic recipe building - iperf

[James Abernathy]

[-- Attachment #1: Type: text/plain, Size: 2010 bytes --]

On Mon, Jun 18, 2012 at 10:40 PM, Khem Raj <raj.khem@gmail.com> wrote:

>
>
> On Monday, June 18, 2012, James Abernathy <jfabernathy@gmail.com> wrote:
> >
> >
> > On Mon, Jun 18, 2012 at 5:29 PM, jfabernathy <jfabernathy@gmail.com>
> wrote:
> >>
> >> On 06/18/2012 05:21 PM, Marc Ferland wrote:
> >>>
> >>> jfabernathy<jfabernathy@gmail.com>  writes:
> >>>
> >>>>    I needed to do some network performance testing on a Crownbay
> board and
> >>>>    needed iperf in that environment.  Since I had the
> core-image-sato-sdk
> >>>>    image created, I just booted that and took the tarball from
> Sourceforge
> >>>>    and built it  per the readme file instructions:
> >>>>    ./configure
> >>>>    make
> >>>>    make install
> >>>>    After I completed my test, I thought about why not put that in my
> list
> >>>>    of personal recipes.  I found the previous version of iperf in the
> >>>>    openembedded collection of benchmark recipes and just copied it
> over.
> >>>>    It built and worked fine.  There were a lot of items in the .bb
> that I
> >>>>    didn't understand, so I thought for fun I'd just try to build a
> recipe
> >>>>    for iperf 2.0.5 and see what happened.  My recipe is simple, mostly
> >>>>    taken from the openembedded 2.0.4 version had stripped down:
> >>>
> >>> Hi JF,
> >>>
> >>> I add the same problem you had with the man page stuff, try this patch.
> >>>
>
>
> >>> Marc
> >>
> >> thanks, that patch fixed it from a build point of view. now I'll build
> the image again and see what happens on the hardware.
> >>
> >> Jim A
> >>
> > As expected the new image booted and ran the iperf 2.0.5 just fine.  Are
> there any plans to add this tool to the Yocto project??
> >
>
> You could have just looked into meta-oe/recipes-benchmarks
> > Jim A
> >

You must have missed the earlier discussion.  I first got the iperf 2.0.4
from meta-oe, but wanted 2.0.5, so I just added it to my private collection
of apps.

Jim A

[-- Attachment #2: Type: text/html, Size: 2859 bytes --]

Re: basic recipe building - iperf

[Khem Raj]

On Tue, Jun 19, 2012 at 2:54 AM, James Abernathy <jfabernathy@gmail.com> wrote:
> You must have missed the earlier discussion.  I first got the iperf 2.0.4
> from meta-oe, but wanted 2.0.5, so I just added it to my private collection
> of apps.

you can post the update patch for meta-oe layer

Re: basic recipe building - iperf

[James Abernathy]

[-- Attachment #1: Type: text/plain, Size: 723 bytes --]

On Tue, Jun 19, 2012 at 10:20 AM, Khem Raj <raj.khem@gmail.com> wrote:

> On Tue, Jun 19, 2012 at 2:54 AM, James Abernathy <jfabernathy@gmail.com>
> wrote:
> > You must have missed the earlier discussion.  I first got the iperf 2.0.4
> > from meta-oe, but wanted 2.0.5, so I just added it to my private
> collection
> > of apps.
>
> you can post the update patch for meta-oe layer
>

I can pass along what I did for iperf 2.0.5 in Yocto, but I have no idea
what to do for OE.  All the commands in their 2.0.4, which worked when
copied to my meta-jfa directory, didn't mean much to me.  I just started
from scratch and created a new recipe based on autotools plus the patch
that Marc passed along.

Jim A

[-- Attachment #2: Type: text/html, Size: 1103 bytes --]