Our binutils is configured with --enable-deterministic-archives, so ar
runs in deterministic mode by default. The ar01 case would fail because
it doesn't consider this mode. Backport a patch from upstream to fix
this issue.
Signed-off-by: Yi Zhao
---
...s-ar01-Fix-for-test-in-deterministic-mode.
The tar from busybox lacks some options that cause the tar01 case
failed. Add tar as runtime dependency.
Signed-off-by: Yi Zhao
---
meta/recipes-extended/ltp/ltp_20170929.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-extended/ltp/ltp_20170929.bb
b/meta/recipes-extended/ltp
Yi Zhao (2):
ltp: add tar as runtime dependency
ltp: fix ar01 case failure
...s-ar01-Fix-for-test-in-deterministic-mode.patch | 252 +
meta/recipes-extended/ltp/ltp_20170929.bb | 2 +
2 files changed, 254 insertions(+)
create mode 100644
meta/recipes-extende
The SquashFS filesystem does not support UUIDs so make this combination
be an error.
Signed-off-by: Tom Rini
---
scripts/lib/wic/ksparser.py | 5 +
1 file changed, 5 insertions(+)
diff --git a/scripts/lib/wic/ksparser.py b/scripts/lib/wic/ksparser.py
index 7850e81d2f37..4fb6868531df 100644
First, allow for wic to be given a filesystem UUID to be used when
creating a filesystem. When not provided, wic will generate the UUID to
be used. Next, when --use-uuid is passed, we update the fstab to mount
things via UUID (and if not found, then use PARTUUID) as UUID is more
portable.
Signed
Hey all,
So, per Ed's feedback on my first series, I went and spent some time
trying to figure out how to have wic know what the UUID would be when
updating the fstab. It turns out the easiest answer here is to have WIC
make the UUID. Per Otavio's concern last time, I also make sure that
the fil
- Mount a '/media' partition to wic-image-minimal.wks with a known UUID.
- In test_qemu, sort our output from checking the output of 'mount' as
it may not be stable. Also, do not check the exit code as passing any
output to cut ensures a 0 exit code.
- Check for a 'UUID=' line in /etc/fstab wi
First, we support squashfs as root, so mention that. Second, the btrfs
rootfs creation function had a copy/paste of the previous function
comment, remove the irrelevant line.
Signed-off-by: Tom Rini
---
scripts/lib/wic/partition.py | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff
On Wed, Dec 13, 2017 at 09:45:13PM -0500, Tom Rini wrote:
> On Wed, Dec 13, 2017 at 02:40:34PM +, Burton, Ross wrote:
>
> > I finally made it break locally, with MACHINE=qemux86 and using sysvinit
> > instead of systemd. Basically, a pristine poky local.conf. I've not dug
> > into it beyond
On Wed, Dec 13, 2017 at 02:40:34PM +, Burton, Ross wrote:
> I finally made it break locally, with MACHINE=qemux86 and using sysvinit
> instead of systemd. Basically, a pristine poky local.conf. I've not dug
> into it beyond that, or why it passes with systemd.
I found it, and, erm, ugh? He
While building fitimage with initramfs bundle using INITRAMFS_IMAGE and
INITRAMFS_IMAGE_BUNDLE = "1", we have few failures
do_bundle_initramfs fails first stating the below error
| CHK include/generated/compile.h
| CHK kernel/config_data.h
| mv: cannot stat 'arch/arm64/boot/fitImage':
When deploying fitImage with initramfs bundle deploy fails with
following error
| DEBUG: Python function extend_recipe_sysroot finished
| DEBUG: Executing shell function do_deploy
| install: cannot stat 'arch/arm64/boot/fitImage': No such file or
directory
Skip using the do_deploy for fitimage in
From: Thomas Perrot
When compiling fitImage with initramfs bundle, the build breaks by
throwing the following error
| CHK include/generated/compile.h
| CHK kernel/config_data.h
| mv: cannot stat 'arch/arm64/boot/fitImage': No such file or directory
Fix the error during this compilati
>From 1.25.0 onwards, busybox dropped systemd compatibility from its
version of syslogd:
https://git.busybox.net/busybox/commit/?id=accd9eeb719916da974584b33b1aeced5f3bb346
Signed-off-by: Andre McCurdy
---
meta/recipes-core/busybox/busybox/musl.cfg | 1 -
1 file changed, 1 deletion(-)
diff
On Wed, Dec 13, 2017 at 02:40:34PM +, Burton, Ross wrote:
> I finally made it break locally, with MACHINE=qemux86 and using sysvinit
> instead of systemd. Basically, a pristine poky local.conf. I've not dug
> into it beyond that, or why it passes with systemd.
OK, thanks! I'll see if I can
On 2017-12-13 7:04 PM, Richard Purdie wrote:
On Wed, 2017-12-13 at 19:01 -0500, Bruce Ashfield wrote:
On 2017-12-13 9:14 AM, Richard Purdie wrote:
On Wed, 2017-12-13 at 09:07 -0500, Bruce Ashfield wrote:
On 12/13/2017 09:05 AM, Richard Purdie wrote:
On Wed, 2017-12-13 at 08:38 -0500, Bruc
Signed-off-by: Andre McCurdy
Signed-off-by: Ross Burton
(cherry picked from commit 0c89b010ce2e426f55ac7c6f94befef988913834)
---
meta/recipes-devtools/cmake/cmake.inc | 1 +
...void-gcc-warnings-with-Wstrict-prototypes.patch | 42 ++
2 files changed, 43 insertio
- This release features JSON output for many commands and greater
support of offloading to hardware.
- Config is changed to config.mk
Signed-off-by: Changhyeok Bae
---
meta/recipes-connectivity/iproute2/iproute2.inc | 2 +-
.../iproute2/0001-libc-compat.h-add-musl-workaround
On 2017-12-13 7:04 PM, Richard Purdie wrote:
On Wed, 2017-12-13 at 19:01 -0500, Bruce Ashfield wrote:
On 2017-12-13 9:14 AM, Richard Purdie wrote:
On Wed, 2017-12-13 at 09:07 -0500, Bruce Ashfield wrote:
On 12/13/2017 09:05 AM, Richard Purdie wrote:
On Wed, 2017-12-13 at 08:38 -0500, Bruc
On Wed, 2017-12-13 at 19:01 -0500, Bruce Ashfield wrote:
> On 2017-12-13 9:14 AM, Richard Purdie wrote:
> >
> > On Wed, 2017-12-13 at 09:07 -0500, Bruce Ashfield wrote:
> > >
> > > On 12/13/2017 09:05 AM, Richard Purdie wrote:
> > > >
> > > >
> > > > On Wed, 2017-12-13 at 08:38 -0500, Bruce Ash
On 2017-12-13 9:14 AM, Richard Purdie wrote:
On Wed, 2017-12-13 at 09:07 -0500, Bruce Ashfield wrote:
On 12/13/2017 09:05 AM, Richard Purdie wrote:
On Wed, 2017-12-13 at 08:38 -0500, Bruce Ashfield wrote:
On 12/13/2017 07:34 AM, Richard Purdie wrote:
Hi Bruce,
https://bugzilla.yoctoproje
On Wed, Dec 13, 2017 at 03:52:29PM +0100, Kristian Amlie wrote:
> See the patch for details. This patch has already been applied
> upstream, but we need it for v2017.11.
>
> Upstream-Status: Accepted
> [http://git.denx.de/?p=u-boot.git;a=commit;h=ded84f90a1066eef5f34daa4539273de64f7b811]
>
> Si
As we may be using external toolchains, we cannot assume
various compiler options to be valid.
Signed-off-by: Juro Bystricky
---
meta/classes/compiler-options.bbclass | 24
1 file changed, 24 insertions(+)
create mode 100644 meta/classes/compiler-options.bbclass
diff -
We use gcc option "-ffile-prefix-map" if available.
Remove the local code that detects the availability of this
compiler option (get_cc_option) and use a more generic code
imported from compiler-option.bbclass.
Signed-off-by: Juro Bystricky
---
meta/classes/kernel.bbclass | 15 +++
1
Use gcc option "-ffile-prefix-map" if available.
This will remap any hard-coded __FILE__ containing build host
path to a reproducible value, with the absolute build-host path
stripped.
Signed-off-by: Juro Bystricky
---
meta/classes/module.bbclass | 5 +++--
1 file changed, 3 insertions(+), 2 del
1. Remove build host references from CFLAGS in generated config.h file.
They end up compiled in the image, but are only used for information.
2. Remove PA_BUILDDIR hardcoded references: safe to remove as we are guaranteed
not to run from the build directory when the image is cross-compiled
3.
The gcc that comes with OE-core supports a compiler option -ffile-prefix-map.
This option is essential in order to support binary reproducibility of packages
built from sources containing absolute paths due to various __FILE__ macros.
These can contain absolute path names of source code files as en
From: Thomas Perrot
When using kernel-fitimage class with aarch64, the image type has to be
Image not zImage. This patch fixes the bad image type replacement for
aarch64
Signed-off-by: Thomas Perrot
Signed-off-by: Manjukumar Matha
---
meta/classes/kernel-fitimage.bbclass | 7 +--
1 file
I rebased the patch to latest master (openembedded-core commit cf5c44ac)
and still can't reproduce what you're seeing. I can see a /boot/bzImage
symlink in both buildHistory [1] and the IPK [2].
Are you using the same source? It seems like your kernel version is
4.12.16 but linux-yocto is at 4
On 2017-12-13 19:06, Stefan Agner wrote:
> From: Stefan Agner
>
> OpenEmbedded has a built-in mechanism to run postinst scripts offline
> at build time or, if necessary, on first boot (delayed execution). If
> the latter is the case and systemd is in use, two services end up
> doing the same thin
From: Stefan Agner
OpenEmbedded has a built-in mechanism to run postinst scripts offline
at build time or, if necessary, on first boot (delayed execution). If
the latter is the case and systemd is in use, two services end up
doing the same thing:
- opkg-configure.service starts "opkg configure" w
Hi Alex,
On Thursday, 14 December 2017 3:53:22 AM NZDT Alexander Kanavin wrote:
> On 12/05/2017 03:41 AM, Paul Eggleton wrote:
> > A set of improvements for devtool, mostly aimed at improving the
> > handling of recipes that fetch multiple source trees (i.e. have multiple
> > tarballs or repositor
'bitbake -c checkpkg world' is moved to class initializer to avoid
it being run twice in a row.
Signed-off-by: Alexander Kanavin
---
meta/lib/oeqa/selftest/cases/distrodata.py | 32 +-
1 file changed, 27 insertions(+), 5 deletions(-)
diff --git a/meta/lib/oeqa/selfte
This command queries the upstream server for what the latest release is and
prints
the output; it is a much neater way to find out these things than fumbling with
distrodata,
'bitbake -c checkpkg' and awkward to read csv output in a file.
Examples:
python3 (tarballs):
NOTE: Current version: 3.5
Specifically, 'devtool upgrade' will now do these things:
1) determine if any of the license checksums need updating; if so,
write the new checksums into the LIC_FILES_CHKSUM value in the recipe
that is written to the workspace;
2) print a notice to the standard output:
NOTE: New recipe is
/hom
Specifically, 'devtool upgrade' will use the latest upstream release if
available
or latest commit if upstream never makes releases.
Signed-off-by: Alexander Kanavin
---
scripts/lib/devtool/upgrade.py | 16
1 file changed, 12 insertions(+), 4 deletions(-)
diff --git a/scripts/
Switch to gitlab, as that's where development now happens.
Drop two upstreamed patches, add apatches to avoid newly
introduced build errors, and a gettext fix suggested here:
http://lists.openembedded.org/pipermail/openembedded-core/2017-November/144566.html
Signed-off-by: Alexander Kanavin
---
Schroedinger support has been dropped:
https://git.ffmpeg.org/gitweb/ffmpeg.git/commitdiff/220b24c7c9
Remove upstreamed patch.
Signed-off-by: Alexander Kanavin
---
.../ffmpeg/ffmpeg/0001-build-fix-for-mips.patch| 44 --
.../ffmpeg/{ffmpeg_3.3.4.bb => ffmpeg_3.4.bb}
Signed-off-by: Alexander Kanavin
---
meta/conf/distro/include/maintainers.inc | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/conf/distro/include/maintainers.inc
b/meta/conf/distro/include/maintainers.inc
index 9e5dbe17269..1e7f249b611 100644
--- a/meta/conf/distro/include/maintainers.i
Signed-off-by: Alexander Kanavin
---
meta/conf/distro/include/maintainers.inc | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/conf/distro/include/maintainers.inc
b/meta/conf/distro/include/maintainers.inc
index 856a6b763bf..9e5dbe17269 100644
--- a/meta/conf/distro/include/maintainers.i
gcc7.patch, musl-fixes.patch, and ppc-musl-fix.patch all change code that is no
longer present in upstream tree. However, a patch with different musl fixes
has been added.
The rest of the patches are rebased to the new tree.
Libtasn is a new dependency.
Disable Gstreamer GL support on x86 due to
Drop upstreamed patch.
Rebase the other patches.
Signed-off-by: Alexander Kanavin
---
...eck-conf.releasever-instead-of-releasever.patch | 31 --
...Corretly-install-tmpfiles.d-configuration.patch | 7 ++---
...hardcode-etc-and-systemd-unit-directories.patch | 9 ---
..
Signed-off-by: Alexander Kanavin
---
...Get-parameters-for-both-libsolv-and-libsolvext-libdn.patch | 11 ++-
...Set-libsolv-variables-with-pkg-config-cmake-s-own-mo.patch | 11 ++-
.../libdnf/{libdnf_0.9.3.bb => libdnf_0.11.1.bb} | 2 +-
3 files changed, 13 insertion
Signed-off-by: Alexander Kanavin
---
...ect-introspection_1.52.1.bb => gobject-introspection_1.54.1.bb} | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
rename
meta/recipes-gnome/gobject-introspection/{gobject-introspection_1.52.1.bb =>
gobject-introspection_1.54.1.bb} (97%)
diff
Drop upstreamed patches, rebase the PYTHON_INSTALL_DIR patch.
Signed-off-by: Alexander Kanavin
---
...ly-set-the-library-installation-directory.patch | 28 -
...to-obtain-PYTHON_INSTALL_DIR-by-running-p.patch | 49 +++---
...-race-when-deleting-temporary-directories.p
Previously oe-core had a development snapshot of rpm, it's better to update
to something more stable.
Removed patches:
0001-Add-PYTHON_ABI-when-searching-for-python-libraries.patch
(upstream is using pkg-config)
0001-When-nice-value-cannot-be-reset-issue-a-notice-inste.patch
(functionality has bee
Debugedit provided by rpm 4.14 is rewriting binaries in-place, and was
found to produce broken output at least for grub:
http://lists.openembedded.org/pipermail/openembedded-core/2017-November/143989.html
A replacement utility was suggested via private mail:
https://lists.fedorahosted.org/archives
On 12/05/2017 03:41 AM, Paul Eggleton wrote:
A set of improvements for devtool, mostly aimed at improving the
handling of recipes that fetch multiple source trees (i.e. have multiple
tarballs or repositories in SRC_URI), with a couple of other fixes
thrown in.
Unfortunately, this badly breaks '
See the patch for details. This patch has already been applied
upstream, but we need it for v2017.11.
Upstream-Status: Accepted
[http://git.denx.de/?p=u-boot.git;a=commit;h=ded84f90a1066eef5f34daa4539273de64f7b811]
Signed-off-by: Kristian Amlie
---
.../u-boot/files/v2017.11-fw-utils-build-fix.
I finally made it break locally, with MACHINE=qemux86 and using sysvinit
instead of systemd. Basically, a pristine poky local.conf. I've not dug
into it beyond that, or why it passes with systemd.
Ross
On 28 November 2017 at 15:55, Tom Rini wrote:
> On Fri, Nov 24, 2017 at 10:36:11AM -0500, T
== Series Details ==
Series: u-boot-fw-utils: Fix broken makefile in v2017.11. (rev2)
Revision: 2
URL : https://patchwork.openembedded.org/series/10173/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests
On Wed, Dec 13, 2017 at 03:03:27PM +0100, Kristian Amlie wrote:
> See the patch for details. This patch has already been applied
> upstream, but we need it for v2017.11.
>
> Upstream-Status: Accepted
> [http://git.denx.de/?p=u-boot.git;a=commit;h=ded84f90a1066eef5f34daa4539273de64f7b811]
>
> Si
On Wed, Dec 13, 2017 at 02:25:50PM +0100, Kristian Amlie wrote:
> See the patch for details. This patch has already been applied
> upstream, but we need it for v2017.11.
>
> Signed-off-by: Kristian Amlie
Reviewed-by: Tom Rini
--
Tom
--
___
Openemb
On 12/13/2017 09:24 AM, Burton, Ross wrote:
On 13 December 2017 at 14:17, Bruce Ashfield
mailto:bruce.ashfi...@windriver.com>> wrote:
yow-bashfiel-d4 [/home/bruc...poky/build]> oe-selftest -r
runqemu.RunqemuTests.test_boot_deploy
Traceback (most recent call last):
File "/home
On 13 December 2017 at 14:17, Bruce Ashfield
wrote:
> yow-bashfiel-d4 [/home/bruc...poky/build]> oe-selftest -r
> runqemu.RunqemuTests.test_boot_deploy
> Traceback (most recent call last):
> File "/home/bruce/poky/scripts/oe-selftest", line 43, in
> from oeqa.utils import load_test_compone
On 12/13/2017 09:14 AM, Richard Purdie wrote:
On Wed, 2017-12-13 at 09:07 -0500, Bruce Ashfield wrote:
On 12/13/2017 09:05 AM, Richard Purdie wrote:
On Wed, 2017-12-13 at 08:38 -0500, Bruce Ashfield wrote:
On 12/13/2017 07:34 AM, Richard Purdie wrote:
Hi Bruce,
https://bugzilla.yoctoproj
On Wed, 2017-12-13 at 09:07 -0500, Bruce Ashfield wrote:
> On 12/13/2017 09:05 AM, Richard Purdie wrote:
> >
> > On Wed, 2017-12-13 at 08:38 -0500, Bruce Ashfield wrote:
> > >
> > > On 12/13/2017 07:34 AM, Richard Purdie wrote:
> > > >
> > > >
> > > > Hi Bruce,
> > > >
> > > > https://bugzilla
On 12/13/2017 09:05 AM, Richard Purdie wrote:
On Wed, 2017-12-13 at 08:38 -0500, Bruce Ashfield wrote:
On 12/13/2017 07:34 AM, Richard Purdie wrote:
Hi Bruce,
https://bugzilla.yoctoproject.org/show_bug.cgi?id=12301
We've root caused the hangs we're seeing in qemux86-64 on our
autobuilder wor
On Wed, 2017-12-13 at 08:38 -0500, Bruce Ashfield wrote:
> On 12/13/2017 07:34 AM, Richard Purdie wrote:
> >
> > Hi Bruce,
> >
> > https://bugzilla.yoctoproject.org/show_bug.cgi?id=12301
> >
> > We've root caused the hangs we're seeing in qemux86-64 on our
> > autobuilder workers. We've identifi
See the patch for details. This patch has already been applied
upstream, but we need it for v2017.11.
Upstream-Status: Accepted
[http://git.denx.de/?p=u-boot.git;a=commit;h=ded84f90a1066eef5f34daa4539273de64f7b811]
Signed-off-by: Kristian Amlie
---
.../u-boot/files/v2017.11-fw-utils-build-fix.
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
On 12/13/2017 07:34 AM, Richard Purdie wrote:
Hi Bruce,
https://bugzilla.yoctoproject.org/show_bug.cgi?id=12301
We've root caused the hangs we're seeing in qemux86-64 on our
autobuilder workers. We've identified a commit on 4.15-rc3 which fixes
the issue but backporting it to the autobuilder's
== Series Details ==
Series: u-boot-fw-utils: Fix broken makefile in v2017.11.
Revision: 1
URL : https://patchwork.openembedded.org/series/10173/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have be
See the patch for details. This patch has already been applied
upstream, but we need it for v2017.11.
Signed-off-by: Kristian Amlie
---
.../u-boot/files/v2017.11-fw-utils-build-fix.patch | 37 ++
meta/recipes-bsp/u-boot/u-boot-common_2017.11.inc | 1 +
2 files changed, 38 i
Hi Bruce,
https://bugzilla.yoctoproject.org/show_bug.cgi?id=12301
We've root caused the hangs we're seeing in qemux86-64 on our
autobuilder workers. We've identified a commit on 4.15-rc3 which fixes
the issue but backporting it to the autobuilder's host kernels will be
a pain.
As a workaround I'
On 12 December 2017 at 22:19, Haris Okanovic wrote:
> I can see a reference to "/boot/bzImage" in both buildhistory and
> tmp-glibc/work/.../pkgdata [1] after running a clean rebuild of
> virtual/kernel [2].
>
> [1] file paths:
>
> "buildhistory/packages/qemux86-oe-linux/linux-yocto/kernel-
> ima
On 13 December 2017 at 02:42, Allen Wild wrote:
> Oops, forgot mail the list when sending my first reply.
>
> I tried appending LDFLAGS, but it doesn't work for syslinux. It's
> during do_install, not do_compile, that $(LD) is called directly to
> link libutil.elf, libcom32.elf, libgpl.elf, and l
Setup a directory tree for source code according to section name.
(if known).
This tree is intended for code browsing ONLY.
If source is moved, for instance with devtool modify,
this command should be rerun to be up-to-date with that move.
Signed-off-by: Tobias Hagelborn
---
scripts/lib/devtool
This class is used to create a symlink to the source in ${S} in a
separate directory structure. ${SECTION} is used, if available, for
naming the path.
Intended for 'devtool srctree ' to set up a tree with the
source for all specified recipes and their dependencies to be able
to do a more convenien
UPDATE v2:
- Moved default output dir to ${TMPDIR}/srctree
- Retested on Pyro master (core-image-sato/core-image-minimal)
In our organization, there is a demand to be able to download source code for
searching.
With the use of sstate-cache this has been challenge. Also, the source is not
gathere
On 09/05/2017 02:10 PM, Randy MacLeod wrote:
On 2017-09-01 08:00 AM, Peter Kjellerstedt wrote:
Well, the most common request we've gotten from the developers is that
they want to be able to search through all the sources, e.g., to find
out where a particular function is used. The tmp directory d
71 matches
Mail list logo
