Re: [yocto] bitbaking error with hello world recipe

[ChenQi]

On 03/19/2013 10:11 AM, Sudhangathan B S wrote:

Hello, I'm new to oe and yocto project..

I simply created my own meta-dese layer, added it in layers.conf

*This is the structure of meta-dese folder:*
*
*
suan@edcn400:~/pokybuilds$ ls -R /home/suan/poky/meta-dese/
/home/suan/poky/meta-dese/:
conf  recipes-dese

/home/suan/poky/meta-dese/conf:
layer.conf

/home/suan/poky/meta-dese/recipes-dese:
files hello-1.0.bb 


try renaming it to hello_1.0.bb


/home/suan/poky/meta-dese/recipes-dese/files:
hello.c
suan@edcn400:~/pokybuilds$


*I have quoted the output here:*
*
*
suan@edcn400:~/pokybuilds$ bitbake core-image-minimal
Loading cache: 100% 
|###| 
ETA:  00:00:00

Loaded 1118 entries from dependency cache.
WARNING: No bb files matched BBFILE_PATTERN_dese 
'^/home/suan/poky/meta-dese/'


Build Configuration:
BB_VERSION= "1.17.1"
BUILD_SYS = "i686-linux"
NATIVELSBSTRING   = "Ubuntu-12.04"
TARGET_SYS= "arm-poky-linux-gnueabi"
MACHINE   = "qemuarm"
DISTRO= "poky"
DISTRO_VERSION= "1.3+snapshot-20130319"
TUNE_FEATURES = "armv5 thumb dsp"
TARGET_FPU= "soft"
meta
meta-yocto
meta-yocto-bsp
meta-dese = "master:164a4cb2fc64e76836182ad2d412343a7b26b964"

NOTE: Resolving any missing task queue dependencies
ERROR: Nothing RPROVIDES 'hello' (but 
/home/suan/poky/meta/recipes-core/images/core-image-minimal.bb 
 RDEPENDS on or otherwise requires it)

NOTE: Runtime target 'hello' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['hello']
ERROR: Required build target 'core-image-minimal' has no buildable 
providers.
Missing or unbuildable dependency chain was: ['core-image-minimal', 
'hello']


Summary: There was 1 WARNING message shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit 
code.

suan@edcn400:~/pokybuilds$

How can I proceed from here..??
-
Sudhangathan BS
Ph:(+91) 9731-905-205
-


___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-qt3][PATCH] layer.conf: avoid unnecessary early expansion with :=

[Christopher Larson]

From: Christopher Larson 

bitbake handles immediate expansions of LAYERDIR for us automatically.

Signed-off-by: Christopher Larson 
---
 conf/layer.conf | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/conf/layer.conf b/conf/layer.conf
index f4597db..84ab5f7 100644
--- a/conf/layer.conf
+++ b/conf/layer.conf
@@ -1,10 +1,10 @@
 # We have a conf and classes directory, add to BBPATH
-BBPATH := "${BBPATH}:${LAYERDIR}"
+BBPATH .= ":${LAYERDIR}"
 
 # We have a packages directory, add to BBFILES
-BBFILES := "${BBFILES} ${LAYERDIR}/recipes-*/*/*.bb"
+BBFILES += "${LAYERDIR}/recipes-*/*/*.bb"
 
 BBFILE_COLLECTIONS += "qt3"
-BBFILE_PATTERN_qt3 := "^${LAYERDIR}/"
+BBFILE_PATTERN_qt3 = "^${LAYERDIR}/"
 BBFILE_PRIORITY_qt3 = "6"
 
-- 
1.8.2

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-xilinx][PATCH] layer.conf: avoid unnecessary early expansion with :=

[Christopher Larson]

From: Christopher Larson 

bitbake handles immediate expansions of LAYERDIR for us automatically.

Signed-off-by: Christopher Larson 
---
 conf/layer.conf | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/conf/layer.conf b/conf/layer.conf
index d1a1a84..f415d2f 100644
--- a/conf/layer.conf
+++ b/conf/layer.conf
@@ -1,12 +1,12 @@
 # We have a conf and classes directory, add to BBPATH
-BBPATH := "${BBPATH}:${LAYERDIR}"
+BBPATH .= ":${LAYERDIR}"
 
 require conf/distro/include/xilinx-default-revisions.inc
 
 # We have a packages directory, add to BBFILES
