Re: [yocto] bash specific syntax in bbclass files
I usually do following before starting Yocto on Ubuntu: -- # dpkg-reconfigure dash and select NO on the prompt -- The above will at least make bash as default shell. //Gaurang Shastri On Thu, May 2, 2013 at 1:37 PM, Paul Eggleton paul.eggle...@linux.intel.com wrote: On Wednesday 01 May 2013 19:13:19 seth bollinger wrote: I recently ran into a problem in meta-raspberrypi/classes/sdcard_image-rpi.bbclass The following was run through my default debian dash shell (I thought I switched a while back, but I must have reverted my VM image or something...). # If SDIMG_ROOTFS_TYPE is a .xz file use xzcat if [[ $SDIMG_ROOTFS_TYPE == *.xz ]] then The bash specific syntax ([[) failed in dash causing the else path to be traversed instead of the correct then path. The failure was silent and resulted in a blind copy of a compressed rootfs to the sdcard image. Of course this didn't run. :) 1. Is there particular shell syntax that class files should stick too? No bashisms should be used, so the above should really be changed. 2. I couldn't find a wildcard string search in dash. Can anyone suggest a more shell agnostic way to do this? AFAIK grep or awk is the only way. 3. Is there a way to guarantee we're running in bash if we're using bash specific syntax? Not that I'm aware of. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre ___ 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] bash specific syntax in bbclass files
On Friday 03 May 2013 12:06:45 Gaurang Shastri wrote: I usually do following before starting Yocto on Ubuntu: -- # dpkg-reconfigure dash and select NO on the prompt -- The above will at least make bash as default shell. Yes, except as I mentioned recently we shouldn't need to be forcing bash and we no longer advise users to do this. I am using Ubuntu with the default dash shell to build on here, for example. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH][eclipse-poky] systemtap: add possibility for user to point to his build folder
On Mon, 2013-04-29 at 14:15 +0200, Adrian Dudau wrote:
[Yocto #4223]
Signed-off-by: Adrian Dudau adrian.du...@enea.com
---
.../src/org/yocto/sdk/remotetools/Messages.java|1 +
.../org/yocto/sdk/remotetools/ShellSession.java|6 +++--
.../sdk/remotetools/actions/SystemtapHandler.java |3 ++-
.../sdk/remotetools/actions/SystemtapModel.java|6 +++--
.../actions/SystemtapSettingDialog.java| 28
.../org/yocto/sdk/remotetools/messages.properties |1 +
6 files changed, 40 insertions(+), 5 deletions(-)
diff --git
a/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/Messages.java
b/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/Messages.java
index 66ba62b..cbf2b05 100644
---
a/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/Messages.java
+++
b/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/Messages.java
@@ -40,6 +40,7 @@ public class Messages extends NLS {
public static String TerminalViewer_text;
//public static String Systemtap_KO_Text;
public static String Metadata_Location;
+ public static String Builddir_Location;
public static String User_ID;
public static String Remote_Host;
public static String Systemtap_Script;
diff --git
a/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/ShellSession.java
b/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/ShellSession.java
index 5602798..cbc8e55 100644
---
a/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/ShellSession.java
+++
b/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/ShellSession.java
@@ -66,12 +66,14 @@ public class ShellSession {
private String shellPath = null;
private final String initCmd;
private final File root;
+ private final File builddir;
private OutputStreamWriter out;
- public ShellSession(int shellType, File root, String initCmd,
OutputStream out) throws IOException {
+ public ShellSession(int shellType, File root, File builddir, String
initCmd, OutputStream out) throws IOException {
this.root = root;
+ this.builddir = builddir;
this.initCmd = initCmd;
if (out == null) {
this.out = new OutputStreamWriter(null);
@@ -95,7 +97,7 @@ public class ShellSession {
}
if (initCmd != null) {
- execute(source + initCmd);
+ execute(source + initCmd + +
builddir.getAbsolutePath());
}
}
diff --git
a/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/actions/SystemtapHandler.java
b/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/actions/SystemtapHandler.java
index 87094ee..dc11e39 100644
---
a/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/actions/SystemtapHandler.java
+++
b/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/actions/SystemtapHandler.java
@@ -35,6 +35,7 @@ public class SystemtapHandler extends AbstractHandler {
setting.open();
String metadata_location =
((SystemtapSettingDialog)setting).getMetadataLocation();
+ String builddir_location =
((SystemtapSettingDialog)setting).getBuilddirLocation();
String remote_host =
((SystemtapSettingDialog)setting).getRemoteHost();
String user_id = ((SystemtapSettingDialog)setting).getUserID();
String systemtap_script =
((SystemtapSettingDialog)setting).getSystemtapScript();
@@ -42,7 +43,7 @@ public class SystemtapHandler extends AbstractHandler {
if(setting.open() == BaseSettingDialog.OK) {
IProgressService progressService =
PlatformUI.getWorkbench().getProgressService();
- SystemtapModel op = new
SystemtapModel(metadata_location,remote_host, user_id, systemtap_script,
+ SystemtapModel op = new
SystemtapModel(metadata_location, builddir_location, remote_host, user_id,
systemtap_script,
systemtap_args,window.getShell().getDisplay());
try {
progressService.busyCursorWhile(op);
diff --git
a/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/actions/SystemtapModel.java
b/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/actions/SystemtapModel.java
index 0d22d97..c834097 100644
---
a/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/actions/SystemtapModel.java
+++
b/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/actions/SystemtapModel.java
@@ -26,6 +26,7 @@ public class SystemtapModel extends BaseModel {
protected static final
Re: [yocto] [meta-raspberrypi][PATCH 1/2] sdcard_image-rpi.bbclass: Fix error in conditional test
Merged to master. Thanks a lot. On Thu, May 2, 2013 at 1:33 PM, Paul Barker p...@paulbarker.me.uk wrote: On 1 May 2013 20:10, Andrei Gherzan and...@gherzan.ro wrote: I think I asked Seth a while ago and he confirmed that bash was his shell. I thought about dash as well. But as a matter of fact we should remove bashisms and make things as usable as possible. So maybe his patch makes sense after all. Based on Paul Eggleton's reply elsewhere: On 2 May 2013 09:07, Paul Eggleton paul.eggle...@linux.intel.com wrote: On Wednesday 01 May 2013 19:13:19 seth bollinger wrote: 2. I couldn't find a wildcard string search in dash. Can anyone suggest a more shell agnostic way to do this? AFAIK grep or awk is the only way. I think this patch probably does make sense. -- Paul Barker Email: p...@paulbarker.me.uk http://www.paulbarker.me.uk -- *Andrei Gherzan* m: +40.744.478.414 | f: +40.31.816.28.12 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi][PATCH] netbase: Remove bbappend and files
Merged to master.
Thanks a lot.
On Mon, Apr 22, 2013 at 10:19 PM, Paul Barker p...@paulbarker.me.uk wrote:
Dropped raspberrypi modifications to hosts and interfaces files as they are
unnecessary.
Signed-off-by: Paul Barker p...@paulbarker.me.uk
---
recipes-core/netbase/netbase-5.0/raspberrypi/hosts |2 --
recipes-core/netbase/netbase-5.0/raspberrypi/interfaces | 15
---
recipes-core/netbase/netbase_5.0.bbappend |3 ---
3 files changed, 20 deletions(-)
delete mode 100644 recipes-core/netbase/netbase-5.0/raspberrypi/hosts
delete mode 100644 recipes-core/netbase/netbase-5.0/raspberrypi/interfaces
delete mode 100644 recipes-core/netbase/netbase_5.0.bbappend
diff --git a/recipes-core/netbase/netbase-5.0/raspberrypi/hosts
b/recipes-core/netbase/netbase-5.0/raspberrypi/hosts
deleted file mode 100644
index 7d87a18..000
--- a/recipes-core/netbase/netbase-5.0/raspberrypi/hosts
+++ /dev/null
@@ -1,2 +0,0 @@
-127.0.0.1 localhost.localdomain localhost
raspberrypi rpi
-
diff --git a/recipes-core/netbase/netbase-5.0/raspberrypi/interfaces
b/recipes-core/netbase/netbase-5.0/raspberrypi/interfaces
deleted file mode 100644
index 00ae607..000
--- a/recipes-core/netbase/netbase-5.0/raspberrypi/interfaces
+++ /dev/null
@@ -1,15 +0,0 @@
-# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
-
-# The loopback interface
-auto lo
-iface lo inet loopback
-
-# Wireless interfaces
-iface wlan0 inet dhcp
- wireless_mode managed
- wireless_essid any
- wpa-driver wext
- wpa-conf /etc/wpa_supplicant.conf
-
-# Bluetooth networking
-iface bnep0 inet dhcp
diff --git a/recipes-core/netbase/netbase_5.0.bbappend
b/recipes-core/netbase/netbase_5.0.bbappend
deleted file mode 100644
index 36432f5..000
--- a/recipes-core/netbase/netbase_5.0.bbappend
+++ /dev/null
@@ -1,3 +0,0 @@
-FILESEXTRAPATHS_prepend := ${THISDIR}/${PN}:
-# Don't forget to bump PRINC if you update the extra files.
-PRINC = 1
--
1.7.10.4
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
--
*Andrei Gherzan*
m: +40.744.478.414 | f: +40.31.816.28.12
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi][PATCH] use right license name for GPLv2
Merged to master. Thanks a lot. On Thu, Mar 14, 2013 at 3:02 PM, Eric Bénard e...@eukrea.com wrote: Hi Andrei, Le Wed, 13 Mar 2013 20:01:54 +0200, Andrei Gherzan and...@gherzan.ro a écrit : The SPDX name for GPLv2 (http://spdx.org/licenses/) is GPL-2.0 so I'd like to use this. OE-core is mainly using GPLv2 thus the change proposal to be consistant. And one more thing, please add the recipe name in the commit log - something like: *rpi-first-run-wizard.bb: Use right license name for GPLv2* 2 recipes were concerned in this patch so I din't put their names in the 1st line to keep it short. Eric -- *Andrei Gherzan* m: +40.744.478.414 | f: +40.31.816.28.12 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi][PATCH 2/2] xserver-xf86-config: fix do_install
Can't replicate this issue and somebody who experienced it in the past
confirmed me that it was someway fixed. So I will drop this patch.
Thanks.
On Wed, Mar 13, 2013 at 6:47 PM, Andrei Gherzan and...@gherzan.ro wrote:
Hey Andreas,
Is this sill needed? Did you test this lately?
On Sun, Jan 27, 2013 at 4:35 PM, Andreas Müller
schnitzelt...@googlemail.com wrote:
On Sat, Jan 26, 2013 at 11:58 PM, Andrei Gherzan and...@gherzan.ro
wrote:
On Thu, Jan 24, 2013 at 10:57:42PM +0100, Andreas Müller wrote:
for some reason wildcards don't work in current head. Error message
was:
| DEBUG: Executing shell function do_install
| install: cannot stat
`/home/Superandy/tmp/oe-core-eglibc/work/raspberrypi-angstrom-linux-gnueabi/xserver-xf86-config/0.1-r18/xorg.conf.d/*':
No such file or directory
I can't reproduce your error. For me this works. Maybe was something
broken in
oe-core? Anyway it seems to be fixed now. Would you retest it please
Will do that
Signed-off-by: Andreas Müller schnitzelt...@googlemail.com
---
.../xorg-xserver/xserver-xf86-config_0.1.bbappend |6 --
1 files changed, 4 insertions(+), 2 deletions(-)
diff --git
a/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend
b/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend
index 65931e2..a8b8e8c 100644
--- a/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend
+++ b/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend
@@ -1,12 +1,14 @@
FILESEXTRAPATHS_prepend := ${THISDIR}/${PN}:
# Don't forget to bump PRINC if you update the extra files.
-PRINC := ${@int(PRINC) + 5}
+PRINC := ${@int(PRINC) + 6}
THISDIR := ${@os.path.dirname(bb.data.getVar('FILE', d, True))}
FILESPATH =. ${@base_set_filespath([${THISDIR}/${PN}], d)}:
-SRC_URI_append_raspberrypi = file://xorg.conf.d/*
+SRC_URI_append_raspberrypi = \
+ file://xorg.conf.d/10-evdev.conf \
+
I don't find this lin ebreak necesssary here. And if it was, don't
combine
formating commits with other fixes.
Oops this was left over from some testing.
Andreas
--
*Andrei Gherzan*
m: +40.744.478.414 | f: +40.31.816.28.12
--
*Andrei Gherzan*
m: +40.744.478.414 | f: +40.31.816.28.12
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi][PATCH 2/2] xserver-xf86-config: fix do_install
On Fri, May 3, 2013 at 11:33 AM, Andrei Gherzan and...@gherzan.ro wrote: Can't replicate this issue and somebody who experienced it in the past confirmed me that it was someway fixed. So I will drop this patch. Thanks. I think wildcards are qorking currently - you can drop this one Andreas ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] bash specific syntax in bbclass files
If every other distribution, over the next year, switched to python-3 as their default, but (instead of updating) future versions of Ubuntu installed a symlink called python-3 pointing back to python-2, would that hold back Yocto from adopting python-3-isms too? It's sad how Ubuntu has so effectively killed the adoption of all features of bash (the default shell on many Linux distributions) introduced in the last 10 years by masquerading their crippled shell as bash. And it's even sadder to see how so many projects, in response, have simply said let's write all our shell scripts in original Bourne shell syntax as a result. Disclaimer: I didn't write the shell code in question, so please don't assume I'm taking this personally. I'm just making a general observation. ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] bash specific syntax in bbclass files
On Fri, 3 May 2013, Trevor Woerner wrote: If every other distribution, over the next year, switched to python-3 as their default, but (instead of updating) future versions of Ubuntu installed a symlink called python-3 pointing back to python-2, would that hold back Yocto from adopting python-3-isms too? It's sad how Ubuntu has so effectively killed the adoption of all features of bash (the default shell on many Linux distributions) introduced in the last 10 years by masquerading their crippled shell as bash. And it's even sadder to see how so many projects, in response, have simply said let's write all our shell scripts in original Bourne shell syntax as a result. personally, i try to be posix-compliant as much as possible to avoid this kind of grief. 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
Re: [yocto] bash specific syntax in bbclass files
On Friday 03 May 2013 07:40:24 Trevor Woerner wrote: If every other distribution, over the next year, switched to python-3 as their default, but (instead of updating) future versions of Ubuntu installed a symlink called python-3 pointing back to python-2, would that hold back Yocto from adopting python-3-isms too? That's not quite the same situation and I don't think they would do that. They might however (as I guess they do now) point the standard python binary at python2 and then expect those using python3 scripts to explicitly request python3. It's sad how Ubuntu has so effectively killed the adoption of all features of bash (the default shell on many Linux distributions) introduced in the last 10 years by masquerading their crippled shell as bash. And it's even sadder to see how so many projects, in response, have simply said let's write all our shell scripts in original Bourne shell syntax as a result. Well, that is one way of looking at it; the change to dash in Ubuntu has indeed been quite a painful road (not so much for us but for the Linux ecosystem in general). On the other hand, it's not that dash is masquerading as bash, it's selected as providing /bin/sh. If you have written a shell script that starts with #!/bin/sh and then proceeds to use bash-specific syntax, sure it might well work on most systems because they're using bash, but the script started with something that wasn't true - it's not in fact a standard Unix Bourne-compatible shell script, it's a bash script. It's also worth mentioning that we have had some benefit out of these changes, in that the scripts that have been fixed that end up running on the target will now more likely run when /bin/sh is provided by ash (i.e. busybox). Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi][PATCH] rpi-gpio: renamed from RPi-GPIO
Package names shouldn't contain capital letters.
Signed-off-by: Paul Barker p...@paulbarker.me.uk
---
.../python/RPi-GPIO/don-t-install-setuptools.patch | 16
recipes-devtools/python/RPi-GPIO_0.2.0.bb | 21 -
.../python/rpi-gpio/don-t-install-setuptools.patch | 16
recipes-devtools/python/rpi-gpio_0.2.0.bb | 21 +
4 files changed, 37 insertions(+), 37 deletions(-)
delete mode 100644
recipes-devtools/python/RPi-GPIO/don-t-install-setuptools.patch
delete mode 100644 recipes-devtools/python/RPi-GPIO_0.2.0.bb
create mode 100644
recipes-devtools/python/rpi-gpio/don-t-install-setuptools.patch
create mode 100644 recipes-devtools/python/rpi-gpio_0.2.0.bb
diff --git a/recipes-devtools/python/RPi-GPIO/don-t-install-setuptools.patch
b/recipes-devtools/python/RPi-GPIO/don-t-install-setuptools.patch
deleted file mode 100644
index bc71443..000
--- a/recipes-devtools/python/RPi-GPIO/don-t-install-setuptools.patch
+++ /dev/null
@@ -1,16 +0,0 @@
-We already have setuptools python module so we will use that and not the
-one provided in this package.
-
-Upstream-Status: Inappropriate [embedded specific]
-Signed-off-by: Andrei Gherzan and...@gherzan.ro
-
-Index: RPi.GPIO-0.2.0/setup.py
-===
RPi.GPIO-0.2.0.orig/setup.py 2012-05-24 13:17:31.0 +0300
-+++ RPi.GPIO-0.2.0/setup.py2012-08-22 00:56:59.049001018 +0300
-@@ -1,6 +1,4 @@
- #!/usr/bin/env python
--import distribute_setup
--distribute_setup.use_setuptools()
- from setuptools import setup, find_packages
- import platform
diff --git a/recipes-devtools/python/RPi-GPIO_0.2.0.bb
b/recipes-devtools/python/RPi-GPIO_0.2.0.bb
deleted file mode 100644
index 73122cd..000
--- a/recipes-devtools/python/RPi-GPIO_0.2.0.bb
+++ /dev/null
@@ -1,21 +0,0 @@
-DESCRIPTION = A module to control Raspberry Pi GPIO channels
-HOMEPAGE = http://code.google.com/p/raspberry-gpio-python/;
-SECTION = devel/python
-LICENSE = MIT
-LIC_FILES_CHKSUM = file://LICENCE.txt;md5=ee5754ae9d5f8061d6d4ccd9c9fe0061
-
-SRCNAME = RPi.GPIO
-PR = r0
-
-SRC_URI = \
-
http://pypi.python.org/packages/source/R/RPi.GPIO/${SRCNAME}-${PV}.tar.gz \
- file://don-t-install-setuptools.patch \
-
-S = ${WORKDIR}/${SRCNAME}-${PV}
-
-inherit setuptools
-
-COMPATIBLE_MACHINE = raspberrypi
-
-SRC_URI[md5sum] = 0fc4bfa6aabc856b0b75252a40ac75cc
-SRC_URI[sha256sum] =
fcfd97dc9687dde76b13b9d12c122e71b13e2ba09a62913d7b8d9ddbb3e8cabf
diff --git a/recipes-devtools/python/rpi-gpio/don-t-install-setuptools.patch
b/recipes-devtools/python/rpi-gpio/don-t-install-setuptools.patch
new file mode 100644
index 000..bc71443
--- /dev/null
+++ b/recipes-devtools/python/rpi-gpio/don-t-install-setuptools.patch
@@ -0,0 +1,16 @@
+We already have setuptools python module so we will use that and not the
+one provided in this package.
+
+Upstream-Status: Inappropriate [embedded specific]
+Signed-off-by: Andrei Gherzan and...@gherzan.ro
+
+Index: RPi.GPIO-0.2.0/setup.py
+===
+--- RPi.GPIO-0.2.0.orig/setup.py 2012-05-24 13:17:31.0 +0300
RPi.GPIO-0.2.0/setup.py2012-08-22 00:56:59.049001018 +0300
+@@ -1,6 +1,4 @@
+ #!/usr/bin/env python
+-import distribute_setup
+-distribute_setup.use_setuptools()
+ from setuptools import setup, find_packages
+ import platform
diff --git a/recipes-devtools/python/rpi-gpio_0.2.0.bb
b/recipes-devtools/python/rpi-gpio_0.2.0.bb
new file mode 100644
index 000..73122cd
--- /dev/null
+++ b/recipes-devtools/python/rpi-gpio_0.2.0.bb
@@ -0,0 +1,21 @@
+DESCRIPTION = A module to control Raspberry Pi GPIO channels
+HOMEPAGE = http://code.google.com/p/raspberry-gpio-python/;
+SECTION = devel/python
+LICENSE = MIT
+LIC_FILES_CHKSUM = file://LICENCE.txt;md5=ee5754ae9d5f8061d6d4ccd9c9fe0061
+
+SRCNAME = RPi.GPIO
+PR = r0
+
+SRC_URI = \
+
http://pypi.python.org/packages/source/R/RPi.GPIO/${SRCNAME}-${PV}.tar.gz \
+ file://don-t-install-setuptools.patch \
+
+S = ${WORKDIR}/${SRCNAME}-${PV}
+
+inherit setuptools
+
+COMPATIBLE_MACHINE = raspberrypi
+
+SRC_URI[md5sum] = 0fc4bfa6aabc856b0b75252a40ac75cc
+SRC_URI[sha256sum] =
fcfd97dc9687dde76b13b9d12c122e71b13e2ba09a62913d7b8d9ddbb3e8cabf
--
1.8.2.2
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Trouble integrating meta-virtualization
Hello, I'm trying to build an image using some components from meta-virtualization, and it's failing because it can't find many of the dependent modules. I'm posting this on the main yocto mailing list since it's more of a general question of 'where are these things?' Specifics: * poky @ git tag 'dylan 9.0.0' * meta-virtualization @ git commit bb8c2c420bca06c67deb05e9f63e101752110759 (4/25/2013) * poky-contrib @jzhang/2342 (latest commit, tried other branches with similar results) * BSP based on 'crystalforest' Here's how it fails: WARNING: Host distribution CentOS-5.9 has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution. Loading cache: 100% |##| ETA: 00:00:00 Loaded 2335 entries from dependency cache. Parsing recipes: 100% || Time: 00:00:02 Parsing of 1674 .bb files complete (1531 cached, 143 parsed). 2296 targets, 75 skipped, 0 masked, 0 errors. Build Configuration: BB_VERSION= 1.18.0 BUILD_SYS = x86_64-linux NATIVELSBSTRING = CentOS-5.9 TARGET_SYS= x86_64-poky-linux MACHINE = scw-appscard DISTRO= poky DISTRO_VERSION= 1.4 TUNE_FEATURES = m64 TARGET_FPU= meta meta-yocto meta-yocto-bsp= scw-dylan:789b2b7e0cca404ff8ba8ed5ba823d215e6ba5b4 meta-intel meta-crystalforest = dylan:6147ba0e962c3d7ba28b53b9b930f1bed5833c90 meta-virtualization = master:bb8c2c420bca06c67deb05e9f63e101752110759 meta-scw-appscard = unknown:unknown meta = jzhang/2342:edfa2b0331248facb9b0db86e3b3229e32ddbf20 NOTE: Resolving any missing task queue dependencies ERROR: Nothing PROVIDES 'bridge-utils' (but /b/ben/yocto2/meta-virtualization/recipes-extended/libvirt/libvirt_1.0.3.bb DEPENDS on or otherwise requires it) NOTE: Runtime target 'libvirt' is unbuildable, removing... Missing or unbuildable dependency chain was: ['libvirt', 'bridge-utils'] ERROR: Required build target 'scw-image-libvirt' has no buildable providers. Missing or unbuildable dependency chain was: ['scw-image-libvirt', 'libvirt', 'bridge-utils'] If I let it continue using 'bit bake -k', all sorts of other common utilities are not found, such as lvm2, ebtables, dnsmasq, … My bblayers.conf file has this: BBLAYERS ?= \ /b/ben/yocto2/poky/meta \ /b/ben/yocto2/poky/meta-yocto \ /b/ben/yocto2/poky/meta-yocto-bsp \ /b/ben/yocto2/meta-intel \ /b/ben/yocto2/meta-intel/meta-crystalforest \ /b/ben/yocto2/meta-virtualization \ /b/ben/yocto2/meta-scw-appscard \ /b/ben/yocto2/poky-contrib/meta \ So my question is: is there a repo other than poky-contrib that contains all of these things, is it up to me to find them, or am I missing a key concept? I'm very new to Yocto, and while the documentation is excellent, it is also vast. thanks a lot! Ben ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Trouble integrating meta-virtualization - ANSWERED
Sorry for the spam. I eventually found everything on openembedded.orghttp://openembedded.org. regards, Ben On May 3, 2013, at 4:44 PM, Ben Warren ben.war...@spidercloud.commailto:ben.war...@spidercloud.com wrote: Hello, I'm trying to build an image using some components from meta-virtualization, and it's failing because it can't find many of the dependent modules. I'm posting this on the main yocto mailing list since it's more of a general question of 'where are these things?' Specifics: * poky @ git tag 'dylan 9.0.0' * meta-virtualization @ git commit bb8c2c420bca06c67deb05e9f63e101752110759 (4/25/2013) * poky-contrib @jzhang/2342 (latest commit, tried other branches with similar results) * BSP based on 'crystalforest' Here's how it fails: WARNING: Host distribution CentOS-5.9 has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution. Loading cache: 100% |##| ETA: 00:00:00 Loaded 2335 entries from dependency cache. Parsing recipes: 100% || Time: 00:00:02 Parsing of 1674 .bb files complete (1531 cached, 143 parsed). 2296 targets, 75 skipped, 0 masked, 0 errors. Build Configuration: BB_VERSION= 1.18.0 BUILD_SYS = x86_64-linux NATIVELSBSTRING = CentOS-5.9 TARGET_SYS= x86_64-poky-linux MACHINE = scw-appscard DISTRO= poky DISTRO_VERSION= 1.4 TUNE_FEATURES = m64 TARGET_FPU= meta meta-yocto meta-yocto-bsp= scw-dylan:789b2b7e0cca404ff8ba8ed5ba823d215e6ba5b4 meta-intel meta-crystalforest = dylan:6147ba0e962c3d7ba28b53b9b930f1bed5833c90 meta-virtualization = master:bb8c2c420bca06c67deb05e9f63e101752110759 meta-scw-appscard = unknown:unknown meta = jzhang/2342:edfa2b0331248facb9b0db86e3b3229e32ddbf20 NOTE: Resolving any missing task queue dependencies ERROR: Nothing PROVIDES 'bridge-utils' (but /b/ben/yocto2/meta-virtualization/recipes-extended/libvirt/libvirt_1.0.3.bb DEPENDS on or otherwise requires it) NOTE: Runtime target 'libvirt' is unbuildable, removing... Missing or unbuildable dependency chain was: ['libvirt', 'bridge-utils'] ERROR: Required build target 'scw-image-libvirt' has no buildable providers. Missing or unbuildable dependency chain was: ['scw-image-libvirt', 'libvirt', 'bridge-utils'] If I let it continue using 'bit bake -k', all sorts of other common utilities are not found, such as lvm2, ebtables, dnsmasq, … My bblayers.conf file has this: BBLAYERS ?= \ /b/ben/yocto2/poky/meta \ /b/ben/yocto2/poky/meta-yocto \ /b/ben/yocto2/poky/meta-yocto-bsp \ /b/ben/yocto2/meta-intel \ /b/ben/yocto2/meta-intel/meta-crystalforest \ /b/ben/yocto2/meta-virtualization \ /b/ben/yocto2/meta-scw-appscard \ /b/ben/yocto2/poky-contrib/meta \ So my question is: is there a repo other than poky-contrib that contains all of these things, is it up to me to find them, or am I missing a key concept? I'm very new to Yocto, and while the documentation is excellent, it is also vast. thanks a lot! Ben ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Trouble integrating meta-virtualization
On 4 May 2013 00:44, Ben Warren ben.war...@spidercloud.com wrote: Hello, I'm trying to build an image using some components from meta-virtualization, and it's failing because it can't find many of the dependent modules. I'm posting this on the main yocto mailing list since it's more of a general question of 'where are these things?' Each layer should have a README file specifying its dependencies. See https://git.yoctoproject.org/cgit/cgit.cgi/meta-virtualization/tree/README or README in your local clone of the tree. In this case the layer seems to depend on meta-oe and meta-networking, both within the meta-openembedded group of layers. Hope this helps, -- Paul Barker Email: p...@paulbarker.me.uk http://www.paulbarker.me.uk ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Trouble integrating meta-virtualization
On May 3, 2013, at 5:35 PM, Paul Barker p...@paulbarker.me.uk wrote: On 4 May 2013 00:44, Ben Warren ben.war...@spidercloud.com wrote: Hello, I'm trying to build an image using some components from meta-virtualization, and it's failing because it can't find many of the dependent modules. I'm posting this on the main yocto mailing list since it's more of a general question of 'where are these things?' Each layer should have a README file specifying its dependencies. See https://git.yoctoproject.org/cgit/cgit.cgi/meta-virtualization/tree/README or README in your local clone of the tree. In this case the layer seems to depend on meta-oe and meta-networking, both within the meta-openembedded group of layers. Hope this helps, Yes it does. Thank you very much. regards, Ben ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
