Hi,
I had to made some device tree changes inside of a devshell.
Just changed the .dts file and exited the shell.
I built the image after that and got the message:
...do_compile is tainted from a forced run
...do_deploy is tainted from a forced run
which made sense given the manual changes I've
Hello yocto community,
I want to know a few things
about how to configure yocto such that
- a simple application (let's say a hello world C program
from a new recipe) is run at boot time.
- run a kernel module from a simple recipe at boot time
and automatically build its "/dev/hello" interface f
Hi,
On Tue, Dec 5, 2017 at 3:21 PM, Laurentiu-Cristian Duca
wrote:
> Hello yocto community,
>
> I want to know a few things
> about how to configure yocto such that
> - a simple application (let's say a hello world C program
> from a new recipe) is run at boot time.
depends which init system yo
Attendees: Stephen, Saul, Stephano, Aaron, Richard, Armin, Rob, Brian, Chin
Huat, Patrick, Randy, Mark, Ross, Christian, Joshua W., wmills, Michael,
Agenda:
* Yocto Project status - 5 min (Stephen/team)
* YP 2.5 M1 is getting ready to build, but the build/test environment is
not stable. T
Hi,
I have edited my local.conf to remove the debug related EXTRA_IMAGE_FEATURES.
My rootfs still contains a /usr/src/debug folder, which I would like to get rid
of. This likely come from -dbg package inclusion, which I would like to
understand how to control/remove. We are using Yocto 1.9/2
On 12/5/17 12:40 PM, Koehler, Yannick wrote:
> Hi,
>
> I have edited my local.conf to remove the debug related EXTRA_IMAGE_FEATURES.
> My rootfs still contains a /usr/src/debug folder, which I would like to get
> rid of. This likely come from -dbg package inclusion, which I would like to
> un
In our situation, we have many packages that are in-house, as such we use a
local folder for the several in-house modules. To do so, we need to use
externalsrc to point to the local code so that the git repo contains both the
code + recipe, instead of 20 repos (1 per packages) and 1 more for yo
Hello
We are using in our layer a kernel 4.8 recipe (linux-stable_4.8.bb)-
everything ok.
I'm trying to upgrade to 4.14, I created a new recipe
linux-stable_4.14.bb. They live side by side, for now.
But with the 4.14 kernel when running `bitbake -c menuconfig
linux-stable`, the new terminal co
Hello Mircea,
>From my point of view:
*> /usr/bin/ld: cannot find -lncursesw*
> collect2: error: ld returned 1 exit status
> scripts/Makefile.host:111: recipe for target 'scripts/kconfig/mconf'
failed
The first line explains it all. You could not configure 4.14, since for
this you should have nc
From: Mingli Yu
Remove the absolute path for start-stop-daemon
to fix samhain start-up as start-stop-daemon
sometimes located in /usr/sbin, not the expected
/sbin.
Signed-off-by: Mingli Yu
---
recipes-security/samhain/files/samhain-client.init | 12 ++--
recipes-security/samhain/fi
10 matches
Mail list logo