All of lore.kernel.org
 help / color / mirror / Atom feed
From: jfabernathy <jfabernathy@gmail.com>
To: Marc Ferland <ferlandm@sonatest.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: basic recipe building - iperf
Date: Mon, 18 Jun 2012 17:29:45 -0400	[thread overview]
Message-ID: <4FDF9DC9.1000805@gmail.com> (raw)
In-Reply-To: <87lijkuxir.fsf@sonatest.com>

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



  reply	other threads:[~2012-06-18 21:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-18 21:01 basic recipe building - iperf jfabernathy
2012-06-18 21:21 ` Marc Ferland
2012-06-18 21:29   ` jfabernathy [this message]
2012-06-19  1:34     ` James Abernathy
2012-06-19  2:40       ` Khem Raj
2012-06-19  9:54         ` James Abernathy
2012-06-19 14:20           ` Khem Raj
2012-06-19 15:22             ` James Abernathy

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=4FDF9DC9.1000805@gmail.com \
    --to=jfabernathy@gmail.com \
    --cc=ferlandm@sonatest.com \
    --cc=yocto@yoctoproject.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.