-BBFILES := "${BBFILES} ${LAYERDIR}/recipes-*/*/*.bb \
+BBFILES += "${LAYERDIR}/recipes-*/*/*.bb \
${LAYERDIR}/recipes-*/*/*.bbappend"
 
 BBFILE_COLLECTIONS += "xilinx"
-BBFILE_PATTERN_xilinx := "^${LAYERDIR}/"
+BBFILE_PATTERN_xilinx = "^${LAYERDIR}/"
 BBFILE_PRIORITY_xilinx = "6"
-- 
1.8.2

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] bitbaking error with hello world recipe

[Sudhangathan B S]

Hello, I'm new to oe and yocto project..

I simply created my own meta-dese layer, added it in layers.conf

*This is the structure of meta-dese folder:*
*
*
suan@edcn400:~/pokybuilds$ ls -R /home/suan/poky/meta-dese/
/home/suan/poky/meta-dese/:
conf  recipes-dese

/home/suan/poky/meta-dese/conf:
layer.conf

/home/suan/poky/meta-dese/recipes-dese:
files  hello-1.0.bb

/home/suan/poky/meta-dese/recipes-dese/files:
hello.c
suan@edcn400:~/pokybuilds$


*I have quoted the output here:*
*
*
suan@edcn400:~/pokybuilds$ bitbake core-image-minimal
Loading cache: 100%
|###|
ETA:  00:00:00
Loaded 1118 entries from dependency cache.
WARNING: No bb files matched BBFILE_PATTERN_dese
'^/home/suan/poky/meta-dese/'

Build Configuration:
BB_VERSION= "1.17.1"
BUILD_SYS = "i686-linux"
NATIVELSBSTRING   = "Ubuntu-12.04"
TARGET_SYS= "arm-poky-linux-gnueabi"
MACHINE   = "qemuarm"
DISTRO= "poky"
DISTRO_VERSION= "1.3+snapshot-20130319"
TUNE_FEATURES = "armv5 thumb dsp"
TARGET_FPU= "soft"
meta
meta-yocto
meta-yocto-bsp
meta-dese = "master:164a4cb2fc64e76836182ad2d412343a7b26b964"

NOTE: Resolving any missing task queue dependencies
ERROR: Nothing RPROVIDES 'hello' (but
/home/suan/poky/meta/recipes-core/images/core-image-minimal.bb RDEPENDS on
or otherwise requires it)
NOTE: Runtime target 'hello' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['hello']
ERROR: Required build target 'core-image-minimal' has no buildable
providers.
Missing or unbuildable dependency chain was: ['core-image-minimal', 'hello']

Summary: There was 1 WARNING message shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
suan@edcn400:~/pokybuilds$

How can I proceed from here..??
-
Sudhangathan BS
Ph:(+91) 9731-905-205
-
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-selinux][for-denzil][PATCH] layer.conf: avoid unnecessary early expansion with :=

[Christopher Larson]

From: Christopher Larson 

bitbake handles immediate expansions of LAYERDIR for us automatically.

Signed-off-by: Christopher Larson 
---
 conf/layer.conf | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/conf/layer.conf b/conf/layer.conf
index ca0aefa..eb86560 100644
--- a/conf/layer.conf
+++ b/conf/layer.conf
@@ -1,11 +1,11 @@
 # We have a conf and classes directory, add to BBPATH
-BBPATH := "${BBPATH}:${LAYERDIR}"
+BBPATH .= ":${LAYERDIR}"
 
 # We have a packages directory, add to BBFILES
-BBFILES := "${BBFILES} ${LAYERDIR}/recipes-*/*/*.bb \
+BBFILES += "${LAYERDIR}/recipes-*/*/*.bb \
 ${LAYERDIR}/recipes-*/*/*.bbappend"
 
 BBFILE_COLLECTIONS += "selinux"
-BBFILE_PATTERN_selinux := "^${LAYERDIR}/"
+BBFILE_PATTERN_selinux = "^${LAYERDIR}/"
 BBFILE_PRIORITY_selinux = "5"
 
-- 
1.8.2

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-selinux][for-danny][PATCH] layer.conf: avoid unnecessary early expansion with :=

[Christopher Larson]

From: Christopher Larson 

bitbake handles immediate expansions of LAYERDIR for us automatically.

Signed-off-by: Christopher Larson 
---
 conf/layer.conf | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/conf/layer.conf b/conf/layer.conf
index ca1bb46..7af76a1 100644
--- a/conf/layer.conf
+++ b/conf/layer.conf
@@ -1,12 +1,12 @@
 # We have a conf and classes directory, add to BBPATH
-BBPATH := "${BBPATH}:${LAYERDIR}"
+BBPATH .= ":${LAYERDIR}"
 
 # We have a packages directory, add to BBFILES
-BBFILES := "${BBFILES} ${LAYERDIR}/recipes-*/*/*.bb \
+BBFILES += "${LAYERDIR}/recipes-*/*/*.bb \
 ${LAYERDIR}/recipes-*/*/*.bbappend"
 
 BBFILE_COLLECTIONS += "selinux"
-BBFILE_PATTERN_selinux := "^${LAYERDIR}/"
+BBFILE_PATTERN_selinux = "^${LAYERDIR}/"
 BBFILE_PRIORITY_selinux = "5"
 
 # This should only be incremented on significant changes that will
-- 
1.8.2

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-selinux][PATCH] layer.conf: avoid unnecessary early expansion with :=

[Christopher Larson]

From: Christopher Larson 

bitbake handles immediate expansions of LAYERDIR for us automatically.

Signed-off-by: Christopher Larson 
---
 conf/layer.conf | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/conf/layer.conf b/conf/layer.conf
index ca1bb46..7af76a1 100644
--- a/conf/layer.conf
+++ b/conf/layer.conf
@@ -1,12 +1,12 @@
 # We have a conf and classes directory, add to BBPATH
-BBPATH := "${BBPATH}:${LAYERDIR}"
+BBPATH .= ":${LAYERDIR}"
 
 # We have a packages directory, add to BBFILES
-BBFILES := "${BBFILES} ${LAYERDIR}/recipes-*/*/*.bb \
+BBFILES += "${LAYERDIR}/recipes-*/*/*.bb \
 ${LAYERDIR}/recipes-*/*/*.bbappend"
 
 BBFILE_COLLECTIONS += "selinux"
-BBFILE_PATTERN_selinux := "^${LAYERDIR}/"
+BBFILE_PATTERN_selinux = "^${LAYERDIR}/"
 BBFILE_PRIORITY_selinux = "5"
 
 # This should only be incremented on significant changes that will
-- 
1.8.2

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-meson-bsp][PATCH] layer.conf: avoid unnecessary early expansion with :=

[Christopher Larson]

From: Christopher Larson 

bitbake handles immediate expansions of LAYERDIR for us automatically.

Signed-off-by: Christopher Larson 
---
 conf/layer.conf | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/conf/layer.conf b/conf/layer.conf
index ae3af08..8bff37a 100644
--- a/conf/layer.conf
+++ b/conf/layer.conf
@@ -1,11 +1,11 @@
 # We have a conf and classes directory, add to BBPATH
-BBPATH := "${BBPATH}:${LAYERDIR}"
+BBPATH .= ":${LAYERDIR}"
 
 # We have a recipes directory, add to BBFILES
-BBFILES := "${BBFILES} ${LAYERDIR}/recipes-*/*/*.bb \
+BBFILES += "${LAYERDIR}/recipes-*/*/*.bb \
 ${LAYERDIR}/recipes-*/*/*.bbappend"
 
 BBFILE_COLLECTIONS += "mesonbsp"
-BBFILE_PATTERN_mesonbsp := "^${LAYERDIR}/"
+BBFILE_PATTERN_mesonbsp = "^${LAYERDIR}/"
 BBFILE_PRIORITY_mesonbsp = "5"
 
-- 
1.8.2

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-meson][PATCH] layer.conf: avoid unnecessary early expansion with :=

[Christopher Larson]

From: Christopher Larson 

bitbake handles immediate expansions of LAYERDIR for us automatically.

Signed-off-by: Christopher Larson 
---
 conf/layer.conf | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/conf/layer.conf b/conf/layer.conf
index 8bd75d8..f463203 100644
--- a/conf/layer.conf
+++ b/conf/layer.conf
@@ -1,10 +1,10 @@
 # We have a conf and classes directory, add to BBPATH
-BBPATH := "${LAYERDIR}:${BBPATH}"
+BBPATH =. "${LAYERDIR}:"
 
 # We have a packages directory, add to BBFILES
-BBFILES := "${BBFILES} ${LAYERDIR}/recipes-*/*/*.bb 
${LAYERDIR}/recipes-*/*/*.bbappend" 
+BBFILES += "${LAYERDIR}/recipes-*/*/*.bb ${LAYERDIR}/recipes-*/*/*.bbappend" 
 
 BBFILE_COLLECTIONS += "meta-meson"
-BBFILE_PATTERN_meta-meson := "^${LAYERDIR}/"
+BBFILE_PATTERN_meta-meson = "^${LAYERDIR}/"
 BBFILE_PRIORITY_meta-meson = "8"
 
-- 
1.8.2

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-baryon][for-denzil][PATCH] layer.conf: avoid unnecessary early expansion with :=

[Christopher Larson]

From: Christopher Larson 

bitbake handles immediate expansions of LAYERDIR for us automatically.

Signed-off-by: Christopher Larson 
---
 conf/layer.conf | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/conf/layer.conf b/conf/layer.conf
index 0d33e3b..5515047 100644
--- a/conf/layer.conf
+++ b/conf/layer.conf
@@ -2,12 +2,12 @@
 # Copyright 2011 Intel Corporation
 
 # We have a conf directory, prepend to BBPATH to prefer our versions
-BBPATH := "${LAYERDIR}:${BBPATH}"
+BBPATH =. "${LAYERDIR}:"
 
 # We have recipes-* directories, add to BBFILES
-BBFILES := "${BBFILES} ${LAYERDIR}/recipes-*/*/*.bb 
${LAYERDIR}/recipes-*/*/*.bbappend"
+BBFILES += "${LAYERDIR}/recipes-*/*/*.bb ${LAYERDIR}/recipes-*/*/*.bbappend"
 
 BBFILE_COLLECTIONS += "meta-baryon"
-BBFILE_PATTERN_meta-baryon := "^${LAYERDIR}/"
+BBFILE_PATTERN_meta-baryon = "^${LAYERDIR}/"
 BBFILE_PRIORITY_meta-baryon = "7"
 
-- 
1.8.2

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-baryon][for-danny][PATCH] layer.conf: avoid unnecessary early expansion with :=

[Christopher Larson]

From: Christopher Larson 

bitbake handles immediate expansions of LAYERDIR for us automatically.

Signed-off-by: Christopher Larson 
---
 conf/layer.conf | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/conf/layer.conf b/conf/layer.conf
index 0d33e3b..5515047 100644
--- a/conf/layer.conf
+++ b/conf/layer.conf
@@ -2,12 +2,12 @@
 # Copyright 2011 Intel Corporation
 
 # We have a conf directory, prepend to BBPATH to prefer our versions
-BBPATH := "${LAYERDIR}:${BBPATH}"
+BBPATH =. "${LAYERDIR}:"
 
 # We have recipes-* directories, add to BBFILES
-BBFILES := "${BBFILES} ${LAYERDIR}/recipes-*/*/*.bb 
${LAYERDIR}/recipes-*/*/*.bbappend"
+BBFILES += "${LAYERDIR}/recipes-*/*/*.bb ${LAYERDIR}/recipes-*/*/*.bbappend"
 
 BBFILE_COLLECTIONS += "meta-baryon"
-BBFILE_PATTERN_meta-baryon := "^${LAYERDIR}/"
+BBFILE_PATTERN_meta-baryon = "^${LAYERDIR}/"
 BBFILE_PRIORITY_meta-baryon = "7"
 
-- 
1.8.2

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-baryon][PATCH] layer.conf: avoid unnecessary early expansion with :=

[Christopher Larson]

From: Christopher Larson 

bitbake handles immediate expansions of LAYERDIR for us automatically.

Signed-off-by: Christopher Larson 
---
 conf/layer.conf | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/conf/layer.conf b/conf/layer.conf
index 0d33e3b..5515047 100644
--- a/conf/layer.conf
+++ b/conf/layer.conf
@@ -2,12 +2,12 @@
 # Copyright 2011 Intel Corporation
 
 # We have a conf directory, prepend to BBPATH to prefer our versions
-BBPATH := "${LAYERDIR}:${BBPATH}"
+BBPATH =. "${LAYERDIR}:"
 
 # We have recipes-* directories, add to BBFILES
-BBFILES := "${BBFILES} ${LAYERDIR}/recipes-*/*/*.bb 
${LAYERDIR}/recipes-*/*/*.bbappend"
+BBFILES += "${LAYERDIR}/recipes-*/*/*.bb ${LAYERDIR}/recipes-*/*/*.bbappend"
 
 BBFILE_COLLECTIONS += "meta-baryon"
-BBFILE_PATTERN_meta-baryon := "^${LAYERDIR}/"
+BBFILE_PATTERN_meta-baryon = "^${LAYERDIR}/"
 BBFILE_PRIORITY_meta-baryon = "7"
 
-- 
1.8.2

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-baryon] [PATCH 0/5] Updates and fixes

[Kevin Strasser]

Cc: Paul Eggleton 

The following changes since commit 566cb211cee8a9870257a4ac2fc706990a70b9d2:

  nfs-utils: update bbappend version to 1.2.7 (2013-02-27 15:24:30 +)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib strassek/baryon
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=strassek/baryon

Kevin Strasser (5):
  kernel: enable nfsd in linux-yocto 3.8
  ffmpegthumbnailer: update to 2.0.8
  ffmpegthumbnailer: include cstring
  samba: sync with meta-oe
  lvm2: sync with meta-oe

 recipes-connectivity/samba/files/smb.conf  |   10 -
 .../bug_221618_precise-64bit-prototype.patch   |   20 +
 ...4104_mention-kerberos-in-smbspool-manpage.patch |   34 +
 ...m_7499-nss_wins-dont-clobber-daemons-logs.patch |   47 +
 .../bug_601406_fix-perl-path-in-example.patch  |   15 +
 ...04768_upstream_7826_drop-using-samba-link.patch |   21 +
 ...ug_604768_upstream_7826_fix-WHATSNEW-link.patch |   18 +
 ...onfigure-disable-core_pattern-cross-check.patch |   20 +
 .../configure-disable-getaddrinfo-cross.patch  |   11 +
 .../samba/samba-3.6.8/documentation.patch  |  302 +
 .../samba/samba-3.6.8/documentation2.patch |  314 +
 .../samba-3.6.8/dont-build-VFS-examples.patch  |   31 +
 .../samba/samba-3.6.8/fhs-filespaths.patch |   65 +
 .../samba/samba-3.6.8/installswat.sh.patch |   23 +
 .../samba-3.6.8/libutil_drop_AI_ADDRCONFIG.patch   |   54 +
 .../samba-3.6.8/only_export_public_symbols.patch   |   21 +
 .../samba/samba-3.6.8/pam-examples.patch   |   17 +
 .../samba/samba-3.6.8/shadow_copy2_backport.patch  | 2101 +++
 .../samba/samba-3.6.8/smbclient-pager.patch|   18 +
 .../samba/samba-3.6.8/smbtar-bashism.patch |   19 +
 .../samba/samba-3.6.8/smbtorture-manpage.patch |   94 +
 .../samba/samba-3.6.8/undefined-symbols.patch  |   24 +
 .../samba/samba-3.6.8/usershare.patch  |   38 +
 .../samba/samba-3.6.8/waf-as-source.patch  |18534 
 recipes-connectivity/samba/samba-basic.inc |   38 +-
 recipes-connectivity/samba/samba.inc   |   43 +-
 .../samba/samba/Managing-Samba.txt |   40 +
 recipes-connectivity/samba/samba/cifs.patch|   10 +
 .../samba/{files => samba}/config-h.patch  |0
 .../samba/{files => samba}/config-lfs.patch|0
 .../samba/samba/configure-3.3.0.patch  |   85 +
 .../samba/{files/init => samba/init.samba} |4 +-
 recipes-connectivity/samba/samba/init.winbind  |   38 +
 recipes-connectivity/samba/samba/mtab.patch|   11 +
 .../samba/{files => samba}/quota.patch |0
 .../{files/smb.conf.example => samba/smb.conf} |   34 +-
 recipes-connectivity/samba/{files => samba}/tdb.pc |2 +-
 .../samba/{files => samba}/tdbheaderfix.patch  |0
 .../samba/{files => samba}/volatiles.03_samba  |0
 recipes-connectivity/samba/samba_3.5.6.bb  |   50 -
 recipes-connectivity/samba/samba_3.6.8.bb  |   59 +
 ...yocto_3.0.bbappend => linux-yocto_3.8.bbappend} |0
 .../ffmpeg/ffmpegthumbnailer/include-cstring.patch |   25 +
 ...bnailer_2.0.7.bb => ffmpegthumbnailer_2.0.8.bb} |9 +-
 recipes-support/lvm2/lvm2.inc  |6 +-
 recipes-support/lvm2/lvm2_2.02.85.bb   |7 -
 recipes-support/lvm2/lvm2_2.02.97.bb   |6 +
 47 files changed, 22209 insertions(+), 109 deletions(-)
 delete mode 100644 recipes-connectivity/samba/files/smb.conf
 create mode 100644 
recipes-connectivity/samba/samba-3.6.8/bug_221618_precise-64bit-prototype.patch
 create mode 100644 
recipes-connectivity/samba/samba-3.6.8/bug_387266_upstream_4104_mention-kerberos-in-smbspool-manpage.patch
 create mode 100644 
recipes-connectivity/samba/samba-3.6.8/bug_598313_upstream_7499-nss_wins-dont-clobber-daemons-logs.patch
 create mode 100644 
recipes-connectivity/samba/samba-3.6.8/bug_601406_fix-perl-path-in-example.patch
 create mode 100644 
recipes-connectivity/samba/samba-3.6.8/bug_604768_upstream_7826_drop-using-samba-link.patch
 create mode 100644 
recipes-connectivity/samba/samba-3.6.8/bug_604768_upstream_7826_fix-WHATSNEW-link.patch
 create mode 100644 
recipes-connectivity/samba/samba-3.6.8/configure-disable-core_pattern-cross-check.patch
 create mode 100644 
recipes-connectivity/samba/samba-3.6.8/configure-disable-getaddrinfo-cross.patch
 create mode 100644 recipes-connectivity/samba/samba-3.6.8/documentation.patch
 create mode 100644 recipes-connectivity/samba/samba-3.6.8/documentation2.patch
 create mode 100644 
recipes-connectivity/samba/samba-3.6.8/dont-build-VFS-examples.patch
 create mode 100644 recipes-connectivity/samba/samba-3.6.8/fhs-filespaths.patch
 create mode 100644 recipes-connectivity/samba/samba-3.6.8/installswat.sh.patch
 create mode 100644 
recipes-connectivity/samba/samba-3.6.8/libutil_drop_AI_ADDRCONFIG.patch
 create mode 100644 
recipes-connectivity/samba/samba-3.6.8/only_exp

[yocto] TMPDIR collision

[Trevor Woerner]

I have been going through the archives from this list looking for
information to not only improve my build times but to make these
builds safer (there are hints dropped here and there that these large
builds are bad on disks which has me worried seeing that I use the
same disk+partition for both my builds and my personal data).

One of the suggestions I'm anxious to try is to use tmpfs for my /tmp.
I assume this is because gcc uses the environment's TMPDIR variable to
define the location to place its temporary artifacts (which on most
systems turns out to be /tmp)? I can certainly see how this would be a
good improvement, but sometimes my /tmp ends up with lots of
non-build-related cruft which can become quite large. While I would
like to get gcc to use a tmpfs for its temporary files, I don't
necessarily want a whole bunch of PDFs I'm reading to be taking up
valuable tmpfs space unnecessarily. Therefore I'd like to keep /tmp
where it is, but somehow get gcc to use a different TMPDIR when
performing a build.

I can't just modify my .bashrc to define the new TMPDIR since anything
that uses the TMPDIR that is run after such a change (i.e. the
non-build-related cruft) will just end up in TMPDIR anyway.

But in bitbake's configuration there is also a variable named TMPDIR
which specifies where bitbake does all of its work (e.g.
${TOPDIR}/tmp). These two TMPDIRs could possibly collide, couldn't
they?

Let's say I wanted to leave /tmp where it is, but modify my
environment, when building, such that gcc will use /some/other/tmp
(i.e. a tmpfs) for its artifacts. It is normal to modify one's
environment when invoking a command, but if I wanted to modify my
environment when invoking bitbake, it'll confuse the two TMPDIRs,
won't it?

$ TMPDIR=/some/other/tmp bitbake world

This would cause both gcc and bitbake to use /some/other/tmp, no?
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Timeout elimination

[Kurt Stevens]

As for putting the image on a cf card, it may depend on which file system 
you would use.

I am using ext3 on a cf card, following the instructions for installing to a 
hard drive on this page:

 https://wiki.yoctoproject.org/wiki/How_do_I

Luck to you.

"Florin Cristian Dan" 
 wrote in 
message 
news:cabzodptr4xswpztyxwnxoq3xpezvmhulu5vx9qgxotkbht-...@mail.gmail.com...
> Hello, i've managed to burn the BSP image (emenlow) on a usb stick, on
> booted on my target machin, apparently it works fine, but i would like to
> know how can i eliminate that 10 day timeout, i've tried to enter the
> address that is given in the splash http://yoctoproject.org/tlk but is not
> working ("page not found"), this is one question, and another question is:
> currently i'm booting the image from a USB stick, but i want to make it
> defintive and run it from the targets CF memory, the principple of writing
> the image to the CF memory is the same as writing the image for the USB
> stick?
> Thank you very much
> Best regards
>





> 



___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] How to script HOB settings

[Kurt Stevens]

Hello,

I have been building images using HOB, and that works very well.

I had read in the docs about creating a custom package group, and I did 
this, and it worked well until I needed to incorporate some openembedded 
layers.

After that my custom package group is either being ignored or 
overridden.

I am having to select multiple perl libraries and system utilities for 
my package, and this is not only error prone and tedious, but I really want 
to keep these settings in a way that I can reapply them easily.

I expect to use the same setup in the future on a different 
architecture, and having a layer or script that I can apply which works like 
the custom package group originally did would be great.

I would appreciate any ideas,

Thanks,

Kurt Stevens




___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Error when building image in Hob

[Andreas Enbacka]

Hello,

 

I would like to ask about an image building problem I have when using Hob
within the yocto project. I am trying to build images for the Intel emenlow
taget (e.g., core-image-sato, core-image-x11).  I am able to build the
images ok in case I do not edit them; however when trying to edit an image
(adding some package(s)), the image build always fail with an error message
as follows:

 

Hob found an error:

Required build target 'hob-image-20130318-131837' has no buildable
providers. Missing or unbuildable dependency chain was

['hob-image-20130318-131837','libgstinterfaces-0.10'] (the error always
refers to 'Nothing RPROVIDES libgstinterfaces-0.10' before the mentioned
error).'

 

Any clues what could cause the problem would be greatly appreciated. 

 

Also, why do the packages always need to be re-selected on step 2/2: Edit
packages, once they have been selected on step 1 in Hob?

 

Best regards,

Andreas Enbacka

 

 

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [linux-yocto] [PATCH 0/1] [meta-realtime] Add rt-app, schedtool, define core-image-realtime, and append recipies-kernel

[Insop Song]

On Mon, Mar 18, 2013 at 7:21 AM, Bruce Ashfield
 wrote:
>
>
> I went with core-image-rt-extended this morning.
>
> The changes have been merged, briefly tested and pushed to the
> yocto layer.
>
> I've also created a docs/ subirectory in the layer, if you have
> test steps, READMEs or other information to contribute, that's the
> place we should put it.
>
> We can tweak this as required from here.
>

Thank you and will update the docs dir soon.

Regards,

Insop
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Help configuring pulseaudio

[Gary Thomas]

I know this is a little off-topic.  I have a Poky/Yocto
based system running pulseaudio out of the box.  Output
(playback) works great,  but it is choosing the wrong
device for input.  I'm hoping someone can give me a pointer
on how to configure things to get the input correct.

Here are my devices (raw ALSA version):
  # aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: Cobra4430p82 [Cobra4430p82], device 0: Multimedia (*) []
Subdevices: 1/1
Subdevice #0:   Subdevice #0
  card 0: Cobra4430p82 [Cobra4430p82], device 2: Voice (*) []
Subdevices: 1/1
Subdevice #0:   Subdevice #0
  card 0: Cobra4430p82 [Cobra4430p82], device 3: Tone Playback (*) []
Subdevices: 1/1
Subdevice #0:   Subdevice #0
  card 0: Cobra4430p82 [Cobra4430p82], device 4: VIB-DL (*) []
Subdevices: 1/1
Subdevice #0:   Subdevice #0
  card 0: Cobra4430p82 [Cobra4430p82], device 5: MODEM (*) []
Subdevices: 1/1
Subdevice #0:   Subdevice #0
  card 0: Cobra4430p82 [Cobra4430p82], device 6: Multimedia (*) []
Subdevices: 1/1
Subdevice #0:   Subdevice #0
  card 0: Cobra4430p82 [Cobra4430p82], device 8: Headset Playback 
twl6040-legacy-8 []
Subdevices: 1/1
Subdevice #0:   Subdevice #0
  card 0: Cobra4430p82 [Cobra4430p82], device 9: (HS Playback) []
Subdevices: 1/1
Subdevice #0:   Subdevice #0
  card 0: Cobra4430p82 [Cobra4430p82], device 11: (HF Playback) []
Subdevices: 1/1
Subdevice #0:   Subdevice #0
  card 0: Cobra4430p82 [Cobra4430p82], device 12: (Vibra) []
Subdevices: 1/1
Subdevice #0:   Subdevice #0
  card 0: Cobra4430p82 [Cobra4430p82], device 13: (BT Capture) []
Subdevices: 1/1
Subdevice #0:   Subdevice #0
  card 0: Cobra4430p82 [Cobra4430p82], device 14: (BT Playback) []
Subdevices: 1/1
Subdevice #0:   Subdevice #0
  card 0: Cobra4430p82 [Cobra4430p82], device 15: (FM Playback) []
Subdevices: 1/1
Subdevice #0:   Subdevice #0
  card 0: Cobra4430p82 [Cobra4430p82], device 16: (FM Capture) []
Subdevices: 1/1
Subdevice #0:   Subdevice #0
  # arecord -l
   List of CAPTURE Hardware Devices 
  card 0: Cobra4430p82 [Cobra4430p82], device 0: Multimedia (*) []
Subdevices: 1/1
Subdevice #0:   Subdevice #0
  card 0: Cobra4430p82 [Cobra4430p82], device 1: Multimedia Capture (*) []
Subdevices: 1/1
Subdevice #0:   Subdevice #0
  card 0: Cobra4430p82 [Cobra4430p82], device 2: Voice (*) []
Subdevices: 1/1
Subdevice #0:   Subdevice #0
  card 0: Cobra4430p82 [Cobra4430p82], device 5: MODEM (*) []
Subdevices: 1/1
Subdevice #0:   Subdevice #0
  card 0: Cobra4430p82 [Cobra4430p82], device 8: Headset Playback 
twl6040-legacy-8 []
Subdevices: 1/1
Subdevice #0:   Subdevice #0
  card 0: Cobra4430p82 [Cobra4430p82], device 10: (Analog Capture) []
Subdevices: 1/1
Subdevice #0:   Subdevice #0
  card 0: Cobra4430p82 [Cobra4430p82], device 13: (BT Capture) []
Subdevices: 1/1
Subdevice #0:   Subdevice #0
  card 0: Cobra4430p82 [Cobra4430p82], device 14: (BT Playback) []
Subdevices: 1/1
Subdevice #0:   Subdevice #0
  card 0: Cobra4430p82 [Cobra4430p82], device 15: (FM Playback) []
Subdevices: 1/1
Subdevice #0:   Subdevice #0
  card 0: Cobra4430p82 [Cobra4430p82], device 16: (FM Capture) []
Subdevices: 1/1
Subdevice #0:   Subdevice #0

Here's what pulse is choosing:
  # pactl stat
  Currently in use: 1 blocks containing 64.0 KiB bytes total.
  Allocated during whole lifetime: 59019 blocks containing 41.4 MiB bytes total.
  Sample cache size: 0 B
  Server String: /var/volatile/tmp/pulse-FUK8lo8eJhXc/native
  Library Protocol Version: 26
  Server Protocol Version: 26
  Is Local: yes
  Client Index: 53
  Tile Size: 65496
  User Name: root
  Host Name: cobra4430p82
  Server Name: pulseaudio
  Server Version: 2.1
  Default Sample Specification: s16le 2ch 44100Hz
  Default Channel Map: front-left,front-right
  Default Sink: alsa_output.platform-omap-abe-twl6040.analog-stereo
  Default Source: alsa_output.platform-omap-abe-twl6040.analog-stereo.monitor
  Cookie: 93f5:b437

What I want is for it to choose the ALSA device hw:0,1 for input (source).

Can someone help out?

Thanks

--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [question] "icecc: improve interaction with sstate"

[Trevor Woerner]

On Sun, Mar 17, 2013 at 7:17 PM, Martin Jansa  wrote:
> Please use better Subject next time, I was wondering what could be
> broken by my patch to icecc and your question is quite unrelated to that
> commit.
>
> Something like "neard failing to build with latest poky" would be
> better.

...which is why I wasn't aware of this thread when I sent my problem
report about neard :-D

I guess *technically* I should have been reading all the correspondence...
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [linux-yocto] [PATCH 0/1] [meta-realtime] Add rt-app, schedtool, define core-image-realtime, and append recipies-kernel

[Bruce Ashfield]

On 13-03-17 03:36 AM, Insop Song wrote:

On Sat, Mar 16, 2013 at 9:04 PM, Bruce Ashfield
 wrote:



This looks good to me now, I still think we'll have some confusion
between the core "rt" images and core-image-realtime that we are
introducing here.

I may rename it core-image-realtime-extended as part of the merge,
if that's acceptable to you ? I think it will be something that
we'll need to revisit at some point, but that's not a good reason
to hold this back anymore.

I'll merge, do a quick test and push this out on Monday.


"core-image-realtime-extended" or "core-image-rt-extended (to be
aligned with existing core-image-rt)" or something along this line
sounds fine to me.


I went with core-image-rt-extended this morning.

The changes have been merged, briefly tested and pushed to the
yocto layer.

I've also created a docs/ subirectory in the layer, if you have
test steps, READMEs or other information to contribute, that's the
place we should put it.

We can tweak this as required from here.

Cheers,

Bruce



I was thinking of updating my patch, but it would be better if you
decide the final name, so I won't update the patch for now.
Or if you know which name is the best, then just let me know, I will
update the patch and send it to you.

Thank you,

Insop



___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Timeout elimination

[Bruce Ashfield]

On 13-03-18 04:34 AM, Florin Cristian Dan wrote:

Hello, i've managed to burn the BSP image (emenlow) on a usb stick, on
booted on my target machin, apparently it works fine, but i would like
to know how can i eliminate that 10 day timeout, i've tried to enter the


To answer this part of the question. Simply rebuild the kernel yourself
and the timeout will be removed. All of the configuration and layers
used to build the kernel you downloaded are available with the meta-intel
releases, minus the layer that adds the timeout configuration.

Cheers,

Bruce


address that is given in the splash http://yoctoproject.org/tlk but is
not working ("page not found"), this is one question, and another
question is: currently i'm booting the image from a USB stick, but i
want to make it defintive and run it from the targets CF memory, the
principple of writing the image to the CF memory is the same as writing
the image for the USB stick?
Thank you very much
Best regards


___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto



___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] remove /usr/share/terminfo

[Hans Beckérus]

This is a continuation of the thread handling removal of /boot/uImage and
terminfo database. The /boot/uImage is solved but I am still having issues
with trying to remove /usr/share/terminfo database. I thought it would be
as easy as just creating a ncurses .bbappend and configure the package with
OE_EXTRACONF = "--disable-database --enable-termcap". Not so. The problem
is that the ncurses.inc has some hardcode configuration options. One of
these is not compatible with "--disable-database". Specifically it is
"--with-ticlib". To me it seems like the ncurses package has not been
designed for providing the option to disable the terminfo database.

What I did as a temporary workaround was to override the entire
ncurses_config() option to overcome the conflict. But I am not very happy
with this solution, neither I am very happy with what happens to the
package when actually faulting out the terminfo support. The result of such
a configuration is that the entire ncurses library gets crippled and a lot
of packages can no longer be used, eg. htop. Also, the ncurses package
recipe does not seem to create the termcap database instead of terminfo if
such is removed. Which is completely natural since it does not support
disabling terminfo in the first place.
Maybe I could try the option to compile in the termcap database? But then I
do not know what the gain would be. What I am after is to get rid of the
database completely from the rootfs due to size constraints, but instead
link to some network mounted location. If the terminfo database is missing
ncurses will simply fallback to a dumb terminal setting which is fine on a
production board. In a test environment the network location will be
available and ncurses will be able to locate the database.

Any ideas what can be done here? If I would like to remove the physical
database from the rootfs and instead replace it by a soft link. Where would
be the best place to do this?

Hans
___
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

[Martin Jansa]

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

[Martin Jansa]

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

[yocto] [META-OE][PATCH] iperf 2.0.5 + fix for minor bug while cross-compiling

[Simon Egli]

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

>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

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Timeout elimination

[Florin Cristian Dan]

Hello, i've managed to burn the BSP image (emenlow) on a usb stick, on
booted on my target machin, apparently it works fine, but i would like to
know how can i eliminate that 10 day timeout, i've tried to enter the
address that is given in the splash http://yoctoproject.org/tlk but is not
working ("page not found"), this is one question, and another question is:
currently i'm booting the image from a USB stick, but i want to make it
defintive and run it from the targets CF memory, the principple of writing
the image to the CF memory is the same as writing the image for the USB
stick?
Thank you very much
Best regards
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto