Re: [yocto] [yocto-docs][PATCH 2/2] dev-manual: Add section about /dev population
Hi Scott Thanks. I had a look at the commits and it looks like commit 7c6c7ac573f92bfc844977e0d7a97ca4aac9bc70 also introduced a strange change on line 946 of dev-manual-common-tasks.xml. See: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/commit/?id=7c6c7ac573f92bfc844977e0d7a97ca4aac9bc70 Pascal > -Original Message- > From: Rifenbark, Scott M [mailto:scott.m.rifenb...@intel.com] > Sent: Samstag, 17. Januar 2015 01:05 > To: Bach, Pascal; yocto@yoctoproject.org > Subject: RE: [yocto] [yocto-docs][PATCH 2/2] dev-manual: Add section > about /dev population > > Pascal, > > I have applied this patch with some editing. Also, applied the patch > that added the USE_DEVFS variable to the ref-manual. > > Thanks, > Scott > > >-Original Message- > >From: yocto-boun...@yoctoproject.org [mailto:yocto- > >boun...@yoctoproject.org] On Behalf Of Pascal Bach > >Sent: Wednesday, January 07, 2015 6:58 AM > >To: yocto@yoctoproject.org > >Subject: [yocto] [yocto-docs][PATCH 2/2] dev-manual: Add section about > >/dev population > > > >Signed-off-by: Pascal Bach > >--- > > .../dev-manual/dev-manual-common-tasks.xml | 104 > > > > 1 file changed, 104 insertions(+) > > > >diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml > >b/documentation/dev-manual/dev-manual-common-tasks.xml > >index 17d725b..9072586 100644 > >--- a/documentation/dev-manual/dev-manual-common-tasks.xml > >+++ b/documentation/dev-manual/dev-manual-common-tasks.xml > >@@ -7582,6 +7582,110 @@ Gateways via their Web > >Interfaces" > > > > > > > >+ > >+Selecting a Device Manager > >+ > >+ > >+Yocto provides multiple ways to manage > /dev > >+ > >+ > >+Persistent and pre populated > >/dev: > >+in this case the /dev directory > is persistent > >+and the required device nodes are created at build > time. > >+ > >+ > >+ > >+Use devtmps with a > device > >manager: > >+in this case the /dev directory > is provided > >+by the kernel as an in memory file system and is > automatically > >+populated by the kernel at runtime. Additional > configuration of > >+device nodes is done in user space by a device manager > like > >+udev or busybox- > >mdev. > >+ > >+ > >+ > >+ > >+ > >+Use Persistent and pre-populated > >/dev > >+ > >+ > >+To use the static method for device population the > variable > >+USE_DEVFS > >+needs to be set to 0. > >+ > >+ > >+ USE_DEVFS = "0" > >+ > >+ > >+ > >+ > >+The content of the resulting /dev > directory > >+is defined in a Device Table file. The device table to > use is defined by > >the variable > >+IMAGE_DEVICE_TABLES >ink> and should be set > >+in the MACHINE, > >+DISTRO > >+or local.conf configuration file. > >+ > >+ > >+ > >+If nothing is defined the default > device_table- > >minimal.txt is used. > >+ > >+ > >+ > >+The population is handled by the > makedevs > >utility > >+during image creation. > >+ > >+ > >+ IMAGE_DEVICE_TABLES = "device_table-mymachine.txt" > >+ > >+ > >+ > >+ > >+ > >+ > >+Use devtmpfs and a device > >manager > >+ > >+ > >+To use the dynamic method for device population the > variable > >+USE_DEVFS > >+needs to be set to 1. This is the default. > >+ > >+ > >+ USE_DEVFS = "1" > >+ > >+ > >+This way the resulting /dev is > populated by > >the kernel > >+using devtmpfs. Make sure the > >corresponding > >+kernel configuration variable > >CONFIG_DEVTMPFS is set > >+when building a linux kernel. > >+ > >+ > >+ > >+All devices created by devtmpfs > will be > >+owned by root and have > permissions > >0600. > >+ > >+To have more control over the device nodes a device > manager like > >+udev or busybox- > >mdev > >+can be used. > >+ > >+The device manager to use is defined by the variable > >+VIRTUAL-RUNTIME_dev_manager and > >should be set > >+in the MACHINE, > >+DISTRO > >+or local.conf configuration file. > >+ > >+ > >+ > >+ VIRTUAL-RUNTIME_dev_manager = "udev" > >+ > >+ # Some alternative values > >+ # VIR
Re: [yocto] Benchmark layer available
On Sunday 18 January 2015 16:51:09 akuster808 wrote: > On 01/17/2015 05:02 PM, Andrei Gherzan wrote: > > Is there any benchmarking layer available? I was interested in LINPACK > > and I think it would make sense to have a benchmarking layer which will > > include stuff like: LINPACK, ioquake3, Whetstone etc. > > there are bench mark recipes in meta-openembedded > > meta-oe/recipes-benchmark > > http://cgit.openembedded.org/meta-openembedded/tree/meta-oe/recipes-benchmar > k > > I don't know what the threshold is for making a layer from a set of recipes. I would say: 1) Most importantly, there is someone to step up and maintain the new layer who has the time and interest in doing so. 2) There is a logical grouping for the recipes and there are more than one or two of them 3) Dependencies between existing layers don't become too much of a problem with the creation of the layer Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-cgl][PATCH 0/2] cluster: Fix some error and format
Use KERNEL_SRC instead of hardcode path in configure. Also fix license format. *** BLURB HERE *** Qian Lei (2): cluster: Fix license format cluster: Add a patch to fix the path of kernel source .../cluster/0001-Fix-the-kernel-source-patch.patch | 38 ++ .../recipes-cgl/cluster/cluster_3.2.0.bb | 5 +-- 2 files changed, 41 insertions(+), 2 deletions(-) create mode 100644 meta-cgl-common/recipes-cgl/cluster/cluster/0001-Fix-the-kernel-source-patch.patch -- 1.8.3.1 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-cgl][PATCH 1/2] cluster: Fix license format
Signed-off-by: Qian Lei
---
meta-cgl-common/recipes-cgl/cluster/cluster_3.2.0.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta-cgl-common/recipes-cgl/cluster/cluster_3.2.0.bb
b/meta-cgl-common/recipes-cgl/cluster/cluster_3.2.0.bb
index 2d6b49c..3e7d42c 100644
--- a/meta-cgl-common/recipes-cgl/cluster/cluster_3.2.0.bb
+++ b/meta-cgl-common/recipes-cgl/cluster/cluster_3.2.0.bb
@@ -7,7 +7,7 @@ SRC_URI =
"https://fedorahosted.org/releases/c/l/cluster/${BP}.tar.xz";
SRC_URI[md5sum] = "3f496dbecaea367af5a5e81d2e8dcab8"
-LICENSE = "GPL-2.0 LGPL-2.0"
+LICENSE = "GPL-2.0 & LGPL-2.0"
LIC_FILES_CHKSUM =
"file://doc/README.licence;md5=ee8ae43af5ea09f12ca7f7a649764cb0"
PR = "r1"
--
1.8.3.1
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-cgl][PATCH 2/2] cluster: Fix the path
Use KERNEL_SRC instead of the hardcode path in configure.
Signed-off-by: Qian Lei
---
.../cluster/0001-Fix-the-kernel-source-patch.patch | 38 ++
.../recipes-cgl/cluster/cluster_3.2.0.bb | 3 +-
2 files changed, 40 insertions(+), 1 deletion(-)
create mode 100644
meta-cgl-common/recipes-cgl/cluster/cluster/0001-Fix-the-kernel-source-patch.patch
diff --git
a/meta-cgl-common/recipes-cgl/cluster/cluster/0001-Fix-the-kernel-source-patch.patch
b/meta-cgl-common/recipes-cgl/cluster/cluster/0001-Fix-the-kernel-source-patch.patch
new file mode 100644
index 000..05dab1b
--- /dev/null
+++
b/meta-cgl-common/recipes-cgl/cluster/cluster/0001-Fix-the-kernel-source-patch.patch
@@ -0,0 +1,38 @@
+From 7ddf265becd44e7f7270ff98d2dcc14361effe8c Mon Sep 17 00:00:00 2001
+From: Qian Lei
+Date: Sun, 18 Jan 2015 14:01:17 +0800
+Subject: [PATCH] Fix the kernel source patch
+
+Signed-off-by: Qian Lei
+---
+ configure | 12 ++--
+ 1 file changed, 2 insertions(+), 10 deletions(-)
+
+diff --git a/configure b/configure
+index 1e6356e..0c8038f 100755
+--- a/configure
b/configure
+@@ -362,18 +362,10 @@ if (! -d "$objdir/make") {
+
+ my @un = POSIX::uname();
+ if (!$kernel_build) {
+- if (-d "/lib/modules/$un[2]/build") {
+-$kernel_build="/lib/modules/$un[2]/build";
+- } else {
+-$kernel_build="/usr/src/linux";
+- }
++ $kernel_build="${KERNEL_SRC}";
+ }
+ if (!$kernel_src) {
+- if (-d "/lib/modules/$un[2]/source") {
+-$kernel_src="/lib/modules/$un[2]/source";
+- } else {
+-$kernel_src=$kernel_build;
+- }
++ $kernel_src=$kernel_build;
+ }
+ if (not $disable_kernel_check and
!kernel_version($kernel_src,$required_kernelversion)) {
+ exit 1;
+--
+1.8.3.1
+
diff --git a/meta-cgl-common/recipes-cgl/cluster/cluster_3.2.0.bb
b/meta-cgl-common/recipes-cgl/cluster/cluster_3.2.0.bb
index 3e7d42c..392af2c 100644
--- a/meta-cgl-common/recipes-cgl/cluster/cluster_3.2.0.bb
+++ b/meta-cgl-common/recipes-cgl/cluster/cluster_3.2.0.bb
@@ -3,7 +3,8 @@ DESCRIPTION = "Red Hat Cluster"
SECTION = "libs"
HOMEPAGE = "https://fedorahosted.org/cluster/wiki/HomePage";
-SRC_URI = "https://fedorahosted.org/releases/c/l/cluster/${BP}.tar.xz";
+SRC_URI = "https://fedorahosted.org/releases/c/l/cluster/${BP}.tar.xz \
+ file://0001-Fix-the-kernel-source-patch.patch"
SRC_URI[md5sum] = "3f496dbecaea367af5a5e81d2e8dcab8"
--
1.8.3.1
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-cgl][PATCH 0/2] cluster: Fix some error and format
On Mon, 19 Jan 2015 11:32:35 + Alexandru Vaduva wrote: > Does this fix the error I encounter when building the package. > The log is attached to this email and is also available in the bugzilla > issue: https://bugzilla.yoctoproject.org/show_bug.cgi?id=7176 Actually no. This patch use the kernel source in bitbake world instead of that on the host. This error only appeared on my build enviroment. But your error is to build openldap, not cluster. > -Original Message- > From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] > On Behalf Of Qian Lei Sent: Monday, January 19, 2015 12:08 PM > To: yocto@yoctoproject.org > Subject: [yocto] [meta-cgl][PATCH 0/2] cluster: Fix some error and format > > Use KERNEL_SRC instead of hardcode path in configure. Also fix license format. > > *** BLURB HERE *** > > Qian Lei (2): > cluster: Fix license format > cluster: Add a patch to fix the path of kernel source > > .../cluster/0001-Fix-the-kernel-source-patch.patch | 38 > ++ .../recipes-cgl/cluster/cluster_3.2.0.bb | > 5 +-- 2 files changed, 41 insertions(+), 2 deletions(-) create mode 100644 > meta-cgl-common/recipes-cgl/cluster/cluster/0001-Fix-the-kernel-source-patch.patch > > -- > 1.8.3.1 > > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto -- Qian Lei -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-cgl][PATCH] cluster: Modify the checksum
Signed-off-by: Qian Lei
---
meta-cgl-common/recipes-cgl/cluster/cluster_3.2.0.bb | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/meta-cgl-common/recipes-cgl/cluster/cluster_3.2.0.bb
b/meta-cgl-common/recipes-cgl/cluster/cluster_3.2.0.bb
index 392af2c..c1a7d1f 100644
--- a/meta-cgl-common/recipes-cgl/cluster/cluster_3.2.0.bb
+++ b/meta-cgl-common/recipes-cgl/cluster/cluster_3.2.0.bb
@@ -6,7 +6,8 @@ HOMEPAGE = "https://fedorahosted.org/cluster/wiki/HomePage";
SRC_URI = "https://fedorahosted.org/releases/c/l/cluster/${BP}.tar.xz \
file://0001-Fix-the-kernel-source-patch.patch"
-SRC_URI[md5sum] = "3f496dbecaea367af5a5e81d2e8dcab8"
+SRC_URI[md5sum] = "300d83dbbc525c3da21c2e961271c84b"
+SRC_URI[sha256sum] =
"4d340338c2376d369cb223469fa1a3356cce9ab5b2a0a0a33256ade2dbbe02d1"
LICENSE = "GPL-2.0 & LGPL-2.0"
LIC_FILES_CHKSUM =
"file://doc/README.licence;md5=ee8ae43af5ea09f12ca7f7a649764cb0"
--
1.8.3.1
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-mingw] No recipes available for: gdb-cross-canadian_7.8.1.bbappend
Hello all, I'm trying to get the toolchain for windows/mingw and im having the following message when "bitbake meta-toolchain" ERROR: No recipes available for: /home/jjgarcia/Development/yocto/es-devel/yocto/poky/meta-mingw/recipes-devtools/gdb/gdb-cross-canadian_7.8.1.bbappend I'm trying with: $ git clone -b dizzy git://git.yoctoproject.org/poky.git $ cd poky; git clone git://git.yoctoproject.org/meta-mingw Configuring as follow: - local.conf with MACHINE ??= "genericx86" SDKMACHINE ?= "i686-mingw32" PACKAGE_CLASSES ?= "package_deb" and - bblayers.conf BBLAYERS ?= " \ ... (adding) /home/jjgarcia/Development/yocto/es-devel/yocto/poky/meta-mingw \ Help appreciated, Thanks in advance, Regards JJ -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Qt4-embedded mkspecs question
Hi, You probably miss the toolchain_create_sdk_env_script_append() in meta/recipes-qt/meta/meta-toolchain-qt.inc. Do not forget QT_DIR_NAME too. Regards, -- Adrien RENAULT Ingénieur R&D Kaptalia Monitoring Le jeudi 4 décembre 2014 19:34:20 Vuille, Martin a écrit : We build Qt4-embedded and export the headers and libraries into the SDK for the application to build against. We also include nativesdk-qt4-tools in the SDK. The application team is saying that they also need the mkspecs, and those are not included in the SDK. Are the mkspecs supposed to be exported into the SDK? I don’t see a nativesdk package that contains them. We had to customize the Qt recipes somewhat, so it’s entirely possible that we broke something. Any help appreciated. MV -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Benchmark layer available
Hello, On Jan 19, 2015 11:47 AM, "Paul Eggleton" wrote: > > On Sunday 18 January 2015 16:51:09 akuster808 wrote: > > On 01/17/2015 05:02 PM, Andrei Gherzan wrote: > > > Is there any benchmarking layer available? I was interested in LINPACK > > > and I think it would make sense to have a benchmarking layer which will > > > include stuff like: LINPACK, ioquake3, Whetstone etc. > > > > there are bench mark recipes in meta-openembedded > > > > meta-oe/recipes-benchmark > > > > http://cgit.openembedded.org/meta-openembedded/tree/meta-oe/recipes-benchmar > > k > > > > I don't know what the threshold is for making a layer from a set of recipes. > > I would say: > > 1) Most importantly, there is someone to step up and maintain the new layer > who has the time and interest in doing so. Well. I asked because I have interest. :) And I can invest some time in doing the setup but definitely would need a helping hand in maintaining it. > > 2) There is a logical grouping for the recipes and there are more than one or > two of them Yup. We would need to discuss that and come to a conclusion. > > 3) Dependencies between existing layers don't become too much of a problem > with the creation of the layer Agreed. Andrei Gherzan -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Kernel configuration
Hi Chris, On Saturday 03 January 2015 00:57:50 Chris Tapp wrote: > If I change my bbappend to use lines of the form: > > SRC_URI_valleyisland-64 += " file://enable-R8169.cfg" Note that this probably doesn't do what you think it does - it'll be _setting_ the value to " file://enable-R8169.cfg" rather than appending to the existing value when MACHINE is "valleyisland-64". Overrides and += don't really work together because they operate at different times - the += happens immediately and then later the override is applied. The correct way to do a conditional append with an override is to use _append, e.g.: SRC_URI_append_valleyisland-64 = " file://enable-R8169.cfg" Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-mingw] No recipes available for: gdb-cross-canadian_7.8.1.bbappend
J.J. Garcia writes: > > Hello all, > I'm trying to get the toolchain for windows/mingw and im having the following message when "bitbake meta-toolchain" > > > ERROR: No recipes available for: > /home/jjgarcia/Development/yocto/es-devel/yocto/poky/meta-mingw/recipes- devtools/gdb/gdb-cross-canadian_7.8.1.bbappend > > > I'm trying with: > > $ git clone -b dizzy git://git.yoctoproject.org/poky.git > > $ cd poky; git clone git://git.yoctoproject.org/meta-mingw > > > Configuring as follow: > - local.conf with > > MACHINE ??= "genericx86" > SDKMACHINE ?= "i686-mingw32" > > > PACKAGE_CLASSES ?= "package_deb" > > and > - bblayers.conf > > BBLAYERS ?= " \ > ... (adding) > /home/jjgarcia/Development/yocto/es-devel/yocto/poky/meta-mingw \ > > > > Help appreciated, > > Thanks in advance, > > Regards > > JJ > > > [SOLVED] I was missing around the versions. I have noticed the recipe was not matching the gdb-cross-canadian_7.8.1.bbappend version number/string and im now using the master for both, poky and meta-mingw (before using dizzy from poky and master for meta-mingw) Sorry for the noise. Should check it before. Thanks all and all the best for the project!!! JJ -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [Recipe reporting system] Upgradable recipe name list
thon-async 0.6.1 0.6.2 No Maintainer python-smmap 0.8.2 0.9.0 No Maintainer python-git0.3.3 0.3.5 No Maintainer linux-yocto-dev 3.17++gitX 3.17.6++5ff54d8fb... No Maintainer ca-certificates 20140325 20141019 No Maintainer libpfm4 4.3.0 4.6.0 No Maintainer dbus-test 1.8.10 1.9.6 No Maintainer uclibc0.9.33+gitX0.9.33.2+gitAUTOI... No Maintainer libxshmfence 1.11.2 No Maintainer systemd 216+gitX 218+gitAUTOINC+a2... No Maintainer u-bootv2014.07+gitX v2015.01+gitAUTOI... No Maintainer waffle1.3.0 1.5.0 No Maintainer mesa-gl 10.3.4 10.4.2No Maintainer qt-mobility-x11 1.2.0 1.2.2-20120224Paul Eggleton qt-mobility-embedded 1.2.0 1.2.2-20120224Paul Eggleton ethtool 3.16 3.18 Paul Eggleton cmake 2.8.12.2 3.1.0 Paul Eggleton augeas1.2.0 1.3.0 Paul Eggleton yasm 1.2.0 1.3.0 Paul Eggleton dosfstools2.11 3.0.26Paul Eggleton unfs3 0.9.22.r4900.9.22.r494 Paul Eggleton gpgme 1.4.3 1.5.3 Paul Eggleton libevent 2.0.21 2.0.22Paul Eggleton libav 9.16 11.2 Paul Eggleton libevdev 1.31.3.2 Paul Eggleton x264 r2265+gitX r2491 Paul Eggleton gcc 4.9.1 4.9.2 Richard Purdie subversion1.8.10 1.8.11Richard Purdie python-distribute 0.6.32 0.7.3 Richard Purdie 0.7.3 only upgrades 0.6.32,... python-gst0.10.221.4.0 Richard Purdie python-scons 2.3.2 2.3.4 Richard Purdie python-pygobject 2.28.3 3.13.3Richard Purdie Newer versions of python-py... python2.7.3 3.4.2rc1 Richard Purdie python3 3.3.3 3.4.2rc1 Richard Purdie btrfs-tools 3.14.2+gitX3.18.1+gitAUTOINC... Richard Purdie tcf-agent 0.4.0+gitX 8.0+gitAUTOINC+3e... Richard Purdie gdb 7.8.1 7.8.2 Richard Purdie bdwgc 7.4.2 gc-7.2d Richard Purdie automake 1.14.1 1.15 Robert Yang binutils 2.24 2.25 Robert Yang ltp 20140828 20150119 Robert Yang git 2.2.1 2.2.2 Robert Yang e2fsprogs 1.42.9 1.42.12 Robert Yang libtool 2.4.2 2.4.4 Robert Yang glib-2.0 2.42.1 2.43.2Robert Yang gmp 6.0.0 6.0.0aRobert Yang wayland 1.6.0 1.6.91Ross Burton gdk-pixbuf2.30.8 2.31.2Ross Burton gtk+ 2.24.253.15.3Ross Burton Do not upgrade to version: ... gtk+3 3.12.2 3.15.3Ross Burton gtk-engines 2.20.2 2.91.1Ross Burton 2.91.1 is a 3.0 beta release libnotify 0.6.0 0.7.6 Ross Burton webkit-gtk1.8.3 1.10.2Ross Burton >= 1.10.2 needs ruby puzzles r10116 r10286Ross Burton libpam1.1.6 1.1.8 Ross Burton vala 0.26.1 0.27.1Ross Burton vte 0.28.2 0.39.1Ross Burton Pending Glib-2.0 Update libsoup-2.4 2.46.0 2.49.1Ross Burton icu 53.1 55Ross Burton libtasn1 4.04.2 Ross Burton gnutls3.3.11 3.3.12Ross Burton at-spi2-core 2.14.1 2.15.3Ross Burton atk 2.14.0 2.15.3Ross Burton at-spi2-atk 2.14.1 2.15.3Ross Burton libpng1.6.13 1.6.16Ross Burton x11-common0.11:7.6 Ross Burton
Re: [yocto] [yocto-docs][PATCH 2/2] dev-manual: Add section about /dev population
Pascal, Thanks for catching this. This was a result of cutting-and-pasting text in from the patch. I did not apply the patch in an automated fashion as there was some rewriting to do. So my hand-transposing missed those characters that were present in the email from which I was referencing. I removed them out and will republish the text later today. The commit to get them out is http://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/commit/?id=3ffbebd6c638e9f5b334dfef1d4e0bcc698ae810. Thanks, Scott >-Original Message- >From: Bach, Pascal [mailto:pascal.b...@siemens.com] >Sent: Monday, January 19, 2015 12:30 AM >To: Rifenbark, Scott M; yocto@yoctoproject.org >Subject: RE: [yocto] [yocto-docs][PATCH 2/2] dev-manual: Add section about >/dev population > >Hi Scott > >Thanks. I had a look at the commits and it looks like commit >7c6c7ac573f92bfc844977e0d7a97ca4aac9bc70 also introduced a strange change >on line 946 of dev-manual-common-tasks.xml. > >See: https://git.yoctoproject.org/cgit/cgit.cgi/yocto- >docs/commit/?id=7c6c7ac573f92bfc844977e0d7a97ca4aac9bc70 > >Pascal > >> -Original Message- >> From: Rifenbark, Scott M [mailto:scott.m.rifenb...@intel.com] >> Sent: Samstag, 17. Januar 2015 01:05 >> To: Bach, Pascal; yocto@yoctoproject.org >> Subject: RE: [yocto] [yocto-docs][PATCH 2/2] dev-manual: Add section >> about /dev population >> >> Pascal, >> >> I have applied this patch with some editing. Also, applied the patch >> that added the USE_DEVFS variable to the ref-manual. >> >> Thanks, >> Scott >> >> >-Original Message- >> >From: yocto-boun...@yoctoproject.org [mailto:yocto- >> >boun...@yoctoproject.org] On Behalf Of Pascal Bach >> >Sent: Wednesday, January 07, 2015 6:58 AM >> >To: yocto@yoctoproject.org >> >Subject: [yocto] [yocto-docs][PATCH 2/2] dev-manual: Add section >> >about /dev population >> > >> >Signed-off-by: Pascal Bach >> >--- >> > .../dev-manual/dev-manual-common-tasks.xml | 104 >> > >> > 1 file changed, 104 insertions(+) >> > >> >diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml >> >b/documentation/dev-manual/dev-manual-common-tasks.xml >> >index 17d725b..9072586 100644 >> >--- a/documentation/dev-manual/dev-manual-common-tasks.xml >> >+++ b/documentation/dev-manual/dev-manual-common-tasks.xml >> >@@ -7582,6 +7582,110 @@ Gateways via their Web >> >Interfaces" >> > >> > >> > >> >+ >> >+Selecting a Device Manager >> >+ >> >+ >> >+Yocto provides multiple ways to manage >> /dev >> >+ >> >+ >> >+Persistent and pre populated >> >/dev: >> >+in this case the /dev directory >> is persistent >> >+and the required device nodes are created at build >> time. >> >+ >> >+ >> >+ >> >+Use devtmps with a >> device >> >manager: >> >+in this case the /dev directory >> is provided >> >+by the kernel as an in memory file system and is >> automatically >> >+populated by the kernel at runtime. Additional >> configuration of >> >+device nodes is done in user space by a device >> >+ manager >> like >> >+udev or busybox- >> >mdev. >> >+ >> >+ >> >+ >> >+ >> >+ >> >+Use Persistent and pre-populated >> >/dev >> >+ >> >+ >> >+To use the static method for device population the >> variable >> >+USE_DEVFS >> >+needs to be set to 0. >> >+ >> >+ >> >+ USE_DEVFS = "0" >> >+ >> >+ >> >+ >> >+ >> >+The content of the resulting >> >+ /dev >> directory >> >+is defined in a Device Table file. The device table >> >+ to >> use is defined by >> >the variable >> >+IMAGE_DEVICE_TABLESul >> >ink> and should be set >> >+in the MACHINE, >> >+DISTRO >> >+or local.conf configuration file. >> >+ >> >+ >> >+ >> >+If nothing is defined the default >> device_table- >> >minimal.txt is used. >> >+ >> >+ >> >+ >> >+The population is handled by the >> makedevs >> >utility >> >+during image creation. >> >+ >> >+ >> >+ IMAGE_DEVICE_TABLES = "device_table-mymachine.txt" >> >+ >> >+ >> >+ >> >+ >> >+ >> >+ >> >+Use devtmpfs and a device >> >manager >> >+ >> >+ >> >+To use the dynamic method for device population the >> variable >> >+USE_DEVFS >> >+needs to be set to 1. This is the default. >> >+ >> >+ >> >+ USE_DEVFS = "1" >> >+ >> >+ >> >+This way the resulting /dev is >> populate
Re: [yocto] Kernel configuration
Hi Paul, On 19 Jan 2015, at 14:37, Paul Eggleton wrote: > On Saturday 03 January 2015 00:57:50 Chris Tapp wrote: >> If I change my bbappend to use lines of the form: >> >> SRC_URI_valleyisland-64 += " file://enable-R8169.cfg" > > Note that this probably doesn't do what you think it does - it'll be > _setting_ > the value to " file://enable-R8169.cfg" rather than appending to the > existing > value when MACHINE is "valleyisland-64". I thought I had this sorted as it was doing _what_ I wanted ;-) > Overrides and += don't really work > together because they operate at different times - the += happens immediately > and then later the override is applied. The correct way to do a conditional > append with an override is to use _append, e.g.: > > SRC_URI_append_valleyisland-64 = " file://enable-R8169.cfg" Thanks for the heads-up - I'll go and update my file and add a comment so I remember next time round :-) -- Chris Tapp opensou...@keylevel.com www.keylevel.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] what is the future for package_tar.bbclass?
The class is broken and unsupported. I have updated the docs indicating such. Scott >-Original Message- >From: yocto-boun...@yoctoproject.org [mailto:yocto- >boun...@yoctoproject.org] On Behalf Of Robert P. J. Day >Sent: Saturday, January 10, 2015 7:16 AM >To: Yocto discussion list >Subject: [yocto] what is the future for package_tar.bbclass? > > > once upon a time, richard purdie didn't see much use for the packaging class >file package_tar.bbclass: > >http://lists.openembedded.org/pipermail/openembedded-core/2014- >July/094843.html > >however, that packaging format is still mentioned at the very end of section >3.4 in the YP reference manual. is there a plan for keeping it, deleting it, >ignoring it, etc? > >rday > >-- > >=== >= >Robert P. J. Day Ottawa, Ontario, CANADA >http://crashcourse.ca > >Twitter: http://twitter.com/rpjday >LinkedIn: http://ca.linkedin.com/in/rpjday >=== >= >-- >___ >yocto mailing list >yocto@yoctoproject.org >https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] can't find the source code of kernel
Hi, Bruce
Thank you very much for your help. My problem have solved. Before, I was
working in "master" branch.
Switch to a new branch, I find the "source" directory ,what included the kernel
source code, in linux-qemuarm-standard-build.
Neil
-Original Message-
From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com]
Sent: Friday, January 16, 2015 12:36 PM
To: Wu, Neil [CLIMATE/RS/CN]; yocto@yoctoproject.org
Subject: Re: [yocto] can't find the source code of kernel
On 2015-01-15 8:13 PM, neil...@emerson.com wrote:
> Hi, Bruce
> Thank you for your reply.
> In the WORKDIR , it just has "linux-qemuarm-standard-build" and not have the
> "linux".
Are you sure you are building Yocto 1.7 and not the master branch ?
Until about a month ago, every build had the source along side the
split build directory .. in a directory called linux. But as I
mentioned, we are working to move the kernel to build out of the
sysroot/shared working directory.
>
> My WORKDIR directory is
> "~/poky/build/tmp/work/qemuarm-poky-linux-gnueabi/linux-yocto/3.14.24+gitAUTOINC+a227f20eff_6166316d47-r0",
> but I don't find the tarball of "linux-14.24"
> in download directory. It has tarball "linux-17.7.tar.xz".
>
> Do you think whether these is the reason?
They shouldn't be related. But that tar.xz you reference above is
clearly from some other kernel build than the linux yocto variant.
>
> I don't know how to set the version of linux when the project building the
> image.
> Maybe, I set the linux to 17.7 version, the problem can solve.
I'm not sure how you are getting a 17.7 tarball, but the linux-yocto
tree builds from a git repository, not a tarball.
In that directory where you see the qemuarm build you should also see a
git.indirectionsymlink that points to the git tree in downloads/git2/
Cheers,
Bruce
>
> Do you have any other better suggestion? Thank you very much.
>
> Neil
>
>
> -Original Message-
> From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com]
> Sent: Thursday, January 15, 2015 9:05 PM
> To: Wu, Neil [CLIMATE/RS/CN]; yocto@yoctoproject.org
> Subject: Re: [yocto] can't find the source code of kernel
>
> On 2015-01-15 5:03 AM, neil...@emerson.com wrote:
>> Hi ,all
>>
>> The version of poky is 1.7. I build the linux-yocto is successful .
>>
>> bitbake linux-yocto
>>
>> But, why I can't find the source code of linux in ${WORKDIR}.
>
> It should be there (note: it is about to move in master, but not in 1.7.1).
>
> In WORKDIR, you have "linux" (the source) and linux-$MACHINE-build (the
> build).
>
> Bruce
>
>>
>> Best wishes
>>
>> Neil
>>
>>
>>
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] dependency eglibc resulted in conflicting PREFERRED_PROVIDER entries being found
Hi ,all I try to build my custom image , The problem appears as follows: ERROR: Trying to resolve runtime dependency eglibc resulted in conflicting PREFERRED_PROVIDER entries being found. The providers found were: ['/home/ectrs/poky/meta/recipes-core/glibc/glibc-initial_2.20.bb', 'virtual:nativesdk:/home/ectrs/poky/meta/recipes-core/glibc/glibc-initial_2.20.bb'] The PREFERRED_PROVIDER entries resulting in this conflict were: ['PREFERRED_PROVIDER_virtual/arm-poky-linux-gnueabi-libc-initial = glibc-initial', 'PREFERRED_PROVIDER_virtual/nativesdk-i686-pokysdk-linux-libc-initial = nativesdk-glibc-initial'] Do you know how to resolve it ? Please help me . Thank you very much. Best wishes Neil -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
