Re: [yocto] [META-OE][PATCH] iperf 2.0.5 + fix for minor bug while cross-compiling
On Mon, Mar 18, 2013 at 12:41:32PM +0100, Simon Egli wrote: > Please see attached my patch to iperf 2.0.5 + fix > I hope this may be of use for someone and that it will be integrated in > to yocto master And please read README in meta-oe checkout and send v2 to right ML. > From 5a46a34945539ac46046bec9534322c09ff0896a Mon Sep 17 00:00:00 2001 > From: Simon Egli > Date: Mon, 18 Mar 2013 12:37:20 +0100 > Subject: [PATCH 1/2] Recipe for iperf 2.0.5 > > Signed-off-by: Simon Egli > --- > meta-oe/recipes-benchmark/iperf/iperf_2.0.5.bb | 21 + > 1 file changed, 21 insertions(+) > create mode 100644 meta-oe/recipes-benchmark/iperf/iperf_2.0.5.bb > > diff --git a/meta-oe/recipes-benchmark/iperf/iperf_2.0.5.bb > b/meta-oe/recipes-benchmark/iperf/iperf_2.0.5.bb > new file mode 100644 > index 000..3f93ee5 > --- /dev/null > +++ b/meta-oe/recipes-benchmark/iperf/iperf_2.0.5.bb > @@ -0,0 +1,21 @@ > +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 \ > + file://0001-Fixing-special-format-bug-with-bitbake.patch \ > + " > + > + > +SRC_URI[md5sum] = "44b5536b67719f4250faed632a3cd016" > +SRC_URI[sha256sum] = > "636b4eff0431cea80667ea85a67ce4c68698760a9837e1e9d13096d20362265b" > + > +inherit autotools > + > +S="${WORKDIR}/iperf-${PV}" > + > +EXTRA_OECONF = "--exec-prefix=${STAGING_DIR_HOST}${layout_exec_prefix}" > + > -- > 1.7.9.5 > > From 85fdd92a41626e821c98251ee13a0dd8f280de40 Mon Sep 17 00:00:00 2001 > From: Simon Egli > Date: Mon, 18 Mar 2013 12:37:40 +0100 > Subject: [PATCH 2/2] Fixing special format bug with bitbake > > On overo (native) we get HAVE_QUAD_SUPPORT, but don't seem with bitbake. > This leads to "iperf -s -u -y c" returning empty bandwith and jitter, > because of formatting error. > Didn't seem to work with "'CFLAGS += "-HAVE_QUAD_SUPPORT"', because of > configure error, > so giving iperf HAVE_QUAD_SUPPORT in Locale.c > > Signed-off-by: Simon Egli > --- > ...01-Fixing-special-format-bug-with-bitbake.patch | 31 > > 1 file changed, 31 insertions(+) > create mode 100644 > meta-oe/recipes-benchmark/iperf/iperf-2.0.5/0001-Fixing-special-format-bug-with-bitbake.patch > > diff --git > a/meta-oe/recipes-benchmark/iperf/iperf-2.0.5/0001-Fixing-special-format-bug-with-bitbake.patch > > b/meta-oe/recipes-benchmark/iperf/iperf-2.0.5/0001-Fixing-special-format-bug-with-bitbake.patch > new file mode 100644 > index 000..fb04cd7 > --- /dev/null > +++ > b/meta-oe/recipes-benchmark/iperf/iperf-2.0.5/0001-Fixing-special-format-bug-with-bitbake.patch > @@ -0,0 +1,31 @@ > +From 8f359740e9d8b4b18c83873aab6d80b40e36beaf Mon Sep 17 00:00:00 2001 > +From: Simon Egli > +Date: Mon, 18 Mar 2013 12:30:12 +0100 > +Subject: [PATCH] Fixing special format bug with bitbake > + > +On overo (native) we get HAVE_QUAD_SUPPORT, but don't seem with bitbake. > +This leads to "iperf -s -u -y c" returning empty bandwith and jitter, > +because of formatting error. > +Didn't seem to work with "'CFLAGS += "-HAVE_QUAD_SUPPORT"', because of > configure error, > +so giving iperf HAVE_QUAD_SUPPORT in Locale.c > + > +Signed-off-by: Simon Egli > +--- > + src/Locale.c |1 + > + 1 file changed, 1 insertion(+) > + > +diff --git a/src/Locale.c b/src/Locale.c > +index b5d42b1..f0e10b6 100644 > +--- a/src/Locale.c > b/src/Locale.c > +@@ -238,6 +238,7 @@ const char server_reporting[] = > + const char reportCSV_peer[] = > + "%s,%u,%s,%u"; > + > ++#define HAVE_QUAD_SUPPORT > + #ifdef HAVE_QUAD_SUPPORT > + #ifdef HAVE_PRINTF_QD > + const char reportCSV_bw_format[] = > +-- > +1.7.9.5 > + > -- > 1.7.9.5 > -- Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com signature.asc Description: Digital signature ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [META-OE][PATCH] iperf 2.0.5 + fix for minor bug while cross-compiling
On Mon, Mar 18, 2013 at 12:41:32PM +0100, Simon Egli wrote: > Please see attached my patch to iperf 2.0.5 + fix > I hope this may be of use for someone and that it will be integrated in > to yocto master > > Greetings, > > Simon > From 5a46a34945539ac46046bec9534322c09ff0896a Mon Sep 17 00:00:00 2001 > From: Simon Egli > Date: Mon, 18 Mar 2013 12:37:20 +0100 > Subject: [PATCH 1/2] Recipe for iperf 2.0.5 > > Signed-off-by: Simon Egli > --- > meta-oe/recipes-benchmark/iperf/iperf_2.0.5.bb | 21 + > 1 file changed, 21 insertions(+) > create mode 100644 meta-oe/recipes-benchmark/iperf/iperf_2.0.5.bb > > diff --git a/meta-oe/recipes-benchmark/iperf/iperf_2.0.5.bb > b/meta-oe/recipes-benchmark/iperf/iperf_2.0.5.bb > new file mode 100644 > index 000..3f93ee5 > --- /dev/null > +++ b/meta-oe/recipes-benchmark/iperf/iperf_2.0.5.bb > @@ -0,0 +1,21 @@ > +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 \ > + file://0001-Fixing-special-format-bug-with-bitbake.patch \ > + " > + > + > +SRC_URI[md5sum] = "44b5536b67719f4250faed632a3cd016" > +SRC_URI[sha256sum] = > "636b4eff0431cea80667ea85a67ce4c68698760a9837e1e9d13096d20362265b" > + > +inherit autotools > + > +S="${WORKDIR}/iperf-${PV}" > + > +EXTRA_OECONF = "--exec-prefix=${STAGING_DIR_HOST}${layout_exec_prefix}" > + > -- > 1.7.9.5 > Why your patch adds iperf_2.0.5.bb instead of upgrading existing 2.0.4? > From 85fdd92a41626e821c98251ee13a0dd8f280de40 Mon Sep 17 00:00:00 2001 > From: Simon Egli > Date: Mon, 18 Mar 2013 12:37:40 +0100 > Subject: [PATCH 2/2] Fixing special format bug with bitbake > > On overo (native) we get HAVE_QUAD_SUPPORT, but don't seem with bitbake. > This leads to "iperf -s -u -y c" returning empty bandwith and jitter, > because of formatting error. > Didn't seem to work with "'CFLAGS += "-HAVE_QUAD_SUPPORT"', because of > configure error, Does it fail with -DHAVE_QUAD_SUPPORT too? > so giving iperf HAVE_QUAD_SUPPORT in Locale.c > > Signed-off-by: Simon Egli > --- > ...01-Fixing-special-format-bug-with-bitbake.patch | 31 > > 1 file changed, 31 insertions(+) > create mode 100644 > meta-oe/recipes-benchmark/iperf/iperf-2.0.5/0001-Fixing-special-format-bug-with-bitbake.patch > > diff --git > a/meta-oe/recipes-benchmark/iperf/iperf-2.0.5/0001-Fixing-special-format-bug-with-bitbake.patch > > b/meta-oe/recipes-benchmark/iperf/iperf-2.0.5/0001-Fixing-special-format-bug-with-bitbake.patch > new file mode 100644 > index 000..fb04cd7 > --- /dev/null > +++ > b/meta-oe/recipes-benchmark/iperf/iperf-2.0.5/0001-Fixing-special-format-bug-with-bitbake.patch > @@ -0,0 +1,31 @@ > +From 8f359740e9d8b4b18c83873aab6d80b40e36beaf Mon Sep 17 00:00:00 2001 > +From: Simon Egli > +Date: Mon, 18 Mar 2013 12:30:12 +0100 > +Subject: [PATCH] Fixing special format bug with bitbake > + > +On overo (native) we get HAVE_QUAD_SUPPORT, but don't seem with bitbake. > +This leads to "iperf -s -u -y c" returning empty bandwith and jitter, > +because of formatting error. > +Didn't seem to work with "'CFLAGS += "-HAVE_QUAD_SUPPORT"', because of > configure error, > +so giving iperf HAVE_QUAD_SUPPORT in Locale.c > + > +Signed-off-by: Simon Egli > +--- > + src/Locale.c |1 + > + 1 file changed, 1 insertion(+) > + > +diff --git a/src/Locale.c b/src/Locale.c > +index b5d42b1..f0e10b6 100644 > +--- a/src/Locale.c > b/src/Locale.c > +@@ -238,6 +238,7 @@ const char server_reporting[] = > + const char reportCSV_peer[] = > + "%s,%u,%s,%u"; > + > ++#define HAVE_QUAD_SUPPORT > + #ifdef HAVE_QUAD_SUPPORT > + #ifdef HAVE_PRINTF_QD > + const char reportCSV_bw_format[] = > +-- > +1.7.9.5 > + > -- > 1.7.9.5 > -- Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com signature.asc Description: Digital signature ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto