Hi Just to see if I understood correctly. Are saying here that you can't pass a custom environmental variable to a child process of the parent process is the python interpreter? The oe-init-build-env

If I can please ask one last on this issue: We decided to try "smart", but it seems that its mirrors list are all empty. Can you please point me as to how to fill the mirror list (I tried to search

Hello to all YOCTO users, I have one (I should say naive) question considering/querying environment variables, initially set with bitbake scripts. I have both python (2.7.14) and python3.6 (3.6.2).

From: youngseok <earwigz32@...> License file changes are due to updates in Version and Copyright date (From OE-Core rev: 44676c90863c3864182c088ca51bec3bdc8dce29) Change-Id:

Adding Michael Halstead.

I'm using git submodule to set up a Yocto build using the various layers required for my project. I see that recent git has the ability to specify that a submodule repository should be a "shallow"

I debugged further on this problem. "dpkg --print-architecture" is just returns "ARCHITECTURE" which is defined by configure script. In configure script, ARCHITECTURE is defined as

Any more comments? I started to use stable/{branch}-next in all the contrib repos. Poky will be constructed from oe-contrib repos. thanks for all the feedback.

merged. not sure if I sent our a confirmation email. Thanks, armin

I reported this to Michael a week or so ago but I think he's still battling an upgrade of the layer index code among other things. Michael, any updates? Thanks, Paul -- Paul Eggleton Intel Open

"Burton, Ross" <ross.burton@...> wrote: Try running make pdf DOC=ref-manual (then drink so coffee and wait) After it, the pdf manual is there. There are other manuals as well, this is just

Sure. The layer that will fetch all the other layers by running make: https://github.com/getsenic/senic-os The kernel source being

Andreas Müller <schnitzeltony@...> wrote: Do you mind filing a bug so it can be tracked better? [1] https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Layer%20Index

do configure is the existing/traditional/common/simple kernel.bbclass way to copy a defconfig and make sure it gets into the build. do_kernel_configme has more processing and logic to deal

Morty Yup, same error. Yup, it's in there. Yup, am using that as a workaround . What is the difference between do_kernel_configme and do_configure? Not quite clear on why both exist. I ask because

I now see that I have smart: root@lec-imx6:~# smart Usage: smart command [options] [arguments] I was not familiar with "smart" command before, so that is good enough. The image is based on

What release? Until recently we used smart not yum. Ross

I've added in local.conf both: PACKAGE_CLASSES = "package_rpm" IMAGE_FEATURES += "package-management" Yet, I don't have yum command, only rpm command. Regards, Ran

That's just part of the localversion processing in the bbclass, so no worries there. Nope. Well, you do need some sort of configuration available, but it doesn't have to be in that format. That

Something I inherited. It does seem to have been based on linux-yocto-custom.bb. SECTION = "kernel" DESCRIPTION = "Mainline Linux kernel" LICENSE = "GPLv2" LIC_FILES_CHKSUM =