From: Anatol Belski <anbelski@microsoft.com>
The libctmalloc-minimal is what is useful for C++ apps if only the
improved allocator is needed. The gperftools package stays otherwise
fully backward compatible as it's going to depend on libtcmalloc-minimal.
The libtcmalloc-minimal can be installed separately, which allows for
more flexibility and for cleaner image contents.
The discussion on the patch
https://patchwork.openembedded.org/patch/163234/ has shown, that a
separate package for other libs might have less sense in this case, so
it's not done. The patch 163234 can be abandoned in favor of this for
now.
Signed-off-by: Anatol Belski <anbelski@microsoft.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
OE use 'lib' even on x86_64 when building with multilib support disabled
and used 'lib64' with multilib
This fixes packaging errors e.g.
pmdk-1.6: pmdk: Files/directories were installed but not shipped in any package:
/usr/lib64/libpmem.so.1.0.0
/usr/lib64/libpmemblk.so.1.0.0
/usr/lib64/libpmemlog.so.1.0.0
/usr/lib64/libpmemobj.so.1.0.0
/usr/lib64/libvmem.so.1.0.0
....
Signed-off-by: Khem Raj <raj.khem@gmail.com>
After autoconf-archive was upgraded to 2019.01.06 it started to add
extra warning flags via WARN_CFLAGS along with -Werror which means that
now compiler could be stricter and break the build if any of the new
warnings are flagged
The difference is
old
WARN_CFLAGS='-fno-strict-aliasing -Wimplicit-function-declaration -Wold-style-definition -Wjump-misses-init -Werror -Wno-suggest-attribute=format -Wunused-parameter -Wmissing-field-initializers'
new
WARN_CFLAGS='-fno-strict-aliasing -Wimplicit-function-declaration -Wold-style-definition -Wjump-misses-init -Wall -Wextra -Wundef -Wwrite-strings -Wpointer-arith -Wmissing-declarations -Wredundant-decls -Wno-unused-parameter -Wno-missing-field-initializers -Wformat=2 -Wcast-align -Wformat-nonliteral -Wformat-security -Wsign-compare -Wstrict-aliasing -Wshadow -Winline -Wpacked -Wmissing-format-attribute -Wmissing-noreturn -Winit-self -Wmissing-include-dirs -Wunused-but-set-variable -Warray-bounds -Wreturn-type -Wswitch-enum -Wswitch-default -Wduplicated-cond -Wduplicated-branches -Wlogical-op -Wrestrict -Wnull-dereference -Wdouble-promotion -pedantic -Wunused-parameter -Wmissing-field-initializers -Werror -Wno-suggest-attribute=format -Wunused-parameter -Wmissing-field-initializers'
Hence we started seing build failure like https://errors.yoctoproject.org/Errors/Details/252684/
This fix just turns off warnings-as-errors so build can still go on, if
we need to fix the warnings they still are present in log.do_compile
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Cc: Oleksandr Kravchuk <open.source@oleksandr-kravchuk.com>
Cc: Robert Yang <liezhi.yang@windriver.com>
* Licence-Update:
- Copyright years are updated to 2019
* Remove automake-foreign.patch as the logic included
in the new version
* Rebase 0002-Remove-pg-from-profile_CFLAGS.patch
to new version
Signed-off-by: Mingli Yu <mingli.yu@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
1) Use git repo instead of github archive tarball.
2) PMDK libraries can be installed in lib or lib64, depending on
host building system. If host has /usr/local/lib64, libraries will
be installed in lib64, otherwise they will be installed in lib.
PMDK is only for 64-bit system, so use LIB_PREFIX=lib64 to force
the install path to be lib64.
3) Use prefix instead of PREFIX to install.
4) Remove unneeded files in /usr/lib64/pmdk_debug.
5) Add "/usr/etc" and "/usr/share" to fix package QA issue.
6) Revise patches for version 1.6. Remove upstream accepted patches.
Signed-off-by: Yongxin Liu <yongxin.liu@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Lets remove it directly, since October would be a year after
EOL so waiting until then would make it quite stale
Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
There have been a couple of releases since we last upgraded, including
a number of additional features. Changelog is here:
https://github.com/npat-efault/picocom/releases
Also tweak SUMMARY - I don't think this has been 20k in a while; with
this upgrade the binary alone went from 60k to 70k.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
-Upgrade from protobuf_3.8.0.bb to protobuf_3.9.0.bb.
-protobuf/0001-Added-stubs-map_util.h-to-list-of-installed-headers.patch
Removed since this is included in 3.9.0.
Signed-off-by: Zang Ruochen <zangrc.fnst@cn.fujitsu.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
If the local.conf has set 'USE_NLS = "no"' the build of libbytesize
will fail with the following message:
| configure: error: in `/build/tmp/work/core2-64-poky-linux/libbytesize/2.0-r0/build':
| configure: error: gettext not found
| See `config.log' for more details
| NOTE: The following config.log files may provide further information.
| NOTE: /build/tmp/work/core2-64-poky-linux/libbytesize/2.0-r0/build/config.log
| ERROR: configure failed
The issue is that libbytesize needs to full version of gettext in
order to configure properly, and not the minimal version which is
provided by default when building with 'USE_NLS = "no"'.
Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
This is the GTK+ 2 Adwaita theme, which has just been removed from oe-core.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
This is GTK+ 2, which is obsolete. It has just been removed from oe-core, so
add it into meta-oe for any remaining users.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
The cryptsetup 2.1 uses LUKS2 format as the default LUKS format. This
change introduced the following issues:
* LUKS2 requires kernel userspace crypto API to be available
(CONFIG_CRYPTO_USER_API and CONFIG_CRYPTO_USER_API_SKCIPHER). But
linux-yocto doesn't enable these options by default. If missing these
kernel modules, the cryptsetup will fall back to using dmcrypt-device
for keyslot processing.
$ cryptsetup --debug --type luks luksFormat /dev/sda3
[snip]
Checking if cipher aes-xts-plain64 is usable.
Userspace crypto wrapper cannot use aes-xts-plain64 (-95).
Using dmcrypt to access keyslot area.
[snip]
* The grub can not decrypt a LUKS2 encrypted boot partition because it
doesn't support LUKS2 now.
See grub bug: https://savannah.gnu.org/bugs/?55093
Add a PACKAGCONFIG for luks format and set the default LUKS format to
LUKS1. The users can specify '--type luks2' in cryptsetup command line
if they want to use LUKS2.
Signed-off-by: Yi Zhao <yi.zhao@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Make sure that we call gpsd from /usr instead of /usr/local.
Signed-off-by: Alistair Francis <alistair@alistair23.me>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Update libvncserver to latest git commit 1354f7f which could help to fix
do_package error when multilib is enabled:
| Files/directories were installed but not shipped in any package:
| /usr/lib/libvncclient.so.0.9.12
| /usr/lib/libvncclient.so.1
| /usr/lib/libvncclient.so
| /usr/lib/libvncserver.so.0.9.12
| /usr/lib/libvncserver.so.1
| /usr/lib/libvncserver.so
| /usr/lib/pkgconfig
| /usr/lib/pkgconfig/libvncserver.pc
| /usr/lib/pkgconfig/libvncclient.pc
Rename recipe name from _git.bb to _${version}.bb as well.
Signed-off-by: Kai Kang <kai.kang@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Option '-std=gnu++14' has been supported from gcc 4.9. But on some build hosts
such as CentOS 7.6 which only has gcc 4.8.5 and fails to configure:
| checking whether the host C compiler can be used... no
| ERROR: Only GCC 4.9 or newer is supported (found version 4.8.5).
Fallback to 2011 C++ standard and lower required gcc version to 4.8.0 which is
the same as in previous version 52.9.1 of mozjs.
Signed-off-by: Kai Kang <kai.kang@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
