I don't see how this change (or the previous glibc-locale one) would cause
that, but since the oe-core upgrade yesterday I'm seeing following
glibc-locale.do_package failure:
http://errors.yoctoproject.org/Errors/Details/250557/
DEBUG: Executing shell function do_prep_locale_tree
tar: i18n: Cannot
On Mon, Jul 01, 2019 at 10:58:04AM -0500, Joshua Watt wrote:
> I'm curious what people thing about all this; How important is
> reproducibility? How reproducible do we want to be? How hard should it
> be to have reproducible builds? What trade-offs are willing to be made
> for reproducible build
> Changes to the sysroot as just as
small typo in commit message if you need to update this commit again for
whatever other reason.
On Thu, Jun 27, 2019 at 2:29 PM Ross Burton wrote:
> Changes to the sysroot as just as interesting during development, so write
> the
> file listing for the sysroo
On Mon, Jun 24, 2019 at 08:44:42AM -0400, bruce.ashfi...@gmail.com wrote:
> From: Bruce Ashfield
>
> Updating the scsci-debug fragment to include the core scsci config
> options. This allows standalone use of the fragment, since all
> supporting options will be enabled simply by including the top
Hi,
I think this will backport also this warning:
http://lists.openembedded.org/pipermail/openembedded-core/2019-June/283912.html
can it be backported together with the fix for it from Bruce:
http://lists.openembedded.org/pipermail/openembedded-core/2019-June/283913.html
I haven't noticed the fix
Fri, Jun 21, 2019 at 11:08 AM Changqing Li
wrote:
>
> On 6/21/19 4:32 PM, Martin Jansa wrote:
> > On Tue, Jun 18, 2019 at 03:46:56PM +0800, changqing...@windriver.com
> wrote:
> >> From: Changqing Li
> >>
> >> The SDK was unable to find the C++ header piec
-oemllib32-linux-gnueabi/
bits ext
* make sure to create correct directory (with -${TARGET_OS suffix instead of
-linux suffix)
before creating the symlinks in it
Signed-off-by: Martin Jansa
---
meta/recipes-devtools/gcc/gcc-runtime.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
On Tue, Jun 18, 2019 at 03:46:56PM +0800, changqing...@windriver.com wrote:
> From: Changqing Li
>
> The SDK was unable to find the C++ header pieces correctly since it's
> using a generic compiler, not one specifically targeting the multilib
> vendor prefix and default tune. This adds the right
Hi,
One of these recent updates is causing following WARNING:
-- CONFIG_SCSI_DEBUG -
Config: CONFIG_SCSI_DEBUG
From:
work-shared/qemuarm/kernel-source/.kernel-meta/configs/v5.0/standard/features/scsi/scsi-debug.cfg
Requested value: CONFIG_SCSI_DEBUG=m
Actual value:
No
On Thu, Jun 20, 2019 at 11:09:39AM -0600, Khem Raj wrote:
> On Thu, Jun 20, 2019 at 1:15 AM Adrian Bunk wrote:
> >
> > On Wed, Jun 19, 2019 at 12:59:05PM -0700, Khem Raj wrote:
> > > On Fri, Jun 14, 2019 at 4:44 AM Richard Purdie <
> > > richard.pur...@linuxfoundation.org> wrote:
> > >
> > > > On
and empty libdir at the end).
So in the end I think it was an issue caused by the custom path
validator in serf's SConstruct, removing that stops touching host
and the installed paths (including the paths inside libserf*.pc)
look correct
Signed-off-by: Martin Jansa
---
...ories.without.sandb
oe-core likes to mix them :)
On Tue, Jun 18, 2019 at 9:14 PM Khem Raj wrote:
> On Tue, Jun 18, 2019 at 12:09 PM Martin Jansa
> wrote:
> >
> > * since 1522f09a4d serf: cleanup recipe
> > serf.do_install fails in builds with multilib enabled (with
> > libdir
and empty libdir at the end).
So in the end I think it was an issue caused by the custom path
validator in serf's SConstruct, removing that stops touching host
and the installed paths (including the paths inside libserf*.pc)
look correct
Signed-off-by: Martin Jansa
---
...ories.without.sandb
/doc/cmake-3.14
-DCMAKE_USE_SYSTEM_LIBRARIES=1 -DCMAKE_USE_SYSTEM_LIBRARY_JSONCPP=0
-DCMAKE_USE_SYSTEM_LIBRARY_LIBUV=0
-DCMAKE_USE_SYSTEM_LIBRARY_LIBRHASH=0 -DKWSYS_CHAR_IS_SIGNED=1
-DBUILD_CursesDialog=0 -DKWSYS_LFS_WORKS=1
\${PACKAGECONFIG_CONFARGS}"
Signed-off-b
* especially when pushing longer history to slow remote git server or when
it timeouts during the push, it's useful to see where the time was actually
spent
Signed-off-by: Martin Jansa
---
meta/classes/buildhistory.bbclass | 4
1 file changed, 4 insertions(+)
diff --git a/meta/cl
Hello, now serf is failing to build here:
DEBUG: Executing python function extend_recipe_sysroot
NOTE: Direct dependencies are
['TOPDIR/oe-core/meta/recipes-devtools/gcc/gcc-runtime_9.1.bb:do_populate_sysroot',
'TOPDIR/oe-core/meta/recipes-core/util-linux/util-linux_2.33.2.bb:do_populate_sysroot'
Sure, follow-up patch is fine with me.
On Thu, Jun 13, 2019 at 8:38 PM Marco Felsch
wrote:
> Hi Martin,
>
> On 19-06-13 20:17, Martin Jansa wrote:
> > Looks like nice cleanup, but is someone still using llvm 3.2 or older?
>
> I don't know but I learned to avoid br
Looks like nice cleanup, but is someone still using llvm 3.2 or older?
With PACKAGECONFIG for almost each gallium driver it might be easier to get
rid
of GALLIUMDRIVERS_LLVM33, GALLIUMDRIVERS_LLVM33_ENABLED, GALLIUMDRIVERS_LLVM
variables and use just GALLIUMDRIVERS.
In worst case scenario people
From: Martin Jansa
* bc can be provided by busybox as well (e.g. if you have your own
defconfig and forget to explicitly disable it:
...
*
* Miscellaneous Utilities
*
adjtimex (4.7 kb) (ADJTIMEX) [N/y/?] n
bbconfig (9.7 kb) (BBCONFIG) [N/y/?] n
bc (45 kb) (BC) [Y/n/?] (NEW) dc
irectories
(pigz in base_bindir and gzip in bindir) and it's only 130kB..
Signed-off-by: Martin Jansa
---
meta/recipes-extended/pigz/pigz_2.4.bb | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-extended/pigz/pigz_2.4.bb
b/meta/recipes-extended/pigz/pi
Thanks!
On Wed, Jun 12, 2019 at 3:35 AM Hongxu Jia wrote:
> On 6/12/19 4:01 AM, Martin Jansa wrote:
> > Hi,
> >
> > when accidentally checking for some old meta-oe commit in oe-core
> > repository I was surprised that it was found in some of the contrib
> > br
This is just FYI:
This probably won't happen with most of OE use-cases, but even with pigz
being the drop in replacement, there are some differences, e.g. when I'm
using pigz-2.4 on my Gentoo host as gzip, xmltex-1.9.tar.gz fails to unpack
gzip: warning:
/tmp/tmpfs/portage/dev-tex/xmltex-1.9-r2/di
Hi,
when accidentally checking for some old meta-oe commit in oe-core
repository I was surprised that it was found in some of the contrib
branches:
~/openembedded-core $ git branch -a --contains 30bbde3d09e
remotes/contrib/hongxu/add-recipes-20190215
remotes/contrib/hongxu/dbg-split
remotes
Also the version went from 0.13.2 to 1.0 which doesn't match with the
sources. Don't forget to set PV when migrating recipes to use git fetcher.
On Tue, Jun 11, 2019 at 3:58 AM Douglas Royds via Openembedded-core <
openembedded-core@lists.openembedded.org> wrote:
> Upstream json-c haven't made a
From: Richard Purdie
The dbus-test package is empty, move its dependencies to the ${PN}-ptest
package. Also ensure that it doesn't depend on the empty ${PN} package
which is about to start causing image failures in the following commit.
In this case the correct dependency is dbus itself.
Signed-
On Fri, Jun 07, 2019 at 12:58:30PM +, g...@git.openembedded.org wrote:
> This is an automated email from the git hooks/post-receive script.
>
> rpurdie pushed a commit to branch warrior
> in repository openembedded-core.
>
> commit 1ad805984c8c9c9a505b6b0e8ad870b8233b13b2
> Author: Richard Pu
openembedded-core/scripts/sstate-diff-machines.sh --targets=world
--tmpdir=tmp-glibc/ --analyze --machines="hammerhead mako qemux86"
Signed-off-by: Martin Jansa
---
meta/classes/grub-efi-cfg.bbclass | 3 +++
meta/classes/systemd-boot-cfg.bbclass | 3 +++
2 files changed, 6 insertions(
On Mon, Jun 03, 2019 at 09:47:02AM +0300, Adrian Bunk wrote:
> Signed-off-by: Adrian Bunk
> --
You need one more dash here, now this v2 comment ended in final commit message
which I believe wasn't the intention.
http://git.openembedded.org/openembedded-core/commit/?id=6fa60ac102f6d3977df4236bd5a
Signed-off-by: Martin Jansa
---
v2: Upstream-Status changed from Submitted to Backport
...fields-fix-to-print-the-fields-again.patch | 41 +++
.../opkg-utils/opkg-utils_0.4.0.bb| 1 +
2 files changed, 42 insertions(+)
create mode 100644
meta/recipes-devtools/opkg
> Web: http://www.bmw-carit.de
> -
> BMW Car IT GmbH
> Geschäftsführer: Kai-Uwe Balszuweit und Christian Salzmann
> Sitz und Registergericht: München HRB 134810
> ---
In those recipes which don't include SRCPV in PV (for whatever reason) we
usually add them explicitly with:
do_fetch[vardeps] += "SRCREV_common"
it's not ideal as people sometimes forget about this. Good practice is to
add this next to the SRCREV_FORMAT (if you set one, to clearly show which
revs a
It's still nicer to have
SRC_URI_append_libc-musl = " ${SRC_URI_MUSL}"
if the intermediate SRC_URI_MUSL variable is useful.
On Fri, May 24, 2019 at 7:59 PM Khem Raj wrote:
> On Fri, May 24, 2019 at 10:31 AM Richard Purdie
> wrote:
> >
> > On Fri, 2019-05-24 at 10:17 +0800, Chen Qi wrote:
> > >
are some other places where PACKAGECONFIG_CONFARGS is used, but
looks like all of them started to use it only after adding
PACKAGECONFIG options in the recipe
Signed-off-by: Martin Jansa
---
meta/classes/autotools.bbclass | 1 +
meta/classes/cmake.bbclass | 1 +
meta/classes/meson.bbclass
: Postinstall scriptlets of ['busybox'] have failed. If the
intention is to defer them to first boot,
then please place them into pkg_postinst_ontarget_${PN} (). Deferring to
first boot via 'exit 1' is no longer supported.
Signed-off-by: Martin Jansa
---
meta/recipes-extended/bc/bc_1
On Wed, May 22, 2019 at 10:09:16PM +0200, Martin Jansa wrote:
> On Wed, May 22, 2019 at 05:18:25PM +0300, Adrian Bunk wrote:
> > On Wed, May 22, 2019 at 01:03:37PM +0200, Martin Jansa wrote:
> > > This pulls bc to many images with busybox, causing busybox postinst to
>
On Wed, May 22, 2019 at 05:18:25PM +0300, Adrian Bunk wrote:
> On Wed, May 22, 2019 at 01:03:37PM +0200, Martin Jansa wrote:
> > This pulls bc to many images with busybox, causing busybox postinst to fail
> > with:
> >
> > update-alternatives: Error: not linking /usr/bi
Can we add an option to skip this with INSANE_SKIP?
It looks like QARECIPETEST doesn't use INSANE_SKIP or I don't see how.
Removing src-uri-bad from ERROR_QA/WARN_QA for some recipes works as well,
is it worth adding INSANE_SKIP for consistency with other checks or not?
On Sat, May 18, 2019 at
This pulls bc to many images with busybox, causing busybox postinst to fail
with:
update-alternatives: Error: not linking /usr/bin/bc to /bin/busybox.nosuid
since /usr/bin/bc exists and is not a link
I'll check which busybox defconfig entry enables BC and send patch to use
u-a for bc in ./meta/re
igned-off-by: Martin Jansa
---
meta/recipes-extended/acpica/acpica_20180508.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-extended/acpica/acpica_20180508.bb
b/meta/recipes-extended/acpica/acpica_20180508.bb
index cd5f466262..b5c89fafc5 100644
--- a/meta/re
This seems to be causing:
WARNING: acpica-20180508-r0 do_package: acpica: alternative target
(/usr/bin/acpidump or /usr/bin/acpidump.acpica) does not exist, skipping...
WARNING: acpica-20180508-r0 do_package: acpica: NOT adding alternative
provide /usr/bin/acpidump: /usr/bin/acpidump.acpica does no
On Sat, May 11, 2019 at 04:16:56PM +, Martin Jansa wrote:
> * to make it easier to rebase
ping?
I know this change alone doesn't look very useful (but it was useful
for me when rebasing other patches in other layers).
> Signed-off-by: Martin Jansa
> ---
> ...owerpc-chang
On Tue, May 14, 2019 at 02:02:10PM +0200, Martin Jansa wrote:
> Thanks all, I think the discussion made it clear that we shouldn't change
> the default yet.
>
> Makes it easier for me as I'll need this PACKAGECONFIG backported to
> warrior as well (and we shouldn'
And why change formatting in first place?
The old version seems better to me.
On Mon, May 20, 2019 at 7:56 PM Khem Raj wrote:
>
>
> On 5/20/19 7:11 AM, Alexander Kanavin wrote:
> > Signed-off-by: Alexander Kanavin
> > ---
> > .../linux-firmware/linux-firmware_git.bb | 128 +-
18, 2019 at 8:34 PM Tom Rini wrote:
> Now that we have a common inc file for both vim and vim-tiny move a few
> bits of logic out of vim.inc and in to vim_$VER.bb so that vim adds
> things rather than vim-tiny removes them.
>
> Suggested-by: Martin Jansa
> Signed-off-by: Tom Rini
Signed-off-by: Martin Jansa
---
.../python/bpo-35907-cve-2019-9948-fix.patch | 55 +
.../python/bpo-35907-cve-2019-9948.patch | 55 +
.../python/bpo-36216-cve-2019-9636-fix.patch | 28 +
.../python/bpo-36216-cve-2019-9636.patch | 111 ++
meta
To simplify meta/recipes-support/vim/vim-tiny_8.1.1240.bb which currently
has:
PROVIDES_remove = "xxd"
ALTERNATIVE_${PN}_remove = "xxd"
Can you move xxd from the .inc file and put it only in vim_8.1.1240.bb?
On Fri, May 17, 2019 at 3:53 PM Alexander Kanavin
wrote:
> Previously vim-tiny would
Actually the BBCLASSEXTEND = "native" as well, as we don't need both vim
recipes to provide xxd-native.
On Fri, May 17, 2019 at 4:27 PM Martin Jansa wrote:
> To simplify meta/recipes-support/vim/vim-tiny_8.1.1240.bb which currently
> has:
>
> PROVIDES_remove = "
ally is there a reson to use TUNE_PKGARCH here (unlike other
cross/canadian-cross recipes
which are using TARGET_ARCH/TRANSLATED_TARGET_ARCH)?
Signed-off-by: Martin Jansa
---
meta/conf/distro/include/tcmode-default.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/conf/d
openembedded-core/scripts/sstate-diff-machines.sh --targets=world
--tmpdir=tmp-glibc/ --analyze --machines="hammerhead mako qemux86"
Signed-off-by: Martin Jansa
---
meta/classes/grub-efi-cfg.bbclass | 3 +++
meta/classes/systemd-boot-cfg.bbclass | 3 +++
2 files changed, 6 insertions(
le or directory
WARNING: exit code 1 from a shell command.
* tools/include/uapi was added in kernel 4.8 with
https://github.com/torvalds/linux/commit/c4b6014e8bb0c8d47fe5c71ebc604f31091e5d3f
tools: Add copy of perf_event.h to tools/include/linux/
Signed-off-by: Martin Jansa
---
meta/reci
:131:2: ERROR: Problem encountered: No TLS backends enabled.
Please enable at least one TLS backend
* add an option to replace gnutls with openssl
Signed-off-by: Martin Jansa
---
meta/recipes-core/glib-networking/glib-networking_2.60.1.bb | 1 +
1 file changed, 1 insertion(+)
diff --g
Can we restore meta/files/common-licenses/Elfutils-Exception in oe-core to
be used by meta-gplv2 version:
recipes-devtools/elfutils/elfutils_0.148.bb:LICENSE = "(GPL-2+ &
Elfutils-Exception)"
causing:
do_rootfs: The license listed Elfutils-Exception was not in the licenses
collected for recipe elf
On Fri, May 10, 2019 at 11:54 PM Martin Jansa
wrote:
> * gnutls from meta-gplv2 isn't new enough for this version of
> glib-networking:
> meson.build:74:0: ERROR: Invalid version of dependency, need 'gnutls'
> ['>= 3.4.6'] found '3.3.30&
le or directory
WARNING: exit code 1 from a shell command.
* tools/include/uapi was added in kernel 4.8 with
https://github.com/torvalds/linux/commit/c4b6014e8bb0c8d47fe5c71ebc604f31091e5d3f
tools: Add copy of perf_event.h to tools/include/linux/
Signed-off-by: Martin Jansa
---
meta/reci
I'm sorry, will need v3.
install: target
'lib32-perf/1.0-r9/perf-1.0/tools/include/uapi/asm-generic/unistd.h' is not
a directory
On Sat, May 11, 2019 at 6:36 PM Martin Jansa wrote:
> * before trying to copy unistd.h into it
>
> * older kernels don't have uapi in t
le or directory
WARNING: exit code 1 from a shell command.
* tools/include/uapi was added in kernel 4.8 with
https://github.com/torvalds/linux/commit/c4b6014e8bb0c8d47fe5c71ebc604f31091e5d3f
tools: Add copy of perf_event.h to tools/include/linux/
Signed-off-by: Martin Jansa
---
meta/reci
* to make it easier to rebase
Signed-off-by: Martin Jansa
---
...owerpc-change-the-memory-size-limit.patch} | 12 ++---
...purgatory-Pass-r-directly-to-linker.patch} | 13 ++---
...ix-add_buffer_phys_virt-align-issue.patch} | 7 +--
...t-to-build-kexec-tools-with-x32-ABI.patch} | 47
le or directory
WARNING: exit code 1 from a shell command.
* tools/include/uapi was added in kernel 4.8 with
https://github.com/torvalds/linux/commit/c4b6014e8bb0c8d47fe5c71ebc604f31091e5d3f
tools: Add copy of perf_event.h to tools/include/linux/
Signed-off-by: Martin Jansa
---
meta/reci
to change the default, because my only motivation was the
license issue with the newer gnutls, with the PACKAGECONFIG available
it's easy to change the TLS backend and that's all I need.
Will send v2 if there is some consensus from glib-networking users that
it should be changed and som
:131:2: ERROR: Problem encountered: No TLS backends enabled.
Please enable at least one TLS backend
* add an option to replace gnutls with openssl
Signed-off-by: Martin Jansa
---
meta/recipes-core/glib-networking/glib-networking_2.60.1.bb | 1 +
1 file changed, 1 insertion(+)
diff --g
#x27;${PN}-ptest', '',
d)} ${PN}-src ${PN}-dbg ${PN}-staticdev ${PN}-dev ${PN}-doc ${PN}-locale
${PACKAGE_BEFORE_PN} ${PN}"
PACKAGES="libopkg opkg-ptest opkg-src opkg-dbg opkg-staticdev opkg-dev
opkg-doc opkg-locale opkg"
The easiest fix should be to reor
#x27;${PN}-ptest', '',
d)} ${PN}-src ${PN}-dbg ${PN}-staticdev ${PN}-dev ${PN}-doc ${PN}-locale
${PACKAGE_BEFORE_PN} ${PN}"
PACKAGES="libopkg opkg-ptest opkg-src opkg-dbg opkg-staticdev opkg-dev
opkg-doc opkg-locale opkg"
The easiest fix should be to reor
Hi,
there is small issue with this in cases where OPKGLIBDIR is set to /usr/lib.
Then all ptest files get packaged in libopkg instead of opkg-ptest and
correct QA error is triggered:
ERROR: QA Issue: /usr/lib/opkg/ptest/tests/opkgcl.py contained in package
libopkg requires /usr/bin/python3, but n
On Thu, Apr 25, 2019 at 04:21:22PM +0100, Burton, Ross wrote:
> Sadly this breaks subversion target builds:
>
> checking for linking Python libraries...
> checking for apr_int64_t Python/C API format string...
> configure: error: failed to recognize APR_INT64_T_FMT on this platform
I had recently
b2e2a00071c69e1afbb672889e754ee
Variable MACHINE value changed from 'qemux86copy' to 'qemux86'
Signed-off-by: Martin Jansa
---
meta/classes/icecc.bbclass | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/classes/icecc.bbclass b/meta/classes/icecc.bbclass
index 6d00
On Thu, Mar 28, 2019 at 10:21:39AM +, Martin Jansa wrote:
> * Work around broken ld-2.29.so when gold is used
> causing qemu-arm to segfault during e.g. gobject-introspection
> or postinst at do_rootfs time, more details in:
>
> http://lists.openembedded.org/pipermail/ope
Would it make sense to at least as temporary work around add a flag saying
that git-lfs does or doesn't exist in HOSTTOOLS after it being added
to HOSTTOOLS_NONFATAL and then let those few recipes which already use
git-lfs to check this flag and fail early with meaningful error message
about git-lf
It's not caused by this change (not the previous one I believe), but today
I've noticed that aarch64 tunes don't set TUNE_PKGARCH correctly.
e.g. with raspberrypi3-64 which since this commit:
https://github.com/agherzan/meta-raspberrypi/commit/9cc89cb7341d633b6fc3a92b937b5560d26257a1
uses conf/mac
/build/luneos-master/webos-ports/meta-openembedded/meta-networking/recipes-protocols/xl2tpd/xl2tpd_git.bb.do_packagedata
with hashes 6312d5711b5c2c1a85ee235d09bf37a8ec00f7ad9e7248c087bb83ef1d5bd078
or c0d3ef52b37bda945d8b2a015980ddb8fe7b4b3dca3d82d71a84176cc5125142
Signed-off-by: Martin Jansa
sroots/x86_64-linux/usr/bin/dd
bs=4096 count=1
+ grep '^# Generated by .*libtool'
++ notinst_deplibs=
...
func_ltwrapper_script_p, calls lt_truncate_bin and pipes the result to
func_generated_by_libtool_p, but with non-existent path to dd this fails
and libtool installs
Please don't forget to include:
http://lists.openembedded.org/pipermail/openembedded-core/2019-March/280094.html
and similar one for sumo:
http://lists.openembedded.org/pipermail/openembedded-core/2019-March/280093.html
in the next pull.
I don't see them included in any thud-next/thud-nmut branche
On Fri, Apr 05, 2019 at 09:28:35PM +0200, Andreas Müller wrote:
> gobject-introspection is mandatory for gstreamer1.0-python - there is no
> configure option to enable or disable it.
>
> To handle properly, this patch does:
>
> * Make 'gobject-introspection-data' a required distro feature
> * Add
Hello,
since this change:
cmake.bbclass: Make it work with ccache
https://patchwork.openembedded.org/patch/157226/
the allarch recipes are no longer allarch, because they contain arch
specific CC and CXX (OECMAKE_C_COMPILER, OECMAKE_CXX_COMPILER variables).
e.g. one example where I've initially
RPROVIDES/RREPLACES/RCONFLICTS is the right combo (you need all 3 for opkg
to remove the old package IIRC).
On Tue, Apr 2, 2019 at 6:29 PM Mark Hatle wrote:
> On 4/2/19 9:15 AM, Paul Barker wrote:
> > tzdata is converted to an empty meta package which pulls in all
> > subpackages. The subpackage
Any update on this one? Or should we downgrade it on our side when bumping
oe-core/thud revision?
On Sun, Mar 24, 2019 at 7:48 PM Martin Jansa wrote:
> On Sun, Mar 24, 2019 at 11:45:08AM -0700, akuster808 wrote:
> >
> >
> > On 3/24/19 11:01 AM, Martin Jansa wrote:
> >
On Wed, Mar 27, 2019 at 10:08:32PM -0700, Khem Raj wrote:
> On Wed, Mar 27, 2019 at 3:32 PM Martin Jansa wrote:
> >
> > On Wed, Mar 27, 2019 at 09:39:07PM +0100, Martin Jansa wrote:
> > > On Wed, Mar 27, 2019 at 05:35:07PM +0100, Martin Jansa wrote:
> > > >
?id=24148
https://sourceware.org/bugzilla/show_bug.cgi?id=10937
https://sourceware.org/bugzilla/show_bug.cgi?id=18103
Signed-off-by: Martin Jansa
---
meta/recipes-core/glibc/glibc_2.29.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-core/glibc/glibc_2.29.bb
On Wed, Mar 27, 2019 at 09:39:07PM +0100, Martin Jansa wrote:
> On Wed, Mar 27, 2019 at 05:35:07PM +0100, Martin Jansa wrote:
> > On Wed, Mar 27, 2019 at 05:17:54PM +0100, Martin Jansa wrote:
> > > On Sun, Mar 17, 2019 at 08:26:37AM -0700, Khem Raj wrote:
> > > > ht
On Wed, Mar 27, 2019 at 03:09:21PM +0100, Alexander Kanavin wrote:
> Also, update PV to match the version scheme used by upstream
> to tag releases (e.g. major.minor.patch).
>
> Signed-off-by: Alexander Kanavin
> ---
> meta/recipes-devtools/llvm/llvm_git.bb | 8 ++--
> 1 file changed, 2 inse
On Wed, Mar 27, 2019 at 04:03:27PM +0200, Adrian Bunk wrote:
> On Wed, Mar 27, 2019 at 02:33:14PM +0100, Martin Jansa wrote:
> > On Tue, Mar 26, 2019 at 12:42:12PM +0200, Adrian Bunk wrote:
> >...
> > > Not having the release there also loses the ability to use either
On Tue, Mar 26, 2019 at 12:42:12PM +0200, Adrian Bunk wrote:
> On Tue, Mar 26, 2019 at 11:20:17AM +0100, Martin Jansa wrote:
> > On Tue, Mar 26, 2019 at 10:00:52AM +, Burton, Ross wrote:
> > > On Tue, 26 Mar 2019 at 01:39, Khem Raj wrote:
> > > > > This
On Tue, Mar 26, 2019 at 10:32:07AM +, Burton, Ross wrote:
> On Tue, 26 Mar 2019 at 10:20, Martin Jansa wrote:
> > http fetcher won't (usually) fetch different version just by changing 1
> > variable inside the recipe and vice versa, renaming the recipe won't
> &
On Tue, Mar 26, 2019 at 10:00:52AM +, Burton, Ross wrote:
> On Tue, 26 Mar 2019 at 01:39, Khem Raj wrote:
> > > This isn't a git snapshot recipe but a release that is fetched over it.
> > > For
> > > clarity, put the PV in the filename.
> >
> > I think its better to keep it as it is. since i
On Sun, Mar 24, 2019 at 11:45:08AM -0700, akuster808 wrote:
>
>
> On 3/24/19 11:01 AM, Martin Jansa wrote:
> > On Tue, Mar 19, 2019 at 07:52:06AM +, mikko.rap...@bmw.de wrote:
> >> On Mon, Mar 18, 2019 at 06:03:05PM +0100, Andreas Müller wrote:
> >>> O
On Tue, Mar 19, 2019 at 07:52:06AM +, mikko.rap...@bmw.de wrote:
> On Mon, Mar 18, 2019 at 06:03:05PM +0100, Andreas Müller wrote:
> > On Mon, Mar 18, 2019 at 5:45 PM Armin Kuster wrote:
> > >
> > > This reverts commit a384248938ea9db096866bf4ec8678d35ca62a12.
> > >
> > > This package update s
On Wed, Mar 20, 2019 at 05:39:28PM +0800, Jiang Lu wrote:
> Enable glib-networking build as a native package, for it is depended
> by libsoup.
>
> Signed-off-by: Jiang Lu
> ---
> .../glib-networking/glib-networking_2.58.0.bb| 9 +
> 1 file changed, 9 insertions(+)
>
> diff -
sume
that nobody needs openssl10 just because oe-core recipes can already
build without it).
Cheers,
> > On 19 Mar 2019, at 14.55, Martin Jansa wrote:
> >
> >> On Tue, Mar 19, 2019 at 12:35:59PM +0100, Alexander Kanavin wrote:
> >> Just to remind once more, all upstre
On Tue, Mar 19, 2019 at 12:35:59PM +0100, Alexander Kanavin wrote:
> Just to remind once more, all upstream support for OpenSSL 1.0.2 ceases in 9
> months, so shipping products with it may not be the best idea.
Just to remind once more, shipping products isn't as easy as building
the few recipes
On Tue, Mar 19, 2019 at 11:22:11AM +0100, Alexander Kanavin wrote:
> The commit you refer to changes the dependency from 1.1.0 to 1.1.1, so
> ca-certificates currently in thud already needs 1.1.
>
> Alex
>
> > On 19 Mar 2019, at 9.55, Martin Jansa wrote:
> >
> &g
On Mon, Mar 18, 2019 at 07:36:29PM -0700, Armin Kuster wrote:
> Responses should be made by Wed March 20th 22:00:00 UTC 2019
>
> The following changes since commit f5a57e939e626a5b7c6de5b51799ca602ed355ed:
>
> mesa: ship /etc/drirc in mesa-megadriver (2019-03-05 22:24:13 +)
>
> are availab
Just FYI:
This won't work if someone uses only openssl10 in the image (a bit
difficult to do with current master, but still some people have to do it),
in case someone needs it as well, here is how Gentoo makes ca-certificate
backwards compatible with old openssl:
https://github.com/gentoo/gentoo/
On Mon, Mar 18, 2019 at 11:21:53AM -0400, Mark Asselstine wrote:
> Per https://github.com/golang/go/wiki/GoArm we need to set GOARM when
> cross building for ARMv5, ARMv6 and ARMv7. The current approach of
> using TUNE_FEATURES can be error prone, as we can see today when
> attempting to build for
Signed-off-by: Martin Jansa
---
.../busybox/busybox/CVE-2011-5325-fix.patch | 393 ++
meta/recipes-core/busybox/busybox_1.27.2.bb | 1 +
2 files changed, 394 insertions(+)
create mode 100644 meta/recipes-core/busybox/busybox/CVE-2011-5325-fix.patch
diff --git a/meta
Signed-off-by: Martin Jansa
---
.../grub/files/fix.build.with.squashfs.patch | 24 +++
meta/recipes-bsp/grub/grub2.inc | 1 +
2 files changed, 25 insertions(+)
create mode 100644 meta/recipes-bsp/grub/files/fix.build.with.squashfs.patch
diff --git a/meta/recipes
Interesting side-effect of this is that mesa package used to ship empty
/etc directory before, now it's empty and not created.
So be aware that if you had image/packagegroup installing mesa package for
whatever reason (by mistake most likely), you'll need to adjust that in
thud.
On Tue, Feb 26, 2
Why not use STAGING_INCDIR ?
On Fri, Mar 8, 2019 at 7:36 AM wrote:
> From: Bruce Ashfield
>
> During the build for some architectures, perf generates a program
> which executes on the host to dump the syscall table.
>
> The generation of that program uses the cross compiler + sysroot
> to expan
4TB of sstate is just for few weeks for me :).
On Mon, Mar 4, 2019 at 11:45 AM Burton, Ross wrote:
> On Mon, 4 Mar 2019 at 10:27, Martin Jansa wrote:
> > There is, you can prune outdated duplicate sstate archives while still
> separately building multiple DISTRO_VERSIONs.
>
>
There is, you can prune outdated duplicate sstate archives while still
separately building multiple DISTRO_VERSIONs.
On Mon, Mar 4, 2019 at 11:17 AM Burton, Ross wrote:
> On Sun, 3 Mar 2019 at 22:52, Tom Rini wrote:
> > SSTATE_DIR =
> "${HOME}/work/OE/sstate-cache-${DISTRO_VERSION}${TARGET_VEND
Fri Feb 1 10:07:20 2019 +0200
>
> vim: Enable GUI support for x11 DISTRO_FEATURES
This isn't the latest vim commit in meta-oe, you're missing:
commit c4db3971ab88dc8c012256e987f73ccd4459b400 (HEAD -> jansa/master,
contrib/jansa/master)
Author: Martin Jansa
Date: Fri
On Wed, Feb 27, 2019 at 10:07:25AM -0800, Khem Raj wrote:
> Signed-off-by: Khem Raj
> ---
> v2: Add checksums and fix version
Something probably doesn't get rebuilt properly, I've noticed one
failure in incremental build after applying this:
ERROR: libvpx-1.7.0-r0 do_compile: Function failed: do
901 - 1000 of 5760 matches
Mail list logo
