Date   

Re: remove /usr/share/terminfo

Hans Beckérus <hans.beckerus@...>
 

On Mon, Mar 18, 2013 at 1:13 PM, Hans Beckérus <hans.beckerus@...> wrote:
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?


So, just posting back my progress so far. Since I did not receive any responses I simply had to try "something". Not very proud of it, but it works. What I did was to create a ncurses .bbappend file in my layer containing only this:

shell_do_install_append() {
       if [ "${CLASSOVERRIDE}" == "class-target" ]; then
               rm -rf "${D}${datadir}/terminfo"
               ln -sf /app/usr/share/terminfo "${D}${datadir}/terminfo"
       fi
}

So, what it does is by using brute force removing the terminfo database from /usr/share as installed by the recipe and replacing it with a soft link to a well known location, eg. an NFS mount point. The minimalistic database is still kept in /etc/terminfo. This database serves most purposes on a production board. If a full functional database is needed a user must provide it through the link. The result is still a fully functional ncurses implementation, but with heavily reduced footprint.

I do not know if my conditional to detect a target build is correct (I do not wish to have this done for eg. natrive builds). There is probably a much better way to have this code only being performed for certain classes.
Also I do not understand why using do_install_append() does not work, I had to use shell_do_install_append() as shell_do_install is defined in ncurses.inc otherwise I got recipe parse errors!?

Hans










Hob custom image build error

Andreas Enbacka <aenbacka@...>
 

Hello,

 

Whenever I build a custom image in Hob (using Create your own image), I get the following error output once the image build stage is completed:

 

Traceback (most recent call last):

  File "/home/user/poky/bitbake/lib/bb/ui/crumbs/builder.py", line 1096, in handler_build_succeeded_cb

    self.build_succeeded()

  File "/home/user/poky/bitbake/lib/bb/ui/crumbs/builder.py", line 1029, in build_succeeded

    version = self.recipe_model.get_custom_image_version()

  File "/home/user/poky/bitbake/lib/bb/ui/crumbs/hoblistmodel.py", line 696, in get_custom_image_version

    return self.custom_image_version

AttributeError: 'RecipeListModel' object has no attribute 'custom_image_version'

 

The UI is the stuck at 99% (do_build). However, the image build process has otherwise succeeded (the image files exist in the images folder). However, Hob needs to be force closed.

 

Best regards,

Andreas Enbacka


Yocto Java support.

Florin Cristian Dan <dan.florincristian@...>
 


Hello, 
Ok, so in the last days, i've managest to bake my own sato-emenlow image, and runed it on my machine wich is a PEB2739 (Intel Atom Z510 based).I'm intrested now in developing some industrial applications, like different types of masurement gauges.  Now i wonder if yocto project has suport for java and how its done, as far as i am, i'have read that there would some meta-java layer, but i'm not sure what to do further, where to get it, and how the development proces would go.
 Can someone please give me some advices.

Best regards


(No subject)

Florin Cristian Dan <dan.florincristian@...>
 

Hello, 
Ok, so in the last days, i've managest to bake my own sato-emenlow image, and runed it on my machine wich is a PEB2739 (Intel Atom Z510 based).I'm intrested now in developing some industrial applications, like different types of masurement gauges.  Now i wonder if yocto project has suport for java and how its done, as far as i am, i'have read that there would some meta-java layer, but i'm not sure what to do further, where to get it, and how the development proces would go.
 Can someone please give me some advices.

Best regards


Re: bitbaking error with hello world recipe

Chen Qi
 

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@...
https://lists.yoctoproject.org/listinfo/yocto


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

kergoth@...
 

From: Christopher Larson <chris_larson@...>

bitbake handles immediate expansions of LAYERDIR for us automatically.

Signed-off-by: Christopher Larson <chris_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


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

kergoth@...
 

From: Christopher Larson <chris_larson@...>

bitbake handles immediate expansions of LAYERDIR for us automatically.

Signed-off-by: Christopher Larson <chris_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


bitbaking error with hello world recipe

Sudhangathan B S <sudhangathan@...>
 

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


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

kergoth@...
 

From: Christopher Larson <chris_larson@...>

bitbake handles immediate expansions of LAYERDIR for us automatically.

Signed-off-by: Christopher Larson <chris_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


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

kergoth@...
 

From: Christopher Larson <chris_larson@...>

bitbake handles immediate expansions of LAYERDIR for us automatically.

