Separated build dir doesn't work because Makefile points out source dir.
Signed-off-by: Changhyeok Bae
---
meta/recipes-connectivity/iw/{iw_5.0.1.bb => iw_5.3.bb} | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
rename meta/recipes-connectivity/iw/{iw_5.0.1.bb => iw_5.3.bb} (83%)
This completes cleanup originally proposed in 2012:
http://lists.openembedded.org/pipermail/openembedded-core/2012-July/064224.html
Current versions of bitbake have "sane" default fetcher commands
so it's no longer necessary for bitbake.conf to over-ride them.
Signed-off-by: Andre McCurdy
Signed-off-by: Andre McCurdy
---
meta/conf/machine/include/tune-arm1136jf-s.inc | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/meta/conf/machine/include/tune-arm1136jf-s.inc
b/meta/conf/machine/include/tune-arm1136jf-s.inc
index d883eba..b25995d 100644
---
Signed-off-by: Andre McCurdy
---
meta/conf/machine/include/tune-ep9312.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/conf/machine/include/tune-ep9312.inc
b/meta/conf/machine/include/tune-ep9312.inc
index 4d92821..be20eb3 100644
---
Signed-off-by: Andre McCurdy
---
meta/conf/machine/include/tune-arm1176jz-s.inc | 17 +
1 file changed, 17 insertions(+)
create mode 100644 meta/conf/machine/include/tune-arm1176jz-s.inc
diff --git a/meta/conf/machine/include/tune-arm1176jz-s.inc
It's not clear that we actually need to call mount -o remount,XX from
the busybox-inittab inittab at all, but as we currently do, let's
respect read-only-rootfs in IMAGE_FEATURES and not remount / as rw.
Signed-off-by: Andre McCurdy
---
meta/classes/rootfs-postcommands.bbclass | 5 +
1 file
Since TUNE_FEATURES now either contains a CPU or an architecture (but
not both) we can't rely on finding the architecture in TUNE_FEATURES.
Use architecture specific over-rides instead.
Signed-off-by: Andre McCurdy
---
meta/conf/machine/include/arm/feature-arm-thumb.inc | 7 +--
1 file
Default values for MACHINE_ESSENTIAL_EXTRA_RDEPENDS and
MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS are set from bitbake.conf and so
don't need to be duplicated in the packagegroup-core-boot recipe.
Signed-off-by: Andre McCurdy
---
meta/recipes-core/packagegroups/packagegroup-core-boot.bb | 6 --
1
Packaging rules were left behind when libnsl was removed:
https://git.openembedded.org/openembedded-core/commit/?id=9dc9983901cec364ea57a72b9da1a0396b60663a
Signed-off-by: Andre McCurdy
---
meta/recipes-core/glibc/glibc-package.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
On 8/8/19 4:16 PM, Randy MacLeod wrote:
On 8/8/19 10:26 AM, Trevor Gamblin wrote:
From: Trevor Gamblin
Signed-off-by: Trevor Gamblin
---
...ke-ed-directly-instead-of-using-the-shell.patch | 44
++
meta/recipes-devtools/patch/patch_2.7.6.bb | 2 +
2 files
The previous simplification:
https://git.openembedded.org/openembedded-core/commit/?id=604777acfc54d285f315b622bd147ed02d55d6fd
looked OK but didn't actually work as expected. The native and
nativesdk classes re-set CFLAGS after the += has been applied and
so any modifications made via += are
Unless SQLITE_BYTEORDER is predefined, the code falls back to build
time huristics - which are not always correct (e.g. in sqlite 3.28.0
big-endian ARM is mis-detected).
Signed-off-by: Andre McCurdy
---
meta/recipes-support/sqlite/sqlite3.inc | 6 +-
1 file changed, 5 insertions(+), 1
Signed-off-by: Andre McCurdy
---
meta/recipes-core/base-files/base-files_3.0.14.bb | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/meta/recipes-core/base-files/base-files_3.0.14.bb
b/meta/recipes-core/base-files/base-files_3.0.14.bb
index 4b4027f..2b1f217 100644
---
Signed-off-by: Andre McCurdy
---
meta/recipes-core/dropbear/dropbear.inc | 11 +--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-core/dropbear/dropbear.inc
b/meta/recipes-core/dropbear/dropbear.inc
index dcbda74..7269888 100644
---
Signed-off-by: Andre McCurdy
---
meta/classes/update-rc.d.bbclass | 17 ++---
1 file changed, 14 insertions(+), 3 deletions(-)
diff --git a/meta/classes/update-rc.d.bbclass b/meta/classes/update-rc.d.bbclass
index 1366fee..bf86bfa 100644
--- a/meta/classes/update-rc.d.bbclass
+++
build system is changed to meson.
Signed-off-by: Changhyeok Bae
---
.../iputils/iputils/ai_canonidn.patch | 58 --
.../iputils/iputils/install.patch | 26
.../iputils/iputils_s20180629.bb | 61 ---
-subversion/subversion-1.12.0-apr_1.7.0_fix-1.patch
Removed since this is included in 1.12.2.
Signed-off-by: Zang Ruochen
---
.../subversion-1.12.0-apr_1.7.0_fix-1.patch| 107 -
.../{subversion_1.12.0.bb => subversion_1.12.2.bb} | 5 +-
2 files changed, 2
Let me explain a bit what these changes do for us in LGE.
We have jenkins jobs for CI as well for official releases.
All built artifacts are moved from jenkins builder to fileserver after
the build.
Each jobs have some identifier which is then included in the filenames
of all relevant build
* just RFC, the part for images isn't finished yet and there is
still some issue with DATETIME when kernel artifacts are used
from sstate, this is just to validate the idea behind
[YOCTO #12937] before finishing the implementation (it's already
finished and used by various LGE builds, but
* do_install doesn't use whole "version" as do_deploy does, e.g.
${PKGE}-${PKGV}-${PKGR}-${MACHINE}
it installs only the files with only ${KERNEL_VERSION} in filename or
path, so it doesn't need expanded AUTOINC value in PKGV nor
EXPANDPRAUTO in PKGR like do_deploy does
* it was
* otherwise PKGR seen in do_install, do_deploy and do_deploy_links will
have different value in each of them (PRSERV will return different
value of EXTENDPRAUTO because TASKHASH is different for each of these
tasks and also cause unnecessary multiple EXTENDPRAUTO increments for
each
* similar to kernel-artifact-names for other recipes/bbclasses which
need to use some deployed artifacts
* bitbake.conf: move IMAGE_BASENAME, IMAGE_VERSION_SUFFIX, IMAGE_NAME,
IMAGE_LINK_NAME variables
* image_types.bbclass: move IMAGE_NAME_SUFFIX variable
* currently IMAGE_NAME_SUFFIX is
* just to make sure it looks like bash variable not bitbake variable in
run.do_* scripts
[YOCTO #12937]
Signed-off-by: Martin Jansa
---
meta/classes/kernel.bbclass | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/meta/classes/kernel.bbclass
* drop ${PKGE}-${PKGV}-${PR} from kernel artifacts names (this is the
latest build) and add it only in hardlinks created in do_deploy_links
so that we can use PKGR there again (because these links are generally
used only by human operators and they don't have their own TASKHASH or
the
== Series Details ==
Series: YOCTO #12937 - Consistent naming scheme for deployed artifacts (rev2)
Revision: 2
URL : https://patchwork.openembedded.org/series/19321/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response.
From: He Zhe
Add a patch to fix the following failure.
rt_sigtimedwait011 TFAIL : .../sigwaitinfo01.c:58: test_empty_set
(.../sigwaitinfo01.c: 148): Unexpected failure:
TEST_ERRNO=EINVAL(22): Invalid argument
Signed-off-by: He Zhe
---
..._sigwaitinfo01-Fix-failure-for-MIPS-arche.patch
From: Mazliana
Purpose of kernel development is basically to customize our
own recipes kernel by reused existing recipes.
This is an initiative of automating manual kernel development
test cases. Applying a single patch to the Linux kernel source
is one of the manual test cases of kernel
== Series Details ==
Series: oeqa/kerneldevelopment: Able to apply a single patch to the Linux
kernel source (rev3)
Revision: 3
URL : https://patchwork.openembedded.org/series/19411/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an
From: Kai Kang
Package libinput has a package config 'libwacom'. When it is set,
package libwacom is required. So add the recipe of libwacom.
Signed-off-by: Kai Kang
---
meta/recipes-graphics/libwacom/libwacom_0.33.bb | 15 +++
1 file changed, 15 insertions(+)
create mode 100644
If the PACKAGECONFIG item, python3, is enabled, we get the following
QA issue when multilib is enabled.
ERROR: bind-9.11.5-P4-r0 do_package: QA Issue: bind: Files/directories were
installed but not shipped in any package:
/usr/lib
/usr/lib/python3.7
/usr/lib/python3.7/site-packages
On Tue, 2019-08-20 at 17:32 +0200, Alexander Kanavin wrote:
> This is the qemu default since qemu 2.2, is generally supported
> better,
> and is recommended by upstream. It also has already been in use for
> arm/risc
> and ovmf.
>
> Additional information:
>
This file is giving misleading information. There's a patch
for bitbake to remove the generation of this file. Remove
it from OEQA as well.
Signed-off-by: Chen Qi
---
meta/lib/oeqa/selftest/cases/bbtests.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Ping..
The /etc/screenrc exists in other distributions as the default config file.
//Yi
On 8/16/19 4:56 PM, Yi Zhao wrote:
Signed-off-by: Yi Zhao
---
meta/recipes-extended/screen/screen_4.6.2.bb | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
On Mon, 5 Aug 2019 at 18:39, chris.lapla...@agilent.com <
chris.lapla...@agilent.com> wrote:
> > But I would like something smarter, e.g. first trying to check if the
> SRC_URI is available, if not switching on using the prebuilt package if
> available (e.g.
> > in a DIR_PREBUILT)...
> >
> >
This solves the following errors:
src/mips/o32.S: Assembler messages:
src/mips/o32.S:286: Error: opcode not supported on this processor:
mips32r2 (mips32r2) `s.d $f12,((16*4)-10*4)($fp)'
src/mips/o32.S:287: Error: opcode not supported on this processor:
mips32r2 (mips32r2) `s.d
== Series Details ==
Series: libffi: Make it build for MIPS o32
Revision: 1
URL : https://patchwork.openembedded.org/series/19446/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been executed on
On Fri, 23 Aug 2019 at 10:20, wrote:
> Package libinput has a package config 'libwacom'. When it is set,
> package libwacom is required. So add the recipe of libwacom.
>
This recipe probably needs to go to meta-oe? Why oe-core?
Alex
--
___
On Fri, 23 Aug 2019 at 11:13, Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:
> The patches in master-next had some failures:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/85/builds/636
>
> I think but am not 100% sure it could from this patch?
>
Yes, at least two of
On 8/22/19 7:29 PM, mazliana.moha...@intel.com wrote:
> From: Mazliana
>
> Purpose of kernel development is basically to customize our
> own recipes kernel by reused existing recipes.
>
> This is an initiative of automating manual kernel development
> test cases. Applying a single patch to
On Fri, Aug 23, 2019 at 09:28:11AM +0800, Hongxu Jia wrote:
> On 8/23/19 1:01 AM, Adrian Bunk wrote:
> > On Thu, Aug 22, 2019 at 09:40:18AM +0800, Hongxu Jia wrote:
> > > - Update Debian patches
> > >
> > > http://ftp.de.debian.org/debian/pool/main/e/elfutils/elfutils_0.176-1.debian.tar.xz
> >
It is possible if a user really has to use it, but not recommended.
Signed-off-by: Adrian Bunk
---
meta/recipes-core/systemd/systemd_242.bb | 6 ++
1 file changed, 6 insertions(+)
diff --git a/meta/recipes-core/systemd/systemd_242.bb
b/meta/recipes-core/systemd/systemd_242.bb
index
It only printed a warning since Yocto 2.4,
documented to be removed in a future release.
Signed-off-by: Adrian Bunk
---
meta/recipes-kernel/linux/linux-dtb.inc | 3 ---
1 file changed, 3 deletions(-)
delete mode 100644 meta/recipes-kernel/linux/linux-dtb.inc
diff --git
Remove backported patches applied upstream.
Signed-off-by: Adrian Bunk
---
meta/recipes-core/systemd/systemd.inc | 2 +-
...-max-sysctl-to-LONG_MAX-rather-than-.patch | 39
.../systemd/0001-networkd-fix-link-up.patch | 66 -
On 8/23/19 10:26 PM, Adrian Bunk wrote:
On Fri, Aug 23, 2019 at 09:28:11AM +0800, Hongxu Jia wrote:
On 8/23/19 1:01 AM, Adrian Bunk wrote:
On Thu, Aug 22, 2019 at 09:40:18AM +0800, Hongxu Jia wrote:
- Update Debian patches
== Series Details ==
Series: systemd: Update to the latest 242 branch
Revision: 1
URL : https://patchwork.openembedded.org/series/19451/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been
This solves the following errors:
src/mips/o32.S: Assembler messages:
src/mips/o32.S:286: Error: opcode not supported on this processor:
mips32r2 (mips32r2) `s.d $f12,((16*4)-10*4)($fp)'
src/mips/o32.S:287: Error: opcode not supported on this processor:
mips32r2 (mips32r2) `s.d
From: "Bedel, Alban"
It do make sense to start rngd early in the boot process because
otherwise we would need to track every service that might need entropy
and explicitly configure it to start after rngd.
When used with systemd rngd blocked the shutdown process because it
simply missed the
Without this change, images with systemd hang on shutdown/reboot.
On Fri, Aug 23, 2019 at 1:39 PM Fabio Berton
wrote:
>
> From: "Bedel, Alban"
>
> It do make sense to start rngd early in the boot process because
> otherwise we would need to track every service that might need entropy
> and
On Mon, Aug 5, 2019 at 9:06 AM Loic Poulain wrote:
> Say a company works with an OE internal tree, with open-source and
> closed-source packages. The company wants to release the tree so that its
> customers can fully customize the images/distro. The closed sources being
> only available
49 matches
Mail list logo
