Re: [yocto] Adding debug output in recipe

Hi Anuj, "bitbake -e" is very useful for debugging out-of-tree build issue. However, looks like I have another issue. From "devtool build" output, I could see variables passed into makefile. Let's focus on "CC" for now: CC=x86_64-poky-linux-gcc -fuse-ld=bfd If we compare this to

Re: [yocto] Adding debug output in recipe

You're right on. KERNEL_CC was used. The 3rd party code actually has 3 components - 1. a kernel module 2. a shared library 3. 2 demo binaries Their top-level makefile builds everything. From Yocto's perspective, it interfaces with this code as though the whole thing is a kernel

[yocto] Adding support for GPIO chipset, Am I doing it right ?

Hi, I'm using poky Rocko. I'm building a linux-rt based system (I'm using bitbake image-core-rt). The GPIO chip (Fintek F81866d) is not supported by the kernel we selected (4.4). I downloaded the patch which adds support of Fintek F81866d to kernel (from

[yocto] meta-virtualization -> docker not packaged when using PACKAGE_CLASSES ?= "package_deb"

Hello, I encountered a funny behavior the other day. While trying to integrate Docker into my image using the openembedded meta-virtualization layer, I happened to not being able to get my image finalized. Usually I build with PACKAGE_CLASSES ?= "package_deb". I also added

[yocto] adding avocado to custom image

Hello everyone, I'm trying to install a python package and its additional plugins to my custom image. These plugins are stored in a directory within the package's folder named optional_plugins. Plugins can easily be installed using the command python setup.py install from within the plugin

[yocto] bitbake failed during build of openjdk-8 using meta-linaro aarm64

Hi, I'm building the openjdk-8 from (openjdk-8_0.1.bb) linaro aarm64. But actually the build failed. I saw similar problem last year but there was no solution to that . Is this build working at all ? WARNING: mpfr-native-3.1.5-r0 do_fetch: Failed to fetch URL

[yocto] [meta-gplv2][PATCH] layer.conf: add LAYERSERIES_COMPAT

Signed-off-by: Martin Jansa --- conf/layer.conf | 2 ++ 1 file changed, 2 insertions(+) diff --git a/conf/layer.conf b/conf/layer.conf index f5601bb..3d614dc 100644 --- a/conf/layer.conf +++ b/conf/layer.conf @@ -13,3 +13,5 @@ BBFILE_PRIORITY_gplv2 = "1"

Re: [yocto] Problem with packages during "devtool build"

Hi Robert, I'd already read the out-of-tree example; it's the first thing I checked. After some changes in 3rd party Makefile, I'm running into errors in do_compile step. My new question now is, how the Makefile picks up cross-compile INC path, as well as the LINKER path. The variable

[yocto] glib-initial do_install fails at 'oe_runmake csu/subdir_lib' (Rocko)

Hello, I cannot buid core-image-minimal for a imx25pdk machine (rocko). Building stops at glibc-initial install. Building for another machine with morty (imx25pdk is not available in morty)  works. I assume is related to this part of the recipe (glibc-initial.inc): do_install () {    

[yocto] FW: [meta-qt5]Feature 'tslib' was disabled, but the pre-condition 'libs.tslib' failed.

I'm so sorry the error message is "Feature 'tslib' was enabled, but the pre-condition 'libs.tslib' failed.", not disabled. So sorry for confusing. :( Koo. From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On Behalf Of dhkoo Sent: Friday, April 06, 2018 4:52

[yocto] [meta-qt5]Feature 'tslib' was disabled, but the pre-condition 'libs.tslib' failed.

Hello. I want to compile the tslib enabled Qt5.10 on the yocto. After running "bitbake core-image-mymachine", on the log 'run.do_configure' shows me "-no-tslib" option configured. So I modified qtbase_git.bb to enable "-tslib" option. And after that, bitbake shows me "Feature 'tslib' was

[yocto] pyro: missing ldconfig

Hi, I recently updated from pyro 2.3.3 to latest pyro branch for my raspberry3 and ran into the following problem trying to create the toolchain via: `bitbake meta-toolchain -c populate_sdk` ``` ERROR: meta-toolchain-1.0-r7 do_populate_sdk: Unable to remove packages. Command

Re: [yocto] Adding debug output in recipe

On 04/06/2018 02:05 PM, Raymond Yeung wrote: > Hi Anuj, > > > "bitbake -e" is very useful for debugging out-of-tree build issue. >  However, looks like I have another issue.  From "devtool build" output, > I could see variables passed into makefile.  Let's focus on "CC" for now: > > >

[yocto] Problem with packages during "devtool build"

I've some 3rd party Makefile-based software I'd like to integrate to a working Poky snapshot. The following are done: 1. devtool add cgosapi 2. Edit workspace/recipe/cgosapi/cgosapi.bb. * Implement do_install to move files on build machine to directories on target. *