Signed-off-by: Christopher Larson <chris_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


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

kergoth@...
 

From: Christopher Larson <chris_larson@...>

bitbake handles immediate expansions of LAYERDIR for us automatically.

Signed-off-by: Christopher Larson <chris_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


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

kergoth@...
 

From: Christopher Larson <chris_larson@...>

bitbake handles immediate expansions of LAYERDIR for us automatically.

Signed-off-by: Christopher Larson <chris_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


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

kergoth@...
 

From: Christopher Larson <chris_larson@...>

bitbake handles immediate expansions of LAYERDIR for us automatically.

Signed-off-by: Christopher Larson <chris_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


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

kergoth@...
 

From: Christopher Larson <chris_larson@...>

bitbake handles immediate expansions of LAYERDIR for us automatically.

Signed-off-by: Christopher Larson <chris_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


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

kergoth@...
 

From: Christopher Larson <chris_larson@...>

bitbake handles immediate expansions of LAYERDIR for us automatically.

Signed-off-by: Christopher Larson <chris_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


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

kergoth@...
 

From: Christopher Larson <chris_larson@...>

bitbake handles immediate expansions of LAYERDIR for us automatically.

Signed-off-by: Christopher Larson <chris_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


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

Kevin Strasser <kevin.strasser@...>
 

Cc: Paul Eggleton <paul.eggleton@...>

The following changes since commit 566cb211cee8a9870257a4ac2fc706990a70b9d2:

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

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_export_public_symbols.patch
create mode 100644 recipes-connectivity/samba/samba-3.6.8/pam-examples.patch
create mode 100644 recipes-connectivity/samba/samba-3.6.8/shadow_copy2_backport.patch
create mode 100644 recipes-connectivity/samba/samba-3.6.8/smbclient-pager.patch
create mode 100644 recipes-connectivity/samba/samba-3.6.8/smbtar-bashism.patch
create mode 100644 recipes-connectivity/samba/samba-3.6.8/smbtorture-manpage.patch
create mode 100644 recipes-connectivity/samba/samba-3.6.8/undefined-symbols.patch
create mode 100644 recipes-connectivity/samba/samba-3.6.8/usershare.patch
create mode 100644 recipes-connectivity/samba/samba-3.6.8/waf-as-source.patch
create mode 100644 recipes-connectivity/samba/samba/Managing-Samba.txt
create mode 100644 recipes-connectivity/samba/samba/cifs.patch
rename recipes-connectivity/samba/{files => samba}/config-h.patch (100%)
rename recipes-connectivity/samba/{files => samba}/config-lfs.patch (100%)
create mode 100644 recipes-connectivity/samba/samba/configure-3.3.0.patch
rename recipes-connectivity/samba/{files/init => samba/init.samba} (98%)
create mode 100644 recipes-connectivity/samba/samba/init.winbind
create mode 100644 recipes-connectivity/samba/samba/mtab.patch
rename recipes-connectivity/samba/{files => samba}/quota.patch (100%)
rename recipes-connectivity/samba/{files/smb.conf.example => samba/smb.conf} (94%)
rename recipes-connectivity/samba/{files => samba}/tdb.pc (87%)
rename recipes-connectivity/samba/{files => samba}/tdbheaderfix.patch (100%)
rename recipes-connectivity/samba/{files => samba}/volatiles.03_samba (100%)
delete mode 100644 recipes-connectivity/samba/samba_3.5.6.bb
create mode 100644 recipes-connectivity/samba/samba_3.6.8.bb
rename recipes-kernel/linux/{linux-yocto_3.0.bbappend => linux-yocto_3.8.bbappend} (100%)
create mode 100644 recipes-multimedia/ffmpeg/ffmpegthumbnailer/include-cstring.patch
rename recipes-multimedia/ffmpeg/{ffmpegthumbnailer_2.0.7.bb => ffmpegthumbnailer_2.0.8.bb} (71%)
delete mode 100644 recipes-support/lvm2/lvm2_2.02.85.bb
create mode 100644 recipes-support/lvm2/lvm2_2.02.97.bb

--
1.7.9.5


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?


Re: 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"
<dan.florincristian@...> wrote in
message
news:CABzOdpTr4xsWPZtYxwnXOq3XpezVMHULu5Vx9qgxOtKbHt-Gxg@......
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

--------------------------------------------------------------------------------



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