summaryrefslogtreecommitdiff
path: root/meta/recipes-devtools
AgeCommit message (Collapse)AuthorFiles
2017-03-17gdb: don't bundle bfd.info -- leave that to binutils.Paul Gortmaker1
We see: file /usr/share/info/bfd.info conflicts between attempted installs of gdb-doc-7.12.1-r0.core2_64 and binutils-doc-2.28-r0.core2_64 You can't really have gdb and not binutils, so there is no need to do alternatives here ; just clobber the one from gdb and let the binutils one be the default. Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-03-17dnf: add /usr/bin/dnf symlink that points to /usr/bin/dnf-2Alexander Kanavin1
All documentation refers to dnf binary as 'dnf' yet make install does not create one - it's done by Fedora's spec file when building the rpm. Let's replicate this behavior. Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-03-16opkg-utils: Remove unused patchesJussi Kukkonen2
0001-update-alternatives-warn-when-multiple-providers-hav.patch was removed from SRC_URI without mention in commit 60c9a9704. 001-Makefile-use-defined-bindir-and-mandir-as-installati.patch was removed from SRC_URI in d6b04e121. Current opkg does not need either patch. Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-03-16gcc: Remove unused patchJussi Kukkonen1
CVE-2016-4490 applied to gcc < 6.1.1, our version is 6.3 Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-03-16python-native: Remove unused patchJussi Kukkonen1
avoid_parallel_make_races_on_pgen.patch was removed from SRC_URI as handled in upstream in db9508891b6. Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-03-16python: Remove unused patchesJussi Kukkonen2
CVE-2016-5636.patch and avoid_parallel_make_races_on_pgen.patch were removed from SRC_URI as handled upstream in adf4266524d0d. Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-03-16python3: Remove unused patchesJussi Kukkonen2
CVE-2016-5636.patch and use_packed_importlib.patch were removed from SRC_URI as handled in upstream in b192bc02bbf91. Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-03-16qemu: Remove uuid PACKAGECONFIGJussi Kukkonen1
--enable-uuid no longer exists: There's a uuid implementation in libqemuutil. Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-03-16python3-pip: support native buildsJuro Bystricky1
Add native pip3 support. [YOCTO#11049] [YOCTO#11022] Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-03-14go: add native recipes for 1.8Khem Raj4
Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-03-14go: Enable on muslKhem Raj2
Working fine for musl targets now Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-03-13run-postinsts: simplify the logic of whether to install it to imagesAlexander Kanavin2
The logic is scattered all over the place, but amounts to "install, unless the rootfs is read only". Let's express that directly. Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2017-03-13nativesdk-packagegroup-sdk-host: replace smartpm with dnfAlexander Kanavin8
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2017-03-13python-smartpm: remove the recipeAlexander Kanavin15
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2017-03-13dnf: add a recipeAlexander Kanavin7
This is replacing Smart package manager, which is unsupported upstream, and has a growing amount of issues (lack of python 3.x support in particular). We identified dnf as the only feasible replacement. Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2017-03-13libdnf: add a recipeAlexander Kanavin6
libdnf is required by dnf. Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2017-03-13rpm: remove 5.x recipeAlexander Kanavin83
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2017-03-13rpm: add a 4.x recipeAlexander Kanavin10
The dnf stack is written and tested against rpm 4.x. So if we want to use dnf for packaging, we should also use rpm 4 - there's simply too much work involved in making rpm 5 work with it due to significant API differences, and supporting that going forward. Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2017-03-13createrepo-c: add a recipeAlexander Kanavin3
This is the current C reimplementation/replacement of the original createrepo. https://github.com/rpm-software-management/createrepo_c/wiki Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2017-03-13rpmresolve: remove the recipeAlexander Kanavin2
The source code is incompatible with rpm4 API - let's use rpm binary itself for now. Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2017-03-11libcomps: add a recipeAlexander Kanavin3
libcomps is required by dnf. Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-03-11librepo: add a recipeAlexander Kanavin5
librepo is needed by dnf and libdnf. Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-03-11python-backports-lzma: add a recipeAlexander Kanavin2
It is needed by dnf, and only when using Python 2.x, so can be dropped after moving dnf/rpm4 stack to Python 3.x. Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-03-11python-iniparse: add a recipeAlexander Kanavin1
python-iniparse is required by dnf. Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-03-11python-pygpgme: add a recipeAlexander Kanavin1
python-pygpgme is required by dnf. Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-03-11pkgconfig: specify --disable-indirect-deps to configureJoe Slater1
This preserves the current behaviour because the auto test by configure will never return yes. ./libtool is needed by the test and it will never exist. Signed-off-by: Joe Slater <jslater@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-03-11opkg-utils: bump revisionChen Qi1
Bump to latest revision so that update-alternatives could detect priority conflict. Also, we could remove the following patch because opkg-utils has already fixed the problem in another way. 0001-Makefile-use-defined-bindir-and-mandir-as-installati.patch [YOCTO #8314] Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-03-11bison: Remove unused bison-2.3_m4.patchMartin Jansa1
* it was used only by bison-2.3 which was moved to meta-gplv2 layer Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-03-11opkg: enable libsolv backend by defaultAlejandro del Castillo1
The libsolv backend is vastly superior than the currently enabled internal ad-hoc solver. While the switch does have a small impact on disk and memory footprint, it make sense to change the default as for most cases the disk/memory footprint hit should be acceptable. ======================== Disk Footprint Increase ======================== qemux86-64 523K qemuarm 445K qemux86 576K ==================================================== Command [1] Libsolv Internal Solver ==================================================== opkg update 26.21 MB 26.21 MB opkg list 29.87 MB 29.87 MB opkg install procps 30.99 MB 27.33 MB opkg remove procps 1.69 MB 1.69 MB opkg update 30.97 MB 27.75 MB [1] Profile done via 'valgrind --tool=massif <command>' in a feed with ~18K packages. Signed-off-by: Alejandro del Castillo <alejandro.delcastillo@ni.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-03-11yasm: Set CCLD_FOR_BUILD to ensure BUILD_CC is usedRichard Purdie1
Otherwise cc may be used which isn't correct. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-03-10go: Add recipes for golang compilers and toolsKhem Raj36
* This is converging the recipes for go from meta-virtualization and oe-meta-go * Add recipes for go 1.7 * go.bbclass is added to ease out writing recipes for go packages * go-examples: Add an example, helloworld written in go This should serve as temlate for writing go recipes * Disable for musl, at least for now * Disable for x32/ppc32 which is not supported Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-03-10quilt: Avoid hardcoding paths into outputRichard Purdie2
Avoids: quilt-0.65-r0 do_package_qa: QA Issue: /usr/lib/quilt/ptest/quilt/scripts/edmail contained in package quilt-ptest requires /media/build1/poky/build/tmp/hosttools/perl, but no providers found in RDEPENDS_quilt-ptest? [file-rdeps] Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-03-10cdrtools-native: Fix when cc is missingRichard Purdie1
If cc isn't in PATH, the recipe fails. Set a variable to avoid this. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-03-10quilt: Don't add hardcoded links to utilitiesRichard Purdie1
This triggers warnings about absolute symlink paths with the PATH changes. In reality we simply don't need/care about these so just remove/disable them. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-03-10meta: do not append to BBCLASSEXTENDMing Liu1
Replace some "+=/=+" with "=" when setting BBCLASSEXTEND, they are redundant and inconsistent with the same setting in other recipes. Signed-off-by: Ming Liu <peter.x.liu@external.atlascopco.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-03-10gcc-runtime: Enable libmpx for x86-64Mikko Ylinen1
Intel MPX was recently enabled on x86 (_append_x86) but that didn't enable it on x86-64. Explicitly enable libmpx on x86-64 too. Signed-off-by: Mikko Ylinen <mikko.ylinen@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-03-10e2fsprogs: expand @mkdir_p@ during configurationJoe Slater2
If we do not do this, locale data will not be put into /usr/share/locale. Signed-off-by: Joe Slater <jslater@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-03-08gcc-runtime: Fix QA issueMartin Jansa1
ERROR: gcc-runtime-6.3.0-r0 do_package: QA Issue: gcc-runtime: Files/directories were installed but not shipped in any package: /usr/lib/libmpxwrappers.la Please set FILES such that these items are packaged. Alternatively if they are unneeded, avoid installing them or delete them within do_install. gcc-runtime: 1 installed and not shipped files. [installed-vs-shipped] Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-03-08qemu: display: CVE-2016-9912Sona Sarmadi2
virtio-gpu: memory leakage when destroying gpu resource Reference: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9912 Reference to upstream patch: http://git.qemu-project.org/?p=qemu.git;a=patch;h=b8e23926c568f2e963af39028b71c472e3023793 Signed-off-by: Sona Sarmadi <sona.sarmadi@enea.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-03-08qemu: display: CVE-2016-9908Sona Sarmadi2
virtio-gpu: information leakage in virgl_cmd_get_capset References: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9908 Signed-off-by: Sona Sarmadi <sona.sarmadi@enea.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-03-08qemu: Move recipe version specific patches and features to recipeNathan Rossi2
Move all the version specific patches, overrides and configuration that are in qemu.inc to the versioned QEMU recipe. This includes moving patches that target the versioned recipe, ptest configuration (which is not available in QEMU by default) and the installing of the powerpc_rom.bin. All these patches/files are also only located in the FILESEXTRAPATHS that is valid from the recipe file and not from qemu.inc itself. The purpose of this change is to make the qemu.inc re-usable for multiple versions of QEMU as well as forks and recipes that intend to provide custom patches. Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
2017-03-08qemu: Convert KVMOPTS to PACKAGECONFIGNathan Rossi1
Move the KVMOPTS configuration checks and option setting to a PACKAGECONFIG option. This also changes the checking of KVM support on the host build machine so that it is processed as a PACKAGECONFIG _remove for class-native only. The darwin/mingw32 overrides are kept and applied as _remove overrides. Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
2017-03-08qemu: Consolidate EXTRA_OECONFNathan Rossi1
Consolidate the configure options into the EXTRA_OECONF variable, including merging any native(sdk) specific options. This consolidation also makes the use of 'system' pixman in the nativesdk case, this is desirable as the QEMU internal pixman may not be available (using QEMU git as opposed to tarball) and pixman is already in DEPENDS. Additionally the QEMU configure recommends to use the system pixman if available. Additionally move the options specified in the do_configure into the EXTRA_OECONF variable. And flesh out all the target directories. Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
2017-03-08qemu: Improve and add PACKAGECONFIG optionsNathan Rossi1
Move the '--disable-bluez' and '--disable-iscsi' options to PACKAGECONFIG. And added the ${BLUEZ} dependency. Fix up the 'gcrypt' option to depend on 'libgcrypt' instead of gcrypt. This is the expected dependency as noted in the QEMU configure help. Handle the '--audio-drv-list' option inside the PACKAGECONFIG[alsa] args. The previous setting uses a ',' to denote the options for the arg however a space inside quotes is also acceptable and allows the arg to be used into the PACKAGECONFIG flag. Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
2017-03-07meta: start to ignore the largefile distro featureAndre McCurdy4
The largefile distro feature has been enabled by default in oe-core for a long time and, more recently, also in poky-tiny. Building without the largefile distro feature receives little or no testing. Many packages now enable LFS without exposing a configure option, so there should be very little expectation that disabling the distro feature will result in a distro which globally disables LFS. Respecting the distro feature adds a maintenance over-head and may be the source of configurations oddities (e.g. dbus-native currently builds with LFS disabled for no clear reason - fixed by this commit). Ignore the largefile distro feature more widely, as a first step towards deprecating and eventually removing it. Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-03-07recipes: Move out stale GPLv2 versions to a seperate layeruninative-1.5Richard Purdie49
These are recipes where the upstream has moved to GPLv3 and these old versions are the last ones under the GPLv2 license. There are several reasons for making this move. There is a different quality of service with these recipes in that they don't get security fixes and upstream no longer care about them, in fact they're actively hostile against people using old versions. The recipes tend to need a different kind of maintenance to work with changes in the wider ecosystem and there needs to be isolation between changes made in the v3 versions and those in the v2 versions. There are probably better ways to handle a "non-GPLv3" system but right now having these in OE-Core makes them look like a first class citizen when I believe they have potential for a variety of undesireable issues. Moving them into a separate layer makes their different needs clearer, it also makes it clear how many of these there are. Some are probably not needed (e.g. mc), I also wonder whether some are useful (e.g. gmp) since most things that use them are GPLv3 only already. Someone could now more clearly see how to streamline the list of recipes here. I'm proposing we mmove to this separate layer for 2.3 with its future maintinership and testing to be determined in 2.4 and beyond. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-03-07patchelf: Fix issues with the 'hole' in binaries approachRichard Purdie2
We're seeing two issues with patchelf, one where it inflates binaries to MBs in size, the other where stripping the resulting binary fails: $ strip fixincl Not enough room for program headers, try linking with -N [.note.ABI-tag]: Bad value The patch header describes more about what the problem is and how the patch fixes it. [YOCTO #11123] [YOCTO #11009] Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-03-07binutils: Upgrade to 2.28 releaseKhem Raj28
Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-03-04guile: fix a bashismMing Liu1
A following flaw was detected by verify-bashisms script: ...... meta/recipes-devtools/guile/guile_2.0.13.bb possible bashism in guile_cross_config line 94 ($'...' should be "$(printf '...')"): echo '#!'`which ${BUILD_SYS}-guile`$' \\\n--no-auto-compile -e main -s\n!#\n(define %guile-build-info '\'\( \ > ${B}/guile-config.cross ...... Fixed by removing $'...' from echo command, using a printf instead. Signed-off-by: Ming Liu <peter.x.liu@external.atlascopco.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-03-04gcc-source: add comment explaining why a function is PythonRoss Burton1
Signed-off-by: Ross Burton <ross.burton@intel.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-10 18:11:56 +0000