summaryrefslogtreecommitdiff
path: root/meta/conf/distro/include
AgeCommit message (Collapse)AuthorFiles
2016-06-23security_flags.inc: add SECURITY_NO_PIE_CFLAGS to libgcc and gcc-sanitizersAlexander Kanavin1
These recipes no longer seem to need full exclusion from security hardening. The rest (glibc, gcc-runtime, valgrind, grub, grub-efi, uclibc) still do. [YOCTO #9489] Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-06-15oprofileui: removeRoss Burton1
oprofileui doesn't work anymore with not-so-recent changes to the oprofile command line interface, and perf is becoming the expected profiling solution so any future profiling tools should be using that instead. Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-06-14gzip: upgrade to 1.8Richard Purdie1
Drop the do_install musl append since the charset file is no longer installed. Refresh the patch. Also update the PREFERRED_VERSION. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-06-03security_flags.inc: add an entry for python3-numpyAlexander Kanavin1
The entry is same as for python-numpy and prevents build failures when extra security flags are in use (e.g. in poky-lsb). Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-06-02python-imaging: remove unused recipeAlexander Kanavin2
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-06-02python-pyrex: remove unused recipeAlexander Kanavin1
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-06-01unzip: fix security issuesEdwin Plauchu1
This patch avoids unzip fails to compile with compiler flags which elevate common string formatting issues into an error (-Wformat -Wformat-security -Werror=format-security). [YOCTO #9551] Signed-off-by: Edwin Plauchu <edwin.plauchu.camacho@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-05-30default-versions.inc: drop python-related defaultsAlexander Kanavin1
There is only one version of python 2.x provided, so no need to set a preferred version. PYTHON_BASEVERSION is now set explicitly in python-dir.bbclass and python3-dir.bbclass, so fix up a few recipes that relied on it being set in default-versions.inc without inheriting python-dir. Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2016-05-25tcmode-default: Bump gccKhem Raj1
gcc 6.1 Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-05-19package_regex.inc: remove deprecated fileMaxin B. John1
Remove this file as it has been deprecated in the previous release. New entries should be added to recipes itself. Signed-off-by: Maxin B. John <maxin.john@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-05-19yocto-uninative: Update to 1.1 tarball (new version of glibc)Richard Purdie1
Since we have a new version of glibc, upgrade to a new version of the uninative tarball to ensure we work on recent distributions. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-05-19makedevs: fix security issuesEdwin Plauchu1
This avoids makedevs failure to compile with compiler flags which elevate common string formatting issues into an error (-Wformat -Wformat-security -Werror=format-security). [YOCTO #9549] Signed-off-by: Edwin Plauchu <edwin.plauchu.camacho@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-05-19zip: fix security issuesEdwin Plauchu1
This patch avoids zip recipe fails to compile with compiler flags which elevate common string formatting issues into an error (-Wformat -Wformat-security -Werror=format-security). [YOCTO #9552] Signed-off-by: Edwin Plauchu <edwin.plauchu.camacho@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-05-19stat: fix security issuesEdwin Plauchu1
This patch avoids stat fails to compile with compiler flags which elevate common string formatting issues into an error (-Wformat -Wformat-security -Werror=format-security). [YOCTO #9550] Signed-off-by: Edwin Plauchu <edwin.plauchu.camacho@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-05-15tcmode-default: Bump glibc,gdbKhem Raj1
glibc 2.24, gdb 7.11 Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-05-15security_flags: Enable security flags on leafpad, ltp and libuser.Aníbal Limón1
Now we have patches that solves the security formatting issues into those packages. Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-05-06security_flags: turn potential string format security issues into an errorJoshua Lock1
Add "-Wformat -Wformat-security -Werror=format-security" to the default SECURITY_CFLAGS to catch potential security vulnerabilities due to the misuse of various string formatting functions. These flags are widely used in distributions such as Fedora and Ubuntu, however we have 15 recipes in OE-Core which fail to build with these flags included and thus the flags are removed for: - busybox - console-tools - cmake - expect - gcc - gettext - kexec-tools - leafpad - libuser - ltp - makedevs - oh-puzzles - stat - unzip - zip [YOCTO #9488] Signed-off-by: Joshua Lock <joshua.g.lock@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-04-18default-providers.inc: set openssl PREFERRED_PROVIDER to opensslAndre McCurdy1
Although the oe-core openssl recipe is currently the only provider of openssl, make the preference for using it explicit in anticipation of a libressl recipe being added to meta-oe. Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-04-15default-providers: Update to use PREFERRED_RPROVIDERRichard Purdie1
Get rid of the very confusing PREFERRED_PROVIDER_bluez4 using the new/better PREFERRED_RPROVIDER syntax. [YOCTO #5044] Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-04-01default-distrovars.inc: remove libassuan from LGPLv2_WHITELIST_GPL-3.0Andre McCurdy1
The libassuan recipe is now buildable in distros which blacklist GPL-3.0 without needing to be explicitly whitelisted (since it provides at least one non GPLv3 package). Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-03-31base.bbclass: drop obsolete HOSTTOOLS_WHITELIST_GPL-3.0Andre McCurdy1
base.bbclass sets 'check_license' to False (and therefore skips license checking completely) for native, nativesdk, etc recipes (ie anything which could potentially be classed as "host tools"), so supporting a dedicated whitelist of GPLv3 host tools is not necessary. Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-03-30default-distrovars.inc: remove gnutls + libtasn1 from LGPLv2_WHITELIST_GPL-3.0Andre McCurdy1
With the modern license handling code, gnutls and libtasn1 are both buildable in distros which blacklist GPL-3.0 without needing to be explicitly whitelisted (since they both provide at least one non GPLv3 package). Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-03-30uninative: Switch md5sum -> sha256Richard Purdie1
There are various concerns about md5 so use sha256 instead. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-03-29no-static-libs.inc: build static libusb1-nativeMartin Jansa1
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-03-26make, remake: make them properly exclude each otherAlexander Kanavin1
Remake and make can't be installed at the same time as they're both installing a header file with the same name. Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-03-23no-static-libs: just like target and native, nativesk-libcap doesn't like ↵Ross Burton1
unrecognised options Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-03-20world-broken: Add packages broken on muslKhem Raj1
These 14 packages are failing aross all architectures on musl targets. Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-03-12musl: disable building of gobject introspection dataAlexander Kanavin1
When musl is in use, GLib binaries crash on assertion failures under qemu Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-03-12python-pygtk: remove the recipeAlexander Kanavin1
python-pygtk hasn't been updated in several years, is incompatible with the current version of pygobject, and is generally obsolete as all modern python gtk apps use introspection directly. Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-03-09security_flags.inc: Special flags are needed for RPMMark Hatle1
RPM interally has support to build and work with the stack protector. This is disabled by default in the RPM package, and the proper settings should be specified in the security_flags. Using the default setting of stack-protector-strong causes linking problems due to issues with libtool selecting the wrong GCC objections to link against. Falling back to the RPM values of stack-protector will permit linking to work properly, and some level of protection. Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
2016-03-07yocto-uninative: Add common include for uninativeRichard Purdie1
uninative has some specific setup requirements. Rather than have everyone doing this themselves, do this centrally and allow people to opt into it based on some Yocto Project builds of the uninative tarballs. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-03-02eudev: Replaces udev with eudev for compatibility when using sysvinit on ↵Alejandro Hernandez1
newer kernels udev has started to fail on new kernels (4.4), due to being deprecated in favor of systemd's udev implementation. To maintain a sysvinit alternative we also need to provide an alternative to udev. Eudev is a fork of systemds udev, this new eudev recipe provides upstream udev 220 funcitonality. - Removes patches that dont apply anymore - ToDo: eudev-ptest? [YOCTO #8998] Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-28adt-installer: Drop since its replaced by the extensible SDKRichard Purdie1
The extensible SDK replaces adt-installer so this can be removed now, all future effort in this direction will be placed onto that. This includes a layer version change so the autobuilder knows when to stop building adt-installer. [YOCTO #6404] Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-22security_flags: Disable ssp when compiling uclibcKhem Raj1
Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-21glibc: Upgrade to 2.23Khem Raj1
Drop kconfig and options-group support Forward port cross-localedef support Assume ssp support in libc when building gcc-initial Signed-off-by: Khem Raj <raj.khem@gmail.com>
2016-02-21no-static-libs: remove eglinfoRoss Burton1
waf.bbclass disables no-static-libs for all waf recipes, so we don't need to have it explicitly disabled here now. Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-18no-static-libs.inc: Add libcap-nativeRichard Purdie1
We need to disable static flags for libcap-native as well. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-16conf/no-static-libs: add explicit rule for libicalRoss Burton1
cmake doesn't have a standard for disabling static libraries so libical needs an explicit statement. Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-15security_flags: Add SECURITY_CFLAGS to TARGET_CC_ARCH for binutilsKhem Raj1
libtool decides to filter out -fstack-protector-strong on its own and its documented here https://www.gnu.org/software/libtool/manual/html_node/Stripped-link-flags.html this causes linking errors when linking libbfd.so since objects (.o) are compiled using -fstack-protector-strong so they are expecting to link with libssp but the option goes missing in linker flags. With this patch the security flags are hoisted upto CC itself and libtool thankfully does not touch CC. Adding to CC also means that we can now remove it from LDFLAGS since when gcc driver is used to do linking then we have LD = CC and this option makes to linker cmdline Since CC is used without CFLAGS in configure tests, some tests fail complaining that -Olevel is not used while using _FORTIFY_SOURCE therefore added SELECTED_OPTIMIZATION to TARGET_CC_ARCH as well Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-15conf/distro/include: Add no-static-libs.incRichard Purdie1
Static libraries are old technology. We've left them around since in previous tests, they only added around 5% to the overall build time. With new and interesting uses of OE, they're becoming more problematic. For example, sstate becomes much larger with static libs enabled which increases the size of eSDK and increases the time taken for sstate operations. Since the static libs contain all the debugging symbols, they're also pretty huge. This patch adds a common include file which allows the user or distro to disable the static libraries in the majority of cases. There are some libs where we do need the static lib, a good example being pseudo-native which uses sqlite3-native static libs. These are left enabled by the include file, as are recipes where --disable-static doesn't work, or isn't supported. This list can likely be reduced over time as individual corner cases are addressed. Maintaining this list in a common location is more desireable than everyone doing it themselves. Poky will switch to using this, OE-Core will need to discuss that as its default. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-07security_flags: wipe security flags for gcc/glibc and related librariesKhem Raj1
It causes a catch-22 situation where we build libssp in gcc-runtime but also pass -fstack-protector flags which require libssp Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-07security_flags: use -fstack-protector-strongKhem Raj1
This is a better version of -fstack-protector-all with reduced stack usage and better performance yet giving same amount of coverage. It's available in gcc 4.9 onwards. https://outflux.net/blog/archives/2014/01/27/fstack-protector-strong/ has more details. Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-07security_flags: ensure security flags only apply to target buildsKhem Raj1
As otherwise the security flags can leak into target builds. This can result in flags that the host compiler doesn't support, causing build failures. Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-07security_flags.inc: don't do -pie for syslinuxRoss Burton1
sysroots/x86_64-linux/usr/libexec/x86_64-poky-linux/gcc/x86_64-poky-linux/5.3.0/ld: syslinux.o: relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-06gtk-theme-torturer: remove from oe-coreRoss Burton1
This recipe is very old, unmaintained, not used at all in OE-Core, and not useful in a world that has moved to GTK+ 3 (even if Sato is slow at catching up). Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-01-31binutils: Upgrade to 2.26Khem Raj1
Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-29libc-package.bbclass: add LOCALE_UTF8_IS_DEFAULTRichard Tollerton1
python hard-codes the encoding of many locales; for instance, en_US is always assumed to be ISO-8859-1, regardless of the actual encoding of the en_US locale on the system. cf https://hg.python.org/cpython/file/7841e9b614eb/Lib/locale.py#l1049, getdefaultlocale(), etc. This code appears to date back to python 2.0. The source of this hard-coding is Xorg's locale.alias but is ultimately justified by glibc's SUPPORTED. This causes problems on OE, because any locale lacking an explicit encoding suffix (e.g. en_US) is UTF-8. It has been this way from the beginning (svn r1). That is not a bug, per se -- no specification prohibits this AFAIK. But it seems to be at odds with virtually every other glibc-based distribution in existence. To avoid needlessly aggravating hidden bugs that nobody else might hit, it makes sense to disable this behavior such that locales are named precisely as specified by SUPPORTED. I suppose that reasonable minds may disagree on whether or not the current behavior is prudent; at the very least, this is likely to break IMAGE_LINGUAS settings. So let's create a new distro variable LOCALE_UTF8_IS_DEFAULT to allow either behavior. Set it to 0 and all your locales get named exactly like they are in SUPPORTED. Leave it at 1 to preserve current OE locale naming conventions. Signed-off-by: Richard Tollerton <rich.tollerton@ni.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-01-22linux-libc-headers: update to 4.4Bruce Ashfield1
Updating the lib-headers to match the 4.4 LTSI kernel version. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-01-19python: Upgrade 2.7.9 > 2.7.11Alejandro Hernandez1
- no license change, just dates Rebased: - check-if-target-is-64b-not-host.patch - add-CROSSPYTHONPATH-for-PYTHON_FOR_BUILD.patch Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-19security_flags.inc: remove obsolete workarounds for curlAndre McCurdy1
The curl configure script contains sanity checks for unexpected options being passed via CFLAGS, LDFLAGS, etc. environment variables. These sanity checks catch -Dxxx options in CFLAGS, which clashes with OE's approach of using CFLAGS to pass -D_FORTIFY_SOURCE (curl's configure script suggests, quite correctly, that -Dxxx options should be passed via CPPFLAGS instead). These sanity checks previously generated fatal errors, but have been downgraded to warnings since curl v7.32. Therefore the workaround of avoiding -D_FORTIFY_SOURCE for curl is obsolete and can be removed. https://github.com/bagder/curl/commit/5d3cbde72ece7d83c280492957a26e26ab4e5cca Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
generated by cgit v1.2.3 (git 2.25.1) at 2025-04-20 10:55:02 +0000