* drop PR
* add +git to PV
* and support for native and nativesdk needed for spice
* the old PACKAGECONFIG didn't work, because both options aren't
recognized as shown by do_configure warning:
configure: WARNING: unrecognized options: --without-ogg, --disable-oggtest
* XIPH_PATH_OGG macro is provided by libogg so we cannot call it without
the libogg dependency, so replace it with explicit --enable-tools
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Armin Kuster <akuster808@gmail.com>
* can be used by qemu to redirect usb devices from virt-manager to qemu
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Armin Kuster <akuster808@gmail.com>
* 0.13.0 is needed for opengl support, see qemu commit:
https://git.qemu.org/?p=qemu.git;a=commitdiff;h=474114b7305cc1be7c2ee8ba5267be159a9d56e3
+# if SPICE_SERVER_VERSION >= 0x000d00 /* release 0.13.0 */
+# define HAVE_SPICE_GL 1
otherwise trying to run qemu with -spice gl=on fails with:
qemu-system-x86_64: -spice gl=on: Invalid parameter 'gl'
* spice-protocol is built separately since 0.12.6
* spice-protocol submodule has been removed,, spice-protocol must now
be installed when building spice-server
* celt051 is optional since 0.12.5, use PACKAGECONFIG for it
* Added Opus support. Celt support will be obsoleted in a future release.
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Armin Kuster <akuster808@gmail.com>
* drop PR
* add +git to PV
* drop python-pyparsing dependency, because python-pyparsing is in
meta-python
* replace dependency on python-pyparsing with python-pyparsing-native
which is used to generate client/generated_marshallers.cpp
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Armin Kuster <akuster808@gmail.com>
WARNING: android-tools-5.1.1.r37-r0 do_patch:
Some of the context lines in patches were ignored. This can lead to incorrectly applied patches.
The context lines in the patches can be updated with devtool:
devtool modify <recipe>
devtool finish --force-patch-refresh <recipe> <layer_path>
Then the updated patches and the source tree (in devtool's workspace)
should be reviewed to make sure the patches apply in the correct place
and don't introduce duplicate lines (which can, and does happen
when some of the context is ignored). Further information:
http://lists.openembedded.org/pipermail/openembedded-core/2018-March/148675.htmlhttps://bugzilla.yoctoproject.org/show_bug.cgi?id=10450
Details:
Applying patch preserve-ownership.patch
patching file system/extras/ext4_utils/make_ext4fs_main.c
Hunk #1 succeeded at 47 with fuzz 2 (offset -2 lines).
Hunk #2 succeeded at 81 (offset -2 lines).
Hunk #3 succeeded at 144 (offset -2 lines).
patching file system/extras/ext4_utils/make_ext4fs.c
Now at patch preserve-ownership.patch
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Armin Kuster <akuster808@gmail.com>
* the inherit was controlled by VIRTUAL-RUNTIME_init_manager and the installation
of .service files by DISTRO_FEATURES and systemd was in DISTRO_FEATURES but not
in VIRTUAL-RUNTIME_init_manager it was causing QA issues about unpackaged
.service files
ERROR: rarpd-ss981107-r0 do_package: QA Issue: rarpd: Files/directories
were installed but not shipped in any package:
/lib
/lib/systemd
/lib/systemd/system
/lib/systemd/system/rarpd.service
ERROR: sblim-sfcb-1.4.9-r0 do_package: QA Issue: sblim-sfcb:
Files/directories were installed but not shipped in any package:
/lib
/lib/systemd
/lib/systemd/system
/lib/systemd/system/sblim-sfcb.service
ERROR: sblim-sfcb-1.4.9-r0 do_package: QA Issue: sblim-sfcb:
Files/directories were installed but not shipped in any package:
/lib
/lib/systemd
/lib/systemd/system
/lib/systemd/system/sblim-sfcb.service
* systemd.bbclass will take care of removing /lib/systemd when systemd
isn't in DISTRO_FEATURES, so we can remove both conditions
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Armin Kuster <akuster808@gmail.com>
WARNING: ntp-4.2.8p10-r0 do_patch:
Some of the context lines in patches were ignored. This can lead to incorrectly applied patches.
The context lines in the patches can be updated with devtool:
devtool modify <recipe>
devtool finish --force-patch-refresh <recipe> <layer_path>
Then the updated patches and the source tree (in devtool's workspace)
should be reviewed to make sure the patches apply in the correct place
and don't introduce duplicate lines (which can, and does happen
when some of the context is ignored). Further information:
http://lists.openembedded.org/pipermail/openembedded-core/2018-March/148675.htmlhttps://bugzilla.yoctoproject.org/show_bug.cgi?id=10450
Details:
Applying patch ntp-4.2.4_p6-nano.patch
patching file include/ntp_syscall.h
Hunk #1 succeeded at 10 with fuzz 2 (offset -4 lines).
Now at patch ntp-4.2.4_p6-nano.patch
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Armin Kuster <akuster808@gmail.com>
Signed-off-by: Joe MacDonald <joe_macdonald@mentor.com>
* TUNE_PKGARCH cannot RRECOMMEND MACHINE specific kernel-modules
* without virtual/kernel dependency (which isn't really build time
dependency) the QA check won't traverse the dependencies correctly
and shows following errors:
ERROR: QA Issue: freediameter rdepends on kernel-module-ipip, but it isn't a build dependency? [build-deps]
ERROR: QA Issue: freediameter rdepends on kernel-module-sctp, but it isn't a build dependency? [build-deps]
ERROR: QA Issue: freediameter rdepends on kernel-module-tipc, but it isn't a build dependency? [build-deps]
ERROR: QA Issue: freediameter rdepends on kernel-module-udp-tunnel, but it isn't a build dependency? [build-deps]
* also change kernel-module dependencies from RDEPENDS to RRECOMMENDS
because the kernel config might include these directly and then
freediameter shouldn't fail to install
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Armin Kuster <akuster808@gmail.com>
Signed-off-by: Joe MacDonald <joe_macdonald@mentor.com>
WARNING: tcpdump-4.9.2-r0 do_patch:
Some of the context lines in patches were ignored. This can lead to incorrectly applied patches.
The context lines in the patches can be updated with devtool:
devtool modify <recipe>
devtool finish --force-patch-refresh <recipe> <layer_path>
Then the updated patches and the source tree (in devtool's workspace)
should be reviewed to make sure the patches apply in the correct place
and don't introduce duplicate lines (which can, and does happen
when some of the context is ignored). Further information:
http://lists.openembedded.org/pipermail/openembedded-core/2018-March/148675.htmlhttps://bugzilla.yoctoproject.org/show_bug.cgi?id=10450
Details:
Applying patch unnecessary-to-check-libpcap.patch
patching file configure.in
Hunk #1 succeeded at 418 with fuzz 2 (offset -149 lines).
Now at patch unnecessary-to-check-libpcap.patch
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Armin Kuster <akuster808@gmail.com>
Signed-off-by: Joe MacDonald <joe_macdonald@mentor.com>
* remove gobject-introspection-native dependency which is added by the
bbclass
* fixes:
TOPDIR/tmpfs/work/armv5te-oe-linux-gnueabi/geoclue/2.4.4-r0/recipe-sysroot/usr/bin/g-ir-scanner-lddwrapper: 2: TOPDIR/tmpfs/work/armv5te-oe-linux-gnueabi/geoclue/2.4.4-r0/recipe-sysroot/usr/bin/g-ir-scanner-lddwrapper: prelink-rtld: not found
TOPDIR/tmpfs/work/armv5te-oe-linux-gnueabi/geoclue/2.4.4-r0/recipe-sysroot/usr/bin/g-ir-scanner-qemuwrapper: 6: TOPDIR/tmpfs/work/armv5te-oe-linux-gnueabi/geoclue/2.4.4-r0/recipe-sysroot/usr/bin/g-ir-scanner-qemuwrapper: qemu-arm: not found
If the above error message is about missing .so libraries, then setting up GIR_EXTRA_LIBS_PATH in the recipe should help.
(typically like this: GIR_EXTRA_LIBS_PATH="${B}/something/.libs" )
reported by world builds since:
http://logs.nslu2-linux.org/buildlogs/oe/world/sumo/log.report.20180311_083331.loghttp://errors.yoctoproject.org/Errors/Details/170607/
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Armin Kuster <akuster808@gmail.com>
WARNING: pidgin-2.12.0-r0 do_patch:
Some of the context lines in patches were ignored. This can lead to
incorrectly applied patches.
The context lines in the patches can be updated with devtool:
devtool modify <recipe>
devtool finish --force-patch-refresh <recipe> <layer_path>
Then the updated patches and the source tree (in devtool's workspace)
should be reviewed to make sure the patches apply in the correct place
and don't introduce duplicate lines (which can, and does happen
when some of the context is ignored). Further information:
http://lists.openembedded.org/pipermail/openembedded-core/2018-March/148675.htmlhttps://bugzilla.yoctoproject.org/show_bug.cgi?id=10450
Details:
Applying patch sanitize-configure.ac.patch
patching file configure.ac
Hunk #1 succeeded at 642 with fuzz 1 (offset 170 lines).
Hunk #2 succeeded at 2397 (offset 537 lines).
Hunk #3 succeeded at 2429 (offset 537 lines).
Now at patch sanitize-configure.ac.patch
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Armin Kuster <akuster808@gmail.com>
WARNING: gperftools-2.6.1-r0 do_patch:
Some of the context lines in patches were ignored. This can lead to incorrectly applied patches.
The context lines in the patches can be updated with devtool:
devtool modify <recipe>
devtool finish --force-patch-refresh <recipe> <layer_path>
Then the updated patches and the source tree (in devtool's workspace)
should be reviewed to make sure the patches apply in the correct place
and don't introduce duplicate lines (which can, and does happen
when some of the context is ignored). Further information:
http://lists.openembedded.org/pipermail/openembedded-core/2018-March/148675.htmlhttps://bugzilla.yoctoproject.org/show_bug.cgi?id=10450
Details:
Applying patch 0001-Support-Atomic-ops-on-clang.patch
patching file src/base/atomicops.h
Hunk #1 succeeded at 124 with fuzz 2 (offset 6 lines).
Now at patch 0001-Support-Atomic-ops-on-clang.patch
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Armin Kuster <akuster808@gmail.com>
WARNING: glibmm-2.54.1-r0 do_patch:
Some of the context lines in patches were ignored. This can lead to incorrectly applied patches.
The context lines in the patches can be updated with devtool:
devtool modify <recipe>
devtool finish --force-patch-refresh <recipe> <layer_path>
Then the updated patches and the source tree (in devtool's workspace)
should be reviewed to make sure the patches apply in the correct place
and don't introduce duplicate lines (which can, and does happen
when some of the context is ignored). Further information:
http://lists.openembedded.org/pipermail/openembedded-core/2018-March/148675.htmlhttps://bugzilla.yoctoproject.org/show_bug.cgi?id=10450
Details:
Applying patch remove-examples.patch
patching file Makefile.am
patching file configure.ac
Hunk #1 succeeded at 166 with fuzz 1 (offset 30 lines).
Now at patch remove-examples.patch
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Armin Kuster <akuster808@gmail.com>
* musl doesn't provide these
* I'm not using uim, but this is breaking signatures test in world builds
for many months and nobody seems to care
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Armin Kuster <akuster808@gmail.com>
* fixes: following errors in every world build:
ERROR: Nothing PROVIDES 'xrdp' (but meta-oe/recipes-support/xorg-xrdp/xorgxrdp_0.2.5.bb DEPENDS on or otherwise requires it)
xrdp was skipped: missing required distro feature 'x11' (not in DISTRO_FEATURES)
ERROR: Required build target 'meta-world-pkgdata' has no buildable providers.
Missing or unbuildable dependency chain was: ['meta-world-pkgdata', 'xorgxrdp', 'xrdp']
ERROR: Nothing PROVIDES 'virtual/libx11' (but meta-oe/recipes-support/xorg-xrdp/xorgxrdp_0.2.5.bb DEPENDS on or otherwise requires it)
libx11-diet PROVIDES virtual/libx11 but was skipped: missing required distro feature 'x11' (not in DISTRO_FEATURES)
libx11 PROVIDES virtual/libx11 but was skipped: missing required distro feature 'x11' (not in DISTRO_FEATURES)
ERROR: Required build target 'meta-world-pkgdata' has no buildable providers.
Missing or unbuildable dependency chain was: ['meta-world-pkgdata', 'xorgxrdp', 'virtual/libx11']
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Armin Kuster <akuster808@gmail.com>
* there is explicit dependency on libpam without respecting pam in DISTRO_FEATURES
so add the check to prevent people building it against broken libpam
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Armin Kuster <akuster808@gmail.com>
Signed-off-by: Joe MacDonald <joe_macdonald@mentor.com>
* fixes:
WARNING: zsh-5.3.1-r0 do_package: zsh: NOT adding alternative provide /bin/sh: /bin/zsh does not exist
* it was installing zsh into /usr/bin even when log.do_configure confirms correct path:
installation basename : zsh
binary install path : /bin
* no other files were moved:
$ find 5.3.1-r0.*/image
5.3.1-r0.new/image
5.3.1-r0.new/image/bin
5.3.1-r0.new/image/bin/zsh-5.3.1
5.3.1-r0.new/image/bin/zsh
5.3.1-r0.new/image/usr
5.3.1-r0.old/image
5.3.1-r0.old/image/usr
5.3.1-r0.old/image/usr/bin
5.3.1-r0.old/image/usr/bin/zsh-5.3.1
5.3.1-r0.old/image/usr/bin/zsh
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Armin Kuster <akuster808@gmail.com>
* fixes:
Making all in po
make[2]: Entering directory
`TOPDIR/BUILD/work/x86_64-linux/fontforge-native/20170731-r0/build/po'
msgfmt --check --output-file=ca.mo ../../git/po/ca.po
msgfmt --check --output-file=el.mo ../../git/po/el.po
msgfmt --check --output-file=es.mo ../../git/po/es.po
msgfmt --check --output-file=it.mo ../../git/po/it.po
/bin/bash: msgfmt: command not found
/bin/bash: msgfmt: command not found
/bin/bash: msgfmt: command not found
/bin/bash: msgfmt: command not found
make[2]: *** [ca.mo] Error 127
make[2]: *** Waiting for unfinished jobs....
make[2]: *** [el.mo] Error 127
make[2]: *** [es.mo] Error 127
make[2]: *** [it.mo] Error 127
make[2]: Leaving directory
`TOPDIR/BUILD/work/x86_64-linux/fontforge-native/20170731-r0/build/po'
* as Ross explained:
needs explicit dependency on gettext-native
native disables NLS so just has gettext-minimal-native in the depends
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Armin Kuster <akuster808@gmail.com>
* when android-tools were moved from meta-smartphone/meta-android to
meta-oe this part was overlooked and my jenkins jobs didn't detect
it because I was still including meta-android layer.
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* as PNBLACKLIST message says, these recipes are blacklisted for long
time and nobody showed any interest to fix them
* remove all unused .patch and .inc files as well
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Updates the mpv package to version 0.26.0.
The patch that was previously necessary related to OpenGL has been added upstream.
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* remove recipes which support only bluez4 and are blacklisted when
bluez5 is selected in DISTRO_FEATURES, if someone is still using
bluez4, then it can be restored in separate meta-bluez4 and
maintained by people using it.
* there are few recipes which support both bluez5 or bluez4 based on
selected DISTRO_FEATURES, these can stay in meta-oe repository, but
now people without bluez5 in DISTRO_FEATURES will need to add
meta-bluez4 layer to satisfy bluez4 dependency
meta-gnome/recipes-connectivity/obex/obexd_0.48.bb:DEPENDS += "${@bb.utils.contains('DISTRO_FEATURES','bluez5','bluez5','bluez4',d)}"
meta-gnome/recipes-gnome/gnome-bluetooth/gnome-bluetooth_3.18.2.bb: ${@bb.utils.contains('DISTRO_FEATURES','bluez5','bluez5','bluez4',d)} \
meta-oe/recipes-connectivity/obex/obex-data-server_0.4.6.bb:DEPENDS += "${@bb.utils.contains('DISTRO_FEATURES','bluez5','bluez5','bluez4',d)}"
meta-oe/recipes-connectivity/obex/openobex_1.7.2.bb:DEPENDS_append_class-target = " ${@bb.utils.contains('DISTRO_FEATURES','bluez5','bluez5','bluez4',d)}"
meta-oe/recipes-connectivity/packagegroups/packagegroup-tools-bluetooth.bb:RDEPENDS_bluez4 = " \
meta-oe/recipes-connectivity/packagegroups/packagegroup-tools-bluetooth.bb:# Install bluez4 tools or bluez5 tools depending on what is specified in the distro.
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* the binary and service name was renamed in 0.11.11
from fluent-bit to td-agent-bit, but unfortunately
SYSTEMD_SERVICE wasn't updated in the recipe with
the upgrade causing do_package failures as in:
http://errors.yoctoproject.org/Errors/Details/147040/
ERROR: SYSTEMD_SERVICE_fluentbit value fluent-bit.service does not exist
0.11.3-r0/image/
0.11.3-r0/image/etc
0.11.3-r0/image/etc/fluent-bit
0.11.3-r0/image/etc/fluent-bit/parsers.conf
0.11.3-r0/image/etc/fluent-bit/fluent-bit.conf
0.11.3-r0/image/lib
0.11.3-r0/image/lib/systemd
0.11.3-r0/image/lib/systemd/system
0.11.3-r0/image/lib/systemd/system/fluent-bit.service
0.11.3-r0/image/usr
0.11.3-r0/image/usr/bin
0.11.3-r0/image/usr/bin/fluent-bit
0.11.3-r0/image/usr/lib
0.11.3-r0/image/usr/lib/libfluent-bit.so
0.11.3-r0/image/usr/lib/pkgconfig
0.11.3-r0/image/usr/lib/pkgconfig/msgpack.pc
0.11.11-r0/image
0.11.11-r0/image/etc
0.11.11-r0/image/etc/td-agent-bit
0.11.11-r0/image/etc/td-agent-bit/parsers.conf
0.11.11-r0/image/etc/td-agent-bit/td-agent-bit.conf
0.11.11-r0/image/lib
0.11.11-r0/image/lib/systemd
0.11.11-r0/image/lib/systemd/system
0.11.11-r0/image/lib/systemd/system/td-agent-bit.service
0.11.11-r0/image/usr
0.11.11-r0/image/usr/bin
0.11.11-r0/image/usr/bin/td-agent-bit
0.11.11-r0/image/usr/lib
0.11.11-r0/image/usr/lib/libfluent-bit.so
0.11.11-r0/image/usr/lib/pkgconfig
0.11.11-r0/image/usr/lib/pkgconfig/msgpack.pc
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* based on discussion in pndeprecated thread:
https://patchwork.openembedded.org/patch/137573/
update the messages to warn possible users that the
recipe will be removed before the end of the next development
cycle (before Yocto 2.4 is released).
* updated with:
sed -i 's/^\(PNBLACKLIST.*".*\)"/\1 - the recipe will be removed on 2017-09-01 unless the issue is fixed"/g' `git grep PNBLACKLIST | sed 's/:.*//g' | sort -u | xargs`
* then noticed couple recipes being blacklisted only based on
DISTRO_FEATURES, so removed those:
meta-networking/recipes-support/lksctp-tools/lksctp-tools_1.0.17.bb
meta-oe/recipes-connectivity/bluez/bluez-hcidump_2.5.bb
meta-oe/recipes-connectivity/bluez/bluez4_4.101.bb
meta-oe/recipes-connectivity/bluez/gst-plugin-bluetooth_4.101.bb
meta-oe/recipes-navigation/foxtrotgps/foxtrotgps_1.1.1.bb
meta-oe/recipes-navigation/gypsy/gypsy.inc
meta-oe/recipes-navigation/navit/navit.inc
meta-oe/recipes-support/opensync/libsyncml_0.5.4.bb
* if it isn't fixed by this date, it's fair game to be removed
whenever someone gets around to i
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* fixes:
dlm-4.0.2: No GNU_HASH in the elf binary:
'/home/jenkins/oe/world/shr-core/tmp-glibc/work/armv5te-oe-linux-gnueabi/dlm/4.0.2-r0/packages-split/dlm/usr/lib/libdlmcontrol.so.3.1'
No GNU_HASH in the elf binary:
'/home/jenkins/oe/world/shr-core/tmp-glibc/work/armv5te-oe-linux-gnueabi/dlm/4.0.2-r0/packages-split/dlm/usr/sbin/dlm_tool'
No GNU_HASH in the elf binary:
'/home/jenkins/oe/world/shr-core/tmp-glibc/work/armv5te-oe-linux-gnueabi/dlm/4.0.2-r0/packages-split/dlm/usr/sbin/dlm_controld'
[ldflags]
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* as shown in the log.do_compile:
cc1: warning: include location "/usr/local/include" is unsafe for cross-compilation [-Wpoison-system-directories]
* it's caused by Makefile doing:
DEFAULT_LIBS=-L/usr/X11R6/lib -L/usr/local/lib -lX11 -lXtst
DEFAULT_INC=-I/usr/X11R6/include -I/usr/local/include
LIBS=$(shell pkg-config --libs x11 xtst 2> /dev/null || echo "$(DEFAULT_LIBS)")
INC=$(shell pkg-config --cflags x11 xtst 2> /dev/null || echo "$(DEFAULT_INC)")
which always uses the DEFAULT_* since RSS, because there was no
pkg-config in the recipe sysroot
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* fixes:
No GNU_HASH in the elf binary:
'/tmp/work/armv5te-oe-linux-gnueabi/pngcheck/2.3.0-r0/packages-split/pngcheck/usr/bin/pngcheck'
[ldflags]
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* I no longer use efl and don't plan to upgrade it to newer version
* someone else should step-up and start maintaining meta-efl
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* 5.1.14 fails with default linux-yocto version:
CC [M] qemux86-oe-linux/vboxguestdrivers/5.1.14-r0/vbox_module/vboxsf/lnkops.o
qemux86-oe-linux/vboxguestdrivers/5.1.14-r0/vbox_module/vboxsf/lnkops.c:93:23: error: 'generic_readlink' undeclared here (not in a function)
.readlink = generic_readlink,
^~~~~~~~~~~~~~~~
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* otherwise we get the failure from do_install with useless log:
DEBUG: Executing shell function do_install
install: cannot stat 'vboxsf.ko': No such file or directory
WARNING: exit code 1 from a shell command.
* instead of the real issue like 5.1.14 currently has with default linux-yocto
version:
CC [M] qemux86-oe-linux/vboxguestdrivers/5.1.14-r0/vbox_module/vboxsf/lnkops.o
qemux86-oe-linux/vboxguestdrivers/5.1.14-r0/vbox_module/vboxsf/lnkops.c:93:23: error: 'generic_readlink' undeclared here (not in a function)
.readlink = generic_readlink,
^~~~~~~~~~~~~~~~
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* calls openssl
* I haven't checked what it does with openssl call, maybe it should
be modified to get the data from target openssl not native
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Joe MacDonald <joe_macdonald@mentor.com>
* some recipes might use xxd
* with stricter host binaries available in PATH:
http://lists.openembedded.org/pipermail/openembedded-core/2017-March/133886.html
we cannot use xxd from host and it's not so common to add it into
HOSTTOOL_NONFATAL
* there is also smaller solution for xxd -i (which is what I need):
https://github.com/gregkh/xxdi
but after creating xxdi-native recipe for this I've discovered that
perl on my host as well as perlnative doesn't provide File::Slurp
used by this, so adding BBCLASSEXTEND here is easier solution
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* add dependency on libcap to fix:
android-tools/5.1.1.r37-r0/git/system/core/adb/adb.c:39:28: fatal error: sys/capability.h: No such file or directory
#include <sys/capability.h>
^
* add patch from buildroot to fix build with newer glibc and on
bit-endian systems
android-tools/5.1.1.r37-r0/git/system/core/adb/usb_linux_client.c:38:25: error: initializer element is not constant
#define cpu_to_le32(x) htole32(x)
^
* and also disable thumb to fix:
http://errors.yoctoproject.org/Errors/Details/133881/
* drop default apply=yes for the .patch files
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* this will fix mongodb build for x86
http://errors.yoctoproject.org/Errors/Details/90392/
which was failing because of missing --wiredtiger=off in qemux86 builds
* also we can drop DISABLE_STATIC, because now it's not leaking through
EXTRA_OECONF
* it will also resolve again autodetected dependencies on bluez, qt and
tcmalloc as shown in bitbake -e output:
env.gpsd-before:EXTRA_OESCONS=" sysroot=/OE/build/oe-core/tmp-glibc/sysroots/qemux86 libQgpsmm='false' debug='true' strip='false' chrpath='yes' systemd='true' "
env.gpsd-after:EXTRA_OESCONS=" sysroot=/OE/build/oe-core/tmp-glibc/sysroots/qemux86 libQgpsmm='false' debug='true' strip='false' chrpath='yes' systemd='true' bluez='true' qt='no' "
env.mongodb-before:EXTRA_OESCONS="--prefix=/OE/build/oe-core/tmp-glibc/work/i586-oe-linux/mongodb/3.3.0+gitAUTOINC+aacd231be0-r0/image/usr LIBPATH=/OE/build/oe-core/tmp-glibc/sysroots/qemux86/usr/lib LINKFLAGS='-Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed' \
CXXFLAGS='-O2 -pipe -g -feliminate-unused-debug-types -fdebug-prefix-map=/OE/build/oe-core/tmp-glibc/work/i586-oe-linux/mongodb/3.3.0+gitAUTOINC+aacd231be0-r0=/usr/src/debug/mongodb/3.3.0+gitAUTOINC+aacd231be0-r0 -fdebug-prefix-map=/OE/build/oe-core/tmp-glibc/sysroots/x86_64-linux= -fdebug-prefix-map=/OE/build/oe-core/tmp-glibc/sysroots/qemux86= -fvisibility-inlines-hidden' \
TARGET_ARCH=i586 --ssl --disable-warnings-as-errors --use-system-pcre --use-system-zlib --js-engine=none --nostrip mongod mongos"
env.mongodb-after:EXTRA_OESCONS="--prefix=/OE/build/oe-core/tmp-glibc/work/i586-oe-linux/mongodb/3.3.0+gitAUTOINC+aacd231be0-r0/image/usr LIBPATH=/OE/build/oe-core/tmp-glibc/sysroots/qemux86/usr/lib LINKFLAGS='-Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed' \
CXXFLAGS='-O2 -pipe -g -feliminate-unused-debug-types -fdebug-prefix-map=/OE/build/oe-core/tmp-glibc/work/i586-oe-linux/mongodb/3.3.0+gitAUTOINC+aacd231be0-r0=/usr/src/debug/mongodb/3.3.0+gitAUTOINC+aacd231be0-r0 -fdebug-prefix-map=/OE/build/oe-core/tmp-glibc/sysroots/x86_64-linux= -fdebug-prefix-map=/OE/build/oe-core/tmp-glibc/sysroots/qemux86= -fvisibility-inlines-hidden' \
TARGET_ARCH=i586 --ssl --disable-warnings-as-errors --use-system-pcre --use-system-zlib --js-engine=none --nostrip --use-system-tcmalloc --wiredtiger=off mongod mongos"
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* fixes autodetected dependencies
http://logs.nslu2-linux.org/buildlogs/oe/world/log.report.20160905_011801.log
chrony-2.4: chronyc rdepends on nss, but it isn't a build dependency, missing nss in DEPENDS or PACKAGECONFIG? [build-deps]
chrony-2.4: chrony rdepends on libcap, but it isn't a build dependency, missing libcap in DEPENDS or PACKAGECONFIG? [build-deps]
chrony-2.4: chrony rdepends on nss, but it isn't a build dependency, missing nss in DEPENDS or PACKAGECONFIG? [build-deps]
* also use PACKAGECONFIG_CONFARGS instead of EXTRA_OECONF in do_configure
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* otherwise jack is autodetected:
mpv-0.15.0: mpv rdepends on libjack, but it isn't a build dependency, missing jack in DEPENDS or PACKAGECONFIG? [build-deps]
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* autodetected as reported in bitbake world status e-mails:
libgit2-0.24.1: libgit2 rdepends on libssh2, but it isn't a build dependency, missing libssh2 in DEPENDS or PACKAGECONFIG? [build-deps]
* log.do_package:
DEBUG: libgit2: Dependency libssh2.so.1 requires package libssh2 (used by files: /OE/build/oe-core/tmp-glibc/work/i586-oe-linux/libgit2/0.24.1-r0/packages-split/libgit2/usr/lib/libgit2.so.0.24.0)
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* autodetected for smsd as reported in bitbake world status e-mails:
gammu-1.32.0: libgsmsd rdepends on unixodbc, but it isn't a build dependency, missing unixodbc in DEPENDS or PACKAGECONFIG? [build-deps]
* log.do_package:
DEBUG: libgsmsd: Dependency libodbc.so.2 requires package unixodbc (used by files: /OE/build/oe-core/tmp-glibc/work/i586-oe-linux/gammu/1.32.0-r0/packages-split/libgsmsd/usr/lib/libgsmsd.so.7.1.32.0)
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* fixed 3 autodetected dependencies:
WARN: jasper: jasper-bin rdepends on freeglut, but it isn't a build dependency?
WARN: jasper: jasper-bin rdepends on libgl-mesa, but it isn't a build dependency?
WARN: jasper: jasper-bin rdepends on libglu, but it isn't a build dependency?
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Martin Jansa