Set KBUILD_BUILD_VERSION=1 to avoid build version being incremented on
every build. It is visible in the output of "cat /proc/version" after
the hash character.
Signed-off-by: Jonathan Liu
---
meta/classes/kernel.bbclass | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/classes/kernel.bbc
With multi kernel support in the installer we can exceed this limit.
Calculate a sane size by checking the size of the original boot
partition minus some objects we know won't be installed, plus some extra
space for users.
In addition, in the common case where only one small kernel is present
to b
I forgot to deal with RDEPENDS here. With the addition of du the script
will depend on ${VIRTUAL-RUNTIME_base-utils}. This happens to be present
in core-image-minimal-initramfs, so it worked for me, but could fail for
others using their own initramfs.
I'll send a v2 adding to RDEPENDS on the r
With multi kernel support in the installer we can exceed this limit.
Calculate a sane size by checking the size of the original boot
partition minus some objects we know won't be installed, plus some extra
space for users.
In addition, in the common case where only one small kernel is present
to b
Since the wtmp and btmp definitions had been moved from logrotate.conf
to logrotate.d in this release, we also need to install them to
/etc/logrotate.d/.
Also update oeqa runtime logrotate test case.
Signed-off-by: Yi Zhao
---
meta/lib/oeqa/runtime/cases/logrotate.py | 4
And on a happier note this time, pseudo master appears much happier and
19f18124f16c4c85405b140a1fb8cb3b31d865bf seems to pass on the
autobuilders. I'll do some specific checks on f27 but things are
looking good, thanks everyone who's helped with this.
Cheers,
Richard
--
__
On 3/15/18 2:04 PM, Amanda Brindle wrote:
> The following changes since commit 0fd6d0dd0041929d60111868ca3575d9d9bf9ac3:
>
> linux-yocto/4.12: backport bugfixes for x86 (2018-03-15 06:27:20 -0700)
>
> are available in the git repository at:
>
> git://git.yoctoproject.org/poky-contrib abrindl
On Sun 2018-04-01 @ 11:49:58 PM, Andreas Müller wrote:
> When running bitbake -cmenuconfig virtual/kernel I get a flood of
> undefined reference errors. Am I alone here?
Sadly, I think you might be.
$ bitbake virtual/kernel -c menuconfig
works fine for me.
I assume you're doing this for
== Series Details ==
Series: python3: Improve logging capabilities for do_create_manifest
Revision: 1
URL : https://patchwork.openembedded.org/series/11647/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several te
Adds a couple of prints to get a nicer log, and creates a
small summary or report after checking every module, it
makes it more feasible for adoption, easier to debug why
a module ended at a certain package and see how the
manifest was created.
Signed-off-by: Alejandro Enedino Hernandez Samaniego
Adresses [1]
https://bugzilla.yoctoproject.org/show_bug.cgi?id=12642
Signed-off-by: Andreas Müller
---
meta/recipes-graphics/mesa/mesa.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-graphics/mesa/mesa.inc
b/meta/recipes-graphics/mesa/mesa.inc
index 9e4da81
This came up whith disabled DRI3 on Raspi/VC4 [1] but might be important for
other
drivers: It fixes an improper initialization.
[1] https://lists.freedesktop.org/archives/mesa-dev/2018-March/190562.html
Signed-off-by: Andreas Müller
---
...i-Initialise-modifier-to-INVALID-for-DRI2.patch | 43
== Series Details ==
Series: "mesa: fix unitialized modifier..." and 1 more
Revision: 1
URL : https://patchwork.openembedded.org/series/11645/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been
Adresses [1]
https://bugzilla.yoctoproject.org/show_bug.cgi?id=12642
Signed-off-by: Andreas Müller
---
meta/recipes-graphics/mesa/mesa.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-graphics/mesa/mesa.inc
b/meta/recipes-graphics/mesa/mesa.inc
index 9e4da81
This came up whith disabled DRI3 on Raspi/VC4 [1] but might be important for
other
drivers: It fixes an improper initialization.
[1] https://lists.freedesktop.org/archives/mesa-dev/2018-March/190562.html
Signed-off-by: Andreas Müller
---
...i-Initialise-modifier-to-INVALID-for-DRI2.patch | 43
On Mon, 26 Mar 2018, Burton, Ross wrote:
On the autobuilder:
| NOTE: FAIL [15.139s]: test_stap (stap.StapTest)
| NOTE: --
| NOTE: Traceback (most recent call last):
| File
"/home/pokybuild/yocto-autobuilder/yocto-worker/ni
Current Dev Position: YP 2.5 M3 final close out.
Next Deadline: YP 2.5 M4 stabilization is 4/2/18
SWAT Team Rotation:
SWAT lead is currently Juro.
SWAT team rotation: Juro -> Paul on April 6, 2018
SWAT team rotation: Paul -> Tracy on April 13, 2018
https://wiki.yoctoproject.org/wiki/Yocto_Bui
It can be installed to some non standard path in which
case build will be broken.
As python2.7 is specified in HOSTTOOLS we can rely
that it is present in the PATH, so no need to hardcode
it to /usr/bin.
Signed-off-by: Ruslan Ruslichenko
---
meta/recipes-devtools/qemu/qemu.inc | 2 +-
1 file cha
Define cpu type for Qemu in QEMU_EXTRAOPTIONS.
Otherways Qemu will emulate some virtual qemu32/64 processor,
which has very basic set of features, and programs built
for later CPU may crash, due to lack of new features (e.g. SSSE3).
Signed-off-by: Ruslan Ruslichenko
---
meta/conf/machine/include
19 matches
Mail list logo
