From: Gerrit Renker <gerrit@erg.abdn.ac.uk>
To: dccp@vger.kernel.org
Subject: Re: iperf
Date: Fri, 20 Jul 2007 12:42:47 +0000 [thread overview]
Message-ID: <200707201342.47663@strip-the-willow> (raw)
In-Reply-To: <5bc4c4570707171213v6eb89545y5970e471345cc3f8@mail.gmail.com>
Thank you for testing this - the patch had been all in one and apparently
I have made a bad job of splitting it up into separate patches.
The error is due to a missing header include (I ported UDP-Lite in 2.6.20
but system headers are not that recent), will fix that and upload a clean
patch set.
| Applying only patch #1 doesn't work... patch #2 correct the error.
| PerfSocket.cpp: In function 'void MakeSocket(thread_Settings*)':
| PerfSocket.cpp:89: error: 'IPPROTO_UDPLITE' was not declared in this scope
| make[2]: *** [PerfSocket.o] Error 1
| make[2]: Leaving directory `/root/iperf-2.0.2/src'
| make[1]: *** [all-recursive] Error 1
| make[1]: Leaving directory `/root/iperf-2.0.2'
| make: *** [all] Error 2
|
| It could be good to not have 2 iperf dccp patched version, one Ian
| patched, one Gerrit patched ?
Agree, will look at Ian's patches when I have some time and confer with Ian.
Thanks again.
next prev parent reply other threads:[~2007-07-20 12:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-17 19:13 iperf
2007-07-17 20:18 ` iperf Ian McDonald
2007-07-19 12:42 ` iperf Patrick
2007-07-19 12:58 ` iperf Gerrit Renker
2007-07-19 13:02 ` iperf Burak Gorkemli
2007-07-19 16:57 ` iperf Patrick
2007-07-19 23:39 ` iperf Ian McDonald
2007-07-19 23:41 ` iperf Ian McDonald
2007-07-19 23:45 ` iperf Ian McDonald
2007-07-20 5:00 ` iperf Ian McDonald
2007-07-20 12:35 ` iperf Gerrit Renker
2007-07-20 12:42 ` Gerrit Renker [this message]
2007-07-20 12:55 ` iperf Gerrit Renker
2007-07-20 17:53 ` iperf Gerrit Renker
2007-07-20 20:38 ` iperf Ian McDonald
2007-07-20 20:40 ` iperf Ian McDonald
2007-07-20 20:41 ` iperf Ian McDonald
2007-07-21 17:13 ` iperf Gerrit Renker
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=200707201342.47663@strip-the-willow \
--to=gerrit@erg.abdn.ac.uk \
--cc=dccp@vger.kernel.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.