Hi,
I'm new to openembedded and yocto. I'm using the openpli meta layers to
build openembedded https://github.com/OpenPLi/openpli-oe-core
Now I'm trying to build a recipe for the kernel but I encountered a
strange issue, bitbake is corrupting my source files when unpacking from
zip file
hi folks:
i am working on project with "DISTRO_FEATURE" set to "wayalnd", during the
compile procedure, i saw the xserver pakage was compiled, which would complain
compile error and stop the process.
i try to debug the dependciy, it seems the "weston" package bring the
xorg-server
On 07/20/2018 07:09 PM, Trevor Woerner wrote:
> Has a date/location been set?
I believe it has. An announcement is being formulated and will be sent
to the mailing lists and posted on the Yocto web site. Give it a little
time as new people are getting use to the process.
kind regards,
Armin
>
Has a date/location been set?
(Is it too presumptuous of me to assume there will be a Yocto Dev Day in
Scotland this year?)
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
If DISTRO_FEATURES contains usrmerge then busybox binaries are
installed under /usr/bin not /bin so use ${base_bindir} to support
both paths and avoid QA errors.
Signed-off-by: Ioan-Adrian Ratiu
---
recipes-core/busybox/busybox_selinux.inc | 7 ---
1 file changed, 4 insertions(+), 3
Add 1.06 from oe-core as bc 1.07 is GPLv3.
Signed-off-by: Ross Burton
---
recipes-extended/bc/bc_1.06.bb| 26 +
recipes-extended/bc/files/fix-segment-fault.patch | 28 +++
2 files changed, 54 insertions(+)
create mode 100644
If DISTRO_FEATURES contains usrmerge then busybox binaries are
installed under /usr/bin not /bin so use ${base_bindir} to support
both paths and avoid QA errors.
Signed-off-by: Ioan-Adrian Ratiu
---
recipes-core/busybox/busybox_selinux.inc | 6 +++---
1 file changed, 3 insertions(+), 3
From: Sebastian Andrzej Siewior
commit 97731753d44d5efcb95b994dc952c0e8195b3e96 upstream
This patch reverts commit c7f26ccfb2c3 ("mm/vmstat.c: fix
vmstat_update() preemption BUG").
Steven saw a "using smp_processor_id() in preemptible" message and
added a preempt_disable() section around it to
OK, so it's only visited links, not linked from ML or wiki or whatever,
right?
How huge the database is? I've checked our internal instance and on
relatively slow VM we have:
47 472 724 Post_buildstatstask
2 715 091 Post_build
559 655 Post_buildfailure
we use postgresql, the db currently has
