Re: [yocto] Using wic from a Bitbake task
Hello all, Will it be valuable to create another option (which assume that bitbake is running and get values from variables directly) for wic which we can invoke from the image recipe as part of image creation process. Noor -Original Message- From: Usman, Fahad Sent: Sunday, July 26, 2015 10:25 PM To: yocto@yoctoproject.org Cc: Ahsan, Noor; Khandavilli, Arun Subject: Using wic from a Bitbake task Hello, Is it possible to invoke 'wic create' command from a bitbake task. As currently it is implemented to be run as a standalone tool and if we invoke it from a task, the 'bitbake -e' command fails, since more than one instances of bitbake cannot be run from a single build directory. We want to emit an SD card image as part of build artifacts when an image recipe is built. And we don't want to use the boot-directdisk.bbclass as it's going to be deprecated in favour of wic. Thanks, Fahad Usman. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] include all kernel modules in image
On Sun, Jul 26, 2015 at 8:04 PM, Trevor Woerner wrote: > > Is there a generic way to say "please include all of these packages" > instead of having to list each and every one of them in a > CORE_IMAGE_EXTRA_INSTALL variable? Adding "kernel-modules" to that > variable doesn't work (I get an error executing a python function -- No > such file or directory). adding kernel-modules should work. it's a meta package that RDEPENDS on kernel-modules-*, e.g. in my build (oe-core/master) $ dpkg -I tmp-glibc/deploy/ipk/ifc6410/kernel-modules_3.19-r0_ifc6410.ipk new debian package, version 2.0. size 1518 bytes: control archive=1222 bytes. 3660 bytes,12 lines control Package: kernel-modules Version: 3.19-r0 Description: linux-linaro-qcomlt version 3.19-r0 Kernel modules meta package Section: base Priority: optional Maintainer: OE-Core Developers License: GPLv2 Architecture: ifc6410 OE: linux-linaro-qcomlt Depends: kernel-module-navman, kernel-module-gspca-m5602, kernel-module-g-ether, kernel-module-ti-usb-3410-5052, kernel-module-zr364xx, kernel-module-hid-microsoft, kernel-module-gspca-spca561, kernel-module-mct-u232, kernel-module-gspca-t613, kernel-module-gspca-sn9c2028, kernel-module-iuu-phoenix, kernel-module-ezusb, kernel-module-wishbone-serial, kernel-module-cypress-m8, kernel-module-usb-f-mass-storage, kernel-module-f81232, kernel-module-gspca-benq, kernel-module-symbolserial, kernel-module-usb-f-ecm, kernel-module-xsens-mt, kernel-module-spcp8x5, kernel-module-gspca-nw80x, kernel-module-kl5kusb105, kernel-module-usb-serial-simple, kernel-module-lcd, kernel-module-videobuf-core, kernel-module-gspca-gl860, kernel-module-cp210x, kernel-module-omninet, kernel-module-gspca-topro, kernel-module-gspca-se401, kernel-module-ir-usb, kernel-module-mac80211, kernel-module-gspca-sq905, kernel-module-mos7840, kernel-module-gspca-finepix, kernel-module-ansi-cprng, kernel-module-gspca-sunplus, kernel-module-cfg80211, kernel-module-gspca-ov534-9, kernel-module-gspca-pac7302, kernel-module-gspca-sq930x, kernel-module-aircable, kernel-module-gspca-dtcs033, kernel-module-oti6858, kernel-module-gspca-konica, kernel-module-gspca-pac7311, kernel-module-gadgetfs, kernel-module-gspca-ov534, kernel-module-gspca-sonixj, kernel-module-nfsd, kernel-module-usb-f-ecm-subset, kernel-module-gspca-sonixb, kernel-module-gspca-tv8532, kernel-module-whiteheat, kernel-module-gspca-stk014, kernel-module-gspca-spca1528, kernel-module-gspca-vc032x, kernel-module-gspca-stv06xx, kernel-module-safe-serial, kernel-module-gspca-jl2005bcd, kernel-module-digi-acceleport, kernel-module-qcserial, kernel-module-keyspan, kernel-module-quatech2, kernel-module-mos7720, kernel-module-configfs, kernel-module-keyspan-pda, kernel-module-ark3116, kernel-module-gspca-conex, kernel-module-gspca-spca501, kernel-module-gspca-spca500, kernel-module-gspca-spca506, kernel-module-gspca-spca505, kernel-module-gspca-spca508, kernel-module-gspca-kinect, kernel-module-option, kernel-module-ipaq, kernel-module-g-ffs, kernel-module-ssu100, kernel-module-gspca-cpia1, kernel-module-libcomposite, kernel-module-gspca-mr97310a, kernel-module-usb-f-rndis, kernel-module-gspca-ov519, kernel-module-io-ti, kernel-module-kobil-sct, kernel-module-empeg, kernel-module-usb-wwan, kernel-module-metro-usb, kernel-module-gspca-stv0680, kernel-module-garmin-gps, kernel-module-qcaux, kernel-module-belkin-sa, kernel-module-mxuport, kernel-module-ath6kl-sdio, kernel-module-gspca-sn9c20x, kernel-module-sierra, kernel-module-pl2303, kernel-module-videobuf-vmalloc, kernel-module-gspca-xirlink-cit, kernel-module-ftdi-sio, kernel-module-hid-magicmouse, kernel-module-io-edgeport, kernel-module-visor, kernel-module-ath6kl-core, kernel-module-gspca-etoms, kernel-module-opticon, kernel-module-pwc, kernel-module-ipw, kernel-module-gspca-mars, kernel-module-gspca-vicam, kernel-module-usbserial, kernel-module-gspca-sq905c, kernel-module-cyberjack, kernel-module-u-ether, kernel-module-ch341, kernel-module-gspca-jeilinj, kernel-module-gspca-pac207, kernel-module-usb-f-fs, kernel-module-hid-logitech, kernel-module-g-mass-storage, kernel-module-gspca-stk1135, kernel-module-gspca-zc3xx Source: git://git.linaro.org/landing-teams/working/qualcomm/kernel.git;branch=release/qcomlt-3.19;protocol=https file://defconfig -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Using wic from a Bitbake task
On 26 July 2015 at 18:24, Usman, Fahad wrote: > Is it possible to invoke 'wic create' command from a bitbake task. As > currently it is implemented to be run as a standalone tool and if we invoke > it from a task, the 'bitbake -e' command fails, since more than one > instances of bitbake cannot be run from a single build directory. Not yet, but there's a bug for that: https://bugzilla.yoctoproject.org/show_bug.cgi?id=7672 Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] include all kernel modules in image
Hey Nicolas,
On 07/27/15 04:50, Nicolas Dechesne wrote:
> On Sun, Jul 26, 2015 at 8:04 PM, Trevor Woerner wrote:
>
> adding kernel-modules should work. it's a meta package that RDEPENDS
> on kernel-modules-*, e.g. in my build (oe-core/master)
For some reason adding:
CORE_IMAGE_EXTRA_INSTALL += "kernel-modules"
to my build produces:
ERROR: Error executing a python function in
/z/layerindex/layers/openembedded-core/meta/recipes-core/images/core-image-minimal.bb:
The stack trace of python calls that resulted in this exception/failure was:
File: 'do_rootfs', lineno: 17, function:
0013:# generate final images
0014:create_image(d)
0015:
0016:
*** 0017:do_rootfs(d)
0018:
File: 'do_rootfs', lineno: 11, function: do_rootfs
0007:# generate the initial manifest
0008:create_manifest(d)
0009:
0010:# generate rootfs
*** 0011:create_rootfs(d)
0012:
0013:# generate final images
0014:create_image(d)
0015:
File: '/z/layerindex/layers/openembedded-core/meta/lib/oe/rootfs.py',
lineno: 933, function: create_rootfs
0929:img_type = d.getVar('IMAGE_PKGTYPE', True)
0930:if img_type == "rpm":
0931:RpmRootfs(d, manifest_dir).create()
0932:elif img_type == "ipk":
*** 0933:OpkgRootfs(d, manifest_dir).create()
0934:elif img_type == "deb":
0935:DpkgRootfs(d, manifest_dir).create()
0936:
0937:os.environ.clear()
File: '/z/layerindex/layers/openembedded-core/meta/lib/oe/rootfs.py',
lineno: 215, function: create
0211:
0212:self._run_ldconfig()
0213:
0214:if self.d.getVar('USE_DEPMOD', True) != "0":
*** 0215:self._generate_kernel_module_deps()
0216:
0217:self._cleanup()
0218:self._log_check()
0219:
File: '/z/layerindex/layers/openembedded-core/meta/lib/oe/rootfs.py',
lineno: 332, function: _generate_kernel_module_deps
0328:versioned_modules_dir =
os.path.join(self.image_rootfs, modules_dir, kernel_ver)
0329:
0330:bb.utils.mkdirhier(versioned_modules_dir)
0331:
*** 0332:self._exec_shell_cmd(['depmodwrapper', '-a', '-b',
self.image_rootfs, kernel_ver])
0333:
0334:"""
0335:Create devfs:
0336:* IMAGE_DEVICE_TABLE is the old name to an absolute path
to a device table file
File: '/z/layerindex/layers/openembedded-core/meta/lib/oe/rootfs.py',
lineno: 156, function: _exec_shell_cmd
0152:else:
0153:exec_cmd = cmd
0154:
0155:try:
*** 0156:subprocess.check_output(exec_cmd,
stderr=subprocess.STDOUT)
0157:except subprocess.CalledProcessError as e:
0158:return("Command '%s' returned %d:\n%s" % (e.cmd,
e.returncode, e.output))
0159:
0160:return None
File: '/usr/lib64/python2.7/subprocess.py', lineno: 566, function:
check_output
0562:'ls: non_existent_file: No such file or directory\n'
0563:"""
0564:if 'stdout' in kwargs:
0565:raise ValueError('stdout argument not allowed, it will
be overridden.')
*** 0566:process = Popen(stdout=PIPE, *popenargs, **kwargs)
0567:output, unused_err = process.communicate()
0568:retcode = process.poll()
0569:if retcode:
0570:cmd = kwargs.get("args")
File: '/usr/lib64/python2.7/subprocess.py', lineno: 710, function: __init__
0706:cwd, env, universal_newlines,
0707:startupinfo, creationflags,
shell, to_close,
0708:p2cread, p2cwrite,
0709:c2pread, c2pwrite,
*** 0710:errread, errwrite)
0711:except Exception:
0712:# Preserve original exception in case os.close raises.
0713:exc_type, exc_value, exc_trace = sys.exc_info()
0714:
File: '/usr/lib64/python2.7/subprocess.py', lineno: 1327, function:
_execute_child
1323:except OSError as e:
1324:if e.errno != errno.ECHILD:
1325:raise
1326:child_exception = pickle.loads(data)
*** 1327:raise child_exception
1328:
1329:
1330:def _handle_exitstatus(self, sts,
_WIFSIGNALED=os.WIFSIGNALED,
1331:_WTERMSIG=os.WTERMSIG, _WIFEXITED=os.WIFEXITED,
Exception: OSError: [Errno 2] No such file or directory
DEBUG: Executing python function rootfs_process_ignore
DEBUG: Python function rootfs_process_ignore finished
DEBUG: Executing python function rootfs_runtime_mapping
DEBUG: Python function rootfs_runtime_mapping finished
DEBUG: Executing python function do_rootfs
NOTE: ## Generate rootfs ###
NOTE: Executing
'/z/layerindex/firefly/tmp/sysroots/x86_64-linux/usr/bin/opkg-make-
Re: [yocto] include all kernel modules in image
On Mon, Jul 27, 2015 at 1:03 PM, Trevor Woerner wrote:
> File: '/z/layerindex/layers/openembedded-core/meta/lib/oe/rootfs.py',
> lineno: 156, function: _exec_shell_cmd
> 0152:else:
> 0153:exec_cmd = cmd
> 0154:
> 0155:try:
> *** 0156:subprocess.check_output(exec_cmd,
> stderr=subprocess.STDOUT)
> 0157:except subprocess.CalledProcessError as e:
> 0158:return("Command '%s' returned %d:\n%s" % (e.cmd,
> e.returncode, e.output))
> 0159:
> 0160:return None
> File: '/usr/lib64/python2.7/subprocess.py', lineno: 566, function:
> check_output
> 0562:'ls: non_existent_file: No such file or directory\n'
> 0563:"""
> 0564:if 'stdout' in kwargs:
> 0565:raise ValueError('stdout argument not allowed, it will
> be overridden.')
> *** 0566:process = Popen(stdout=PIPE, *popenargs, **kwargs)
> 0567:output, unused_err = process.communicate()
> 0568:retcode = process.poll()
> 0569:if retcode:
> 0570:cmd = kwargs.get("args")
> File: '/usr/lib64/python2.7/subprocess.py', lineno: 710, function: __init__
> 0706:cwd, env, universal_newlines,
> 0707:startupinfo, creationflags,
> shell, to_close,
> 0708:p2cread, p2cwrite,
> 0709:c2pread, c2pwrite,
> *** 0710:errread, errwrite)
> 0711:except Exception:
> 0712:# Preserve original exception in case os.close raises.
> 0713:exc_type, exc_value, exc_trace = sys.exc_info()
> 0714:
> File: '/usr/lib64/python2.7/subprocess.py', lineno: 1327, function:
> _execute_child
> 1323:except OSError as e:
> 1324:if e.errno != errno.ECHILD:
> 1325:raise
> 1326:child_exception = pickle.loads(data)
> *** 1327:raise child_exception
> 1328:
> 1329:
> 1330:def _handle_exitstatus(self, sts,
> _WIFSIGNALED=os.WIFSIGNALED,
> 1331:_WTERMSIG=os.WTERMSIG, _WIFEXITED=os.WIFEXITED,
> Exception: OSError: [Errno 2] No such file or directory
well, something's definitely wrong here.. are you doing a minimal
OE-core build? can you try to reproduce / narrow down? Are you running
recent master? I have no idea what the error means here.. but clearly,
it works for me, so that could be something from your environment..
nico
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] include all kernel modules in image
On 07/27/15 08:04, Nicolas Dechesne wrote:
> On Mon, Jul 27, 2015 at 1:03 PM, Trevor Woerner wrote:
>
>
> well, something's definitely wrong here.. are you doing a minimal
> OE-core build? can you try to reproduce / narrow down? Are you running
> recent master? I have no idea what the error means here.. but clearly,
> it works for me, so that could be something from your environment..
I agree.
The error appears to be some sort of "file not found". The command it is
running when it fails is:
depmodwrapper
/z/layerindex/firefly/tmp/work/firefly_emmc_mainline-poky-linux-gnueabi/core-image-minimal/1.0-r0/rootfs
4.0.0-rc1
Since the directory (/z/layerindex/firefly...) exists, it must be
failing because something is wrong with the version (?)
My kernel recipe's name is "firefly-mainline-kernel_4.0.bb" and it looks
like:
# Copyright (C) 2015 Trevor Woerner
# Released under the MIT license (see COPYING.MIT for the terms)
inherit kernel
DESCRIPTION = "Mainline Rockchip Linux kernel for Firefly"
HOMEPAGE =
"http://wiki.t-firefly.com/index.php/Firefly-RK3288/Mainline_Kernel/en";
LICENSE = "GPLv2"
LIC_FILES_CHKSUM = "file://COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7"
SECTION = "kernel"
DEPENDS = "rk2918-tools-native"
SRC_URI =
"git://github.com/TeeFirefly/linux-rockchip.git;branch=firefly;rev=cbbae6741c60c9e09f87521e3a79810abd6a2fda"
LINUX_VERSION ?= "4.0.0-rc1"
PV = "4.0.0-rc1+git${SRCPV}"
S = "${WORKDIR}/git"
B = "${S}"
COMPATIBLE_MACHINE = "firefly-emmc-mainline"
KERNEL_CONFIG_COMMAND = "cd ${S}; make rk3288_firefly_defconfig"
KERNEL_IMAGETYPE = "zImage"
do_compile_append () {
make rk3288-firefly.dtb
}
do_install_append () {
if [ ! -r arch/arm/boot/zImage ]; then
echo "can't find 'arch/arm/boot/zImage'"
exit 1
fi
if [ ! -r arch/arm/boot/dts/rk3288-firefly.dtb ]; then
echo "can't find 'arch/arm/boot/dts/rk3288-firefly.dtb'"
exit 1
fi
cat ${S}/arch/arm/boot/zImage
${S}/arch/arm/boot/dts/rk3288-firefly.dtb > ${S}/zImage-dtb
rk2918_mkkrnlimg -a ${S}/zImage-dtb ${S}/kernel.img
}
inherit deploy
do_deploy_append () {
install -d ${DEPLOYDIR}
cp ${S}/kernel.img ${DEPLOYDIR}
}
addtask deploy before do_build after do_compile
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] include all kernel modules in image
On 07/27/15 08:04, Nicolas Dechesne wrote: > On Mon, Jul 27, 2015 at 1:03 PM, Trevor Woerner wrote: > > are you doing a minimal > OE-core build? I'm creating a BSP for the Firefly using vendor-ish u-boot and kernel from: http://wiki.t-firefly.com/index.php/Firefly-RK3288/Mainline_Kernel/en > can you try to reproduce / narrow down? It seems related to the version string. Something to do with creating modules.dep. > Are you running > recent master? Yes, master on everything. I can push a work-in-progress branch to github if it helps. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] fido LICENSE error opencv
Hello All, I was able to fix the license error in fido by adding commercial_x264 to LICENSE_FLAGS_WHITELIST variable. LICENSE_FLAGS_WHITELIST = "commercial_libmad commercial_mpeg2dec commercial_libav commercial_ffmpeg commercial_x264" Opencv was installed on the Raspberry core-image-sato with the following changes git diff meta/recipes-sato/images/core-image-sato.bb diff --git a/meta/recipes-sato/images/core-image-sato.bb b/meta/recipes-sato/ima index e3246d2..f4b2286 100644 --- a/meta/recipes-sato/images/core-image-sato.bb +++ b/meta/recipes-sato/images/core-image-sato.bb @@ -8,4 +8,9 @@ LICENSE = "MIT" inherit core-image -IMAGE_INSTALL += "packagegroup-core-x11-sato-games" +IMAGE_INSTALL += "packagegroup-core-x11-sato-games kernel-dev xterm git \ + jasper gsl gsl-dev python-netserver python-pygtk python-pygtk-dev \ + python-numpy liba52 liba52-dev libmad libmad-dev libmad-staticdev \ + chkconfig v4l-utils python-imaging parted python-distribute \ + python-pyrex python-pexpect gperf tree libav libav-dev \ + x264 x264-dev libav libav-dev opencv opencv-samples cmake" What is the preferred method of creating an image with additional software installed? Thanks for all the help. Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Using wic from a Bitbake task
May I know it’s expected completion date? Noor From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On Behalf Of Burton, Ross Sent: Monday, July 27, 2015 3:05 PM To: Usman, Fahad Cc: yocto@yoctoproject.org; Khandavilli, Arun Subject: Re: [yocto] Using wic from a Bitbake task On 26 July 2015 at 18:24, Usman, Fahad mailto:fahad_us...@mentor.com>> wrote: Is it possible to invoke 'wic create' command from a bitbake task. As currently it is implemented to be run as a standalone tool and if we invoke it from a task, the 'bitbake -e' command fails, since more than one instances of bitbake cannot be run from a single build directory. Not yet, but there's a bug for that: https://bugzilla.yoctoproject.org/show_bug.cgi?id=7672 Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Using wic from a Bitbake task
On 27 July 2015 at 13:49, Ahsan, Noor wrote: > May I know it’s expected completion date? > > Currently marked as "1.9", you'll have to talk to Ed to get anything more precise than that. Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Missing certificates
On 2015-07-24 12:02, Gary Thomas wrote: I was trying to run a simple fetch from python using url = 'https://raw.github.com/Itseez/opencv/master/samples/c/fruits.jpg' filedata = urllib2.urlopen(url).read() This failed: Traceback (most recent call last): File "./edge.py", line 36, in filedata = urllib2.urlopen(url).read() File "/usr/lib/python2.7/urllib2.py", line 154, in urlopen return opener.open(url, data, timeout) File "/usr/lib/python2.7/urllib2.py", line 431, in open response = self._open(req, data) File "/usr/lib/python2.7/urllib2.py", line 449, in _open '_open', req) File "/usr/lib/python2.7/urllib2.py", line 409, in _call_chain result = func(*args) File "/usr/lib/python2.7/urllib2.py", line 1240, in https_open context=self._context) File "/usr/lib/python2.7/urllib2.py", line 1197, in do_open raise URLError(err) urllib2.URLError: I can see that it was looking for some certificates in /usr/lib/ssl/certs but that directory is missing. Anyone know what I might be missing (or have misconfigured)? Thanks I've found a discussion about this problem on the OpenEmbedded development list: http://lists.openembedded.org/pipermail/openembedded-devel/2015-July/102160.html So the problem that this has uncovered is twofold: 1) Python (and OpenSSL) are not using the certificates that are installed by the ca-certificates package OpenSSL expects the certificates in /usr/lib/ssl/certs and ca-certificates uses /etc/ssl/certs 2) The certificates from ca-certificates are not immediately usable by OpenSSL since they are not hashed. This is done by the 'c_rehash' program but has been explicitly disabled by a patch. Further exploration implies that this was disabled because not all targets will have c_rehash available and since the hashing is expected to be done on the target when the certificates are loaded/updated. Finally, c_rehash, may or may not exist in the OpenSSL packages, depending on whether or not perl is available on the target (it's a perl script) How best to solve this? As is, python htts:// support is broken in OE-core, so I think an off-the-shelf solution is warranted. Perhaps the PACKAGECONFIG for openssl should default to supporting perl on the target, and hence the c_rehash utility would be available? Certainly the choice of where the certificates live, etc, should be standardized. Maybe the c_rehash can be run at package build time for ca-certificates? This would make things work, at least for the real CA certificates. Ideas? -- Gary Thomas | Consulting for the MLB Associates |Embedded world -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Finger print URU4500 on Linux/Yocto. (Recipes? Drivers? Do it works?)
Hi everybody! I'm gonna use an usb fingerprint by DigitalPersona named U.are.U 4500. They have a driver for old kernels which I'm using but now I'm going to a new platform (iMX.6) with 3.14.28 kernel. I want to know if anybody is using that and if it works!? Googling around I found this library: http://www.freedesktop.org/wiki/Software/fprint/libfprint/, which seems to have support for my device (uru4500), the big question is: Are there recipes for build/installing this with Yocto? (I'm in Dizzy release) Best regards, - dhs -- "Do or do not. There is no try" Yoda Master -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] ADT python build
Hello All,
On Raspberry Pi target and earlier version of myhdl was getting a
ImportError: No module named py_compile (see py_compile error attached)
Trying to install a python module using the ADT enviornment.
name="myhdl",
version=version,
description="Python as a Hardware Description Language",
long_description="See home page.",
author="Jan Decaluwe",
author_email="j...@jandecaluwe.com",
url="http://www.myhdl.org";
The following are the steps that result in an error using the ADT and Raspberry
Pi target.
mkdir build_myhdl
cd build_myhdl/
git clone https://github.com/jandecaluwe/myhdl.git
cd myhdl/
source
/opt/poky/1.8+snapshot/environment-setup-cortexa7hf-vfp-vfpv4-neon-poky-linux-gnueabi
python setup.py install
which python
/opt/poky/1.8+snapshot/sysroots/x86_64-pokysdk-linux/usr/bin/python
python setup.py install
Traceback (most recent call last):
File "setup.py", line 3, in
import ast
ImportError: No module named ast
Thanks in advance. Edward Vidal Jr.
e-mail devel...@sbcglobal.net
915-595-1613python setup.py install
starts out okay.
writing manifest file 'myhdl.egg-info/SOURCES.txt'
installing library code to build/bdist.linux-armv7l/egg
running install_lib
running build_py
creating build/lib
creating build/lib/myhdl
copying myhdl/_Signal.py -> build/lib/myhdl
copying myhdl/_util.py -> build/lib/myhdl
copying myhdl/_Cosimulation.py -> build/lib/myhdl
copying myhdl/_compat.py -> build/lib/myhdl
copying myhdl/_Waiter.py -> build/lib/myhdl
copying myhdl/__init__.py -> build/lib/myhdl
copying myhdl/_tristate.py -> build/lib/myhdl
copying myhdl/_bin.py -> build/lib/myhdl
.
.
.
many more lines
.
.
.
copying build/lib/myhdl/_resolverefs.py -> build/bdist.linux-armv7l/egg/myhdl
copying build/lib/myhdl/_resize.py -> build/bdist.linux-armv7l/egg/myhdl
copying build/lib/myhdl/_ShadowSignal.py -> build/bdist.linux-armv7l/egg/myhdl
copying build/lib/myhdl/_simulator.py -> build/bdist.linux-armv7l/egg/myhdl
Traceback (most recent call last):
File "setup.py", line 60, in
'Programming Language :: Python :: 3.4',
File "/usr/lib/python2.7/distutils/core.py", line 151, in setup
dist.run_commands()
File "/usr/lib/python2.7/distutils/dist.py", line 953, in run_commands
self.run_command(cmd)
File "/usr/lib/python2.7/distutils/dist.py", line 972, in run_command
cmd_obj.run()
File
"/usr/lib/python2.7/site-packages/distribute-0.6.32-py2.7.egg/setuptools/command/install.py",
line 73, in run
self.do_egg_install()
File
"/usr/lib/python2.7/site-packages/distribute-0.6.32-py2.7.egg/setuptools/command/install.py",
line 93, in do_egg_install
self.run_command('bdist_egg')
File "/usr/lib/python2.7/distutils/cmd.py", line 326, in run_command
self.distribution.run_command(command)
File "/usr/lib/python2.7/distutils/dist.py", line 972, in run_command
cmd_obj.run()
File
"/usr/lib/python2.7/site-packages/distribute-0.6.32-py2.7.egg/setuptools/command/bdist_egg.py",
line 179, in run
cmd = self.call_command('install_lib', warn_dir=0)
File
"/usr/lib/python2.7/site-packages/distribute-0.6.32-py2.7.egg/setuptools/command/bdist_egg.py",
line 166, in call_command
self.run_command(cmdname)
File "/usr/lib/python2.7/distutils/cmd.py", line 326, in run_command
self.distribution.run_command(command)
File "/usr/lib/python2.7/distutils/dist.py", line 972, in run_command
cmd_obj.run()
File
"/usr/lib/python2.7/site-packages/distribute-0.6.32-py2.7.egg/setuptools/command/install_lib.py",
line 24, in run
self.byte_compile(outfiles)
File "/usr/lib/python2.7/distutils/command/install_lib.py", line 138, in
byte_compile
dry_run=self.dry_run)
File "/usr/lib/python2.7/distutils/util.py", line 437, in byte_compile
from py_compile import compile
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [OE-core] qt5 webkit Nothing RPROVIDES 'liborc-0.4'
On Thu, Jul 23, 2015 at 02:01:40PM +0300, Life Life wrote: > Hello, > > I'm trying to build qt5 webkit. I seen this error message > > Build Configuration: > BB_VERSION= "1.24.0" > BUILD_SYS = "x86_64-linux" > NATIVELSBSTRING = "Ubuntu-14.04" > TARGET_SYS= "arm-poky-linux-gnueabi" > MACHINE = "phyboard-wega-am335x-2" > DISTRO= "poky" > DISTRO_VERSION= "1.7" > TUNE_FEATURES = "arm armv7a vfp thumb neon callconvention-hard cortexa8" > TARGET_FPU= "vfp-neon" > meta > meta-yocto= "(nobranch):9aff3a4ec058a1a1149d026ebedcc6251089fffb" > meta-phytec = "(nobranch):ccf1c78f312f84933b90926e9bf4f72de59e8e94" > meta-phyam335x= "(nobranch):a6c488b268d0c2e506f293221703dafcc05b9610" > meta-oe > meta-networking > meta-python > meta-multimedia = "(nobranch):9efaed99125b1c4324663d9a1b2d3319c74e7278" > meta-qt5 = "master:6d9e2a6dfc21f7d9a3a11b4bcb426b5dfe6feaeb" > meta-ruby = "(nobranch):9efaed99125b1c4324663d9a1b2d3319c74e7278" > > NOTE: Preparing runqueue > NOTE: Executing SetScene Tasks > NOTE: Executing RunQueue Tasks > NOTE: Tasks Summary: Attempted 3367 tasks of which 3367 didn't need to be > rerun and all succeeded. > NOTE: Resolving any missing task queue dependencies > ERROR: Nothing RPROVIDES 'liborc-0.4' (but > /home/xy/yocto/build/recipes/images/ > core-image-base-edited-20150723-135844.bb RDEPENDS on or otherwise requires > it) My guess is that qtwebkit is autodetecting orc (as provided in meta/recipes-devtools/orc/orc_0.4.23.bb) so if you build qtwebkit in sysroot with orc already staged and then reuse the same qtwebkit build in build directory without orc you'll get this kind of error message. Proper fix is to explicitly disable orc support in qtwebkit (or even better add PACKAGECONFIG[orc] which will explicitly enable/disable it). Regards, -- 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] fido LICENSE error opencv
On Mon, Jul 27, 2015 at 7:34 AM, Edward Vidal wrote: > Hello All, > I was able to fix the license error in fido by adding commercial_x264 to > LICENSE_FLAGS_WHITELIST variable. > > LICENSE_FLAGS_WHITELIST = "commercial_libmad commercial_mpeg2dec > commercial_libav commercial_ffmpeg commercial_x264" > > Opencv was installed on the Raspberry core-image-sato with the following > changes > > git diff meta/recipes-sato/images/core-image-sato.bb > diff --git a/meta/recipes-sato/images/core-image-sato.bb > b/meta/recipes-sato/ima > index e3246d2..f4b2286 100644 > --- a/meta/recipes-sato/images/core-image-sato.bb > +++ b/meta/recipes-sato/images/core-image-sato.bb > @@ -8,4 +8,9 @@ LICENSE = "MIT" > > inherit core-image > > -IMAGE_INSTALL += "packagegroup-core-x11-sato-games" > +IMAGE_INSTALL += "packagegroup-core-x11-sato-games kernel-dev xterm git \ > + jasper gsl gsl-dev python-netserver python-pygtk python-pygtk-dev \ > + python-numpy liba52 liba52-dev libmad libmad-dev libmad-staticdev \ > + chkconfig v4l-utils python-imaging parted python-distribute \ > + python-pyrex python-pexpect gperf tree libav libav-dev \ > + x264 x264-dev libav libav-dev opencv opencv-samples cmake" > > What is the preferred method of creating an image with additional software > installed? > > Thanks for all the help. > > Edward Vidal Jr. > e-mail devel...@sbcglobal.net > 915-595-1613 > > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > Hi I had the same problem with opencv in yocto . There is a trend about this in mailign list: https://www.mail-archive.com/yocto@yoctoproject.org/msg24746.html I am pushing to do a change in opencv receipt Hope it helps -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] include all kernel modules in image
Hey Nicolas, Thanks for taking a poke at this and for verifying it should otherwise work ;-) It turns out it was a version issue (as I suspected), the "-rc1" should have been in a variable named "LINUX_VERSION_EXTENSION" leaving the rest in "LINUX_VERSION" as before: SRC_URI = "git://github.com/TeeFirefly/linux-rockchip.git;branch=firefly;rev=cbbae6741c60c9e09f87521e3a79810abd6a2fda" LINUX_VERSION ?= "4.0.0" LINUX_VERSION_EXTENSION = "-rc1" Best regards, Trevor -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] include all kernel modules in image
On 07/27/15 08:17, Trevor Woerner wrote: > inherit kernel ... > DEPENDS = "rk2918-tools-native" ...and the "DEPENDS = " needs to be a "DEPENDS +=" since the "inherit kernel" above already sets a bunch of DEPENDS and if the "+" isn't used, the recipe loses the DEPENDS on the cross toolchain (for example)! -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Problem add and removing files to filesystem
On Fri, Jul 24, 2015 at 5:24 PM, Khem Raj wrote:
> On 15-07-24 14:27:09, Lorin Vandegrift wrote:
> > Hi all,
> >
> > We are having problems adding extra files/removing files from the
> generated
> > file system in Yocto. We've had success with using a do_install command
> in
> > our own bb file and using commands in the format rsync -avz test.txt
> > ${D}{sysconfdir}, however we can't write to some paths (i.e. writing to
> > root with ${D). Additionally, we are not able to overwrite files
> generated
> > by other recipes. We also tried using install and couldn't push our init
> > script (nstall -m 0755 test.sh ${D}${sysconfdir}/init.d). Any advice for
> > these? Also is there a recommended way for removing files? We were
> able
> > to remove them by using the rm command and adding it to
> > ROOTFS_POSTPROCESS_COMMAND.
>
> You can consider few approaches
>
> 1. Move the files into packages of there own in the recipe which means
>
> PACKAGES += "foo"
> FILES_foo = "files you want to separate out"
>
> 2. Write a bbappend in your own layer if you are doing something thats
> not generic and wont benefit community, in this bbappend you can write
> do_install_append () function and do the removal and any other packaging
> related adjustments needed for that recipe
>
> 3. Write your own rootfs post processing function and hook it up into
> ROOTFS_POSTPROCESS_COMMAND variable, this will however mean that online
> package upgrades wont work out of box.
>
> If you are looking for overwriting files then consider them patching
> using patches or overlaying files using SRC_URI itself again using a
> bbappend, if its a config file and you have few tweaks you can sed/awk
> then in do_install step itself.
>
> what you are trying is violating the packaging concerns of buildsystem
> and thats why its not working as you expected.
>
> Consider components and files a component provides as basic unit of
> operation, all changes has to be done at that level for best results.
>
> -Khem
>
Hi there,
Thanks for the response. Unfortunately we tried your suggestions with no
luck. Below is the bb file for our package, do you see anything that we
might of missed? The tar ball listed below is in a subdirectory called
"files" in the same folder as the bb file.
Thanks
SUMMARY = "Extra filesystem files"
SECTION = "rootfs"
LICENSE = "CLOSED"
SRC_URI = "file://extrafiles.tar.gz"
S = "${WORKDIR}/files"
ROOTFS_POSTPROCESS_COMMAND += "set_root_passwd;"
ROOTFS_POSTPROCESS_COMMAND += "modify_filesystem;"
do_install() {
install -m 0755 testFile.sh ${D}/home/root
rsync -avz wpa_supplicant ${D}${sysconfdir}
rsync -avz root ${D}${sysconfdir}
rsync -avz network ${D}${sysconfdir}
rsync -avz test.txt ${D}${sysconfdir}
rsync -avz syslog.conf ${D}${sysconfdir}
rsync -avz rules.d ${D}${sysconfdir}/udev/
rsync -avz sys_init.service ${D}${sysconfdir}/system/
}
modify_filesystem() {
rm ${IMAGE_ROOTFS}${sysconfdir}/wpa_supplicant.conf;
}
set_root_passwd() {
sed 's%^root:[^:]*:%root:$1$xyz$KSp5j8kx3cPgA3/ODPZ6E.:%' \
< ${IMAGE_ROOTFS}/etc/shadow \
> ${IMAGE_ROOTFS}/etc/shadow.new;
mv ${IMAGE_ROOTFS}/etc/shadow.new ${IMAGE_ROOTFS}/etc/shadow ;
}
EXTRA_IMAGE_FEATURES += "read-only-rootfs"
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] fido LICENSE error opencv
Hello All,I got openCV to detect 2 C920 cameras using a python api.I started a repository https://github.com/develone/raspberrypi2_yocto I am currently using fido branch.The things that I have been able to createbitbake rpi-basic-image bitbake core-image-sato with addition additional libs and applications see the file wkg_conf_files/core-image-sato.bbbitbake meta-toolchainIf you have any questions feel free to contract me. Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613 On Monday, July 27, 2015 9:53 AM, Victor Rodriguez wrote: On Mon, Jul 27, 2015 at 7:34 AM, Edward Vidal wrote: > Hello All, > I was able to fix the license error in fido by adding commercial_x264 to > LICENSE_FLAGS_WHITELIST variable. > > LICENSE_FLAGS_WHITELIST = "commercial_libmad commercial_mpeg2dec > commercial_libav commercial_ffmpeg commercial_x264" > > Opencv was installed on the Raspberry core-image-sato with the following > changes > > git diff meta/recipes-sato/images/core-image-sato.bb > diff --git a/meta/recipes-sato/images/core-image-sato.bb > b/meta/recipes-sato/ima > index e3246d2..f4b2286 100644 > --- a/meta/recipes-sato/images/core-image-sato.bb > +++ b/meta/recipes-sato/images/core-image-sato.bb > @@ -8,4 +8,9 @@ LICENSE = "MIT" > > inherit core-image > > -IMAGE_INSTALL += "packagegroup-core-x11-sato-games" > +IMAGE_INSTALL += "packagegroup-core-x11-sato-games kernel-dev xterm git \ > + jasper gsl gsl-dev python-netserver python-pygtk python-pygtk-dev \ > + python-numpy liba52 liba52-dev libmad libmad-dev libmad-staticdev \ > + chkconfig v4l-utils python-imaging parted python-distribute \ > + python-pyrex python-pexpect gperf tree libav libav-dev \ > + x264 x264-dev libav libav-dev opencv opencv-samples cmake" > > What is the preferred method of creating an image with additional software > installed? > > Thanks for all the help. > > Edward Vidal Jr. > e-mail devel...@sbcglobal.net > 915-595-1613 > > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > Hi I had the same problem with opencv in yocto . There is a trend about this in mailign list: https://www.mail-archive.com/yocto@yoctoproject.org/msg24746.html I am pushing to do a change in opencv receipt Hope it helps -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
