summaryrefslogtreecommitdiffstats
path: root/meta/recipes-devtools
Commit message (Collapse)AuthorAgeFilesLines
...
* python3: Improve logging capabilities for do_create_manifestAlejandro Enedino Hernandez Samaniego2018-04-031-7/+27
| | | | | | | | | | | | | Adds a couple of prints to get a nicer log, and creates a small summary or report after checking every module, it makes it more feasible for adoption, easier to debug why a module ended at a certain package and see how the manifest was created. (From OE-Core rev: 4c2af72f51a7bf187615fc0b3a229d25c3e191e9) Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* nasm: Fix pure function warningsKhem Raj2018-04-032-1/+30
| | | | | | | (From OE-Core rev: e3c76fd3db928fc487e86325df299f3f02ef369c) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu: do not hardcode python2.7 pathRuslan Ruslichenko2018-04-031-1/+1
| | | | | | | | | | | | | It can be installed to some non standard path in which case build will be broken. As python2.7 is specified in HOSTTOOLS we can rely that it is present in the PATH, so no need to hardcode it to /usr/bin. (From OE-Core rev: a200d22b26aded093289cb9150b3f05f76578c83) Signed-off-by: Ruslan Ruslichenko <rruslich@cisco.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cmake: upgrade 3.10.2 -> 3.10.3Otavio Salvador2018-04-033-2/+2
| | | | | | | | | | | | | | | | | | | | | ,----[ Changes in 3.10.3 ] | Brad King (1): | CMake 3.10.3 | | Craig Scott (1): | GoogleTest: Rename TIMEOUT parameter to avoid clash | | Sebastian Holtermann (1): | Autogen: Fix for the empty source file crash in 3.10.2 | | Tianhao Chai (1): | ccmake: fix status line buffer overflow on very wide terminals `---- (From OE-Core rev: ae230e1f858f83d1ff063554b49bd3ee1f880f76) Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* pseudo: Upgrade to latest masterRichard Purdie2018-04-031-1/+1
| | | | | | | | | | | | | | | This change includes several bug fixes and improvements, including better path handling (the existance of . and .. for files), handling of the sticky bit, and syscall renameat2 handling and interception through syscall() which was breaking coreutils mv operations on fedora27. [YOCTO #12594] [YOCTO #12379] [YOCTO #11643] (From OE-Core rev: ddbcb88849d5c07a4cbbdc90fa1ab4d369476f8a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3: Fix do_create_manifest for python3-sqlite3Alejandro Enedino Hernandez Samaniego2018-03-312-21/+37
| | | | | | | | | | | | | | | | Some of the sqlite3 files ended up in python3-misc incorrectly, this is caused becuse we couldnt add the whole ${libdir}/python3/sqlite3 folder on the package because we also have another sqlite3-tests package that needs to include another folder from that directory. This patch not only fixes the do_create_manifest script to handle this situation, but also patches the manifest (created using the script) which also fixes a hiddn runtime dependency that we wouldn't have seen. (From OE-Core rev: 3324cb31670f33ffe193e550e3b3da8380b3c8c9) Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3: fix create_manifest to handle pycache foldersAlejandro Enedino Hernandez Samaniego2018-03-312-10/+15
| | | | | | | | | | | | | | | We have a couple of python modules that contain folders themselves, for that reason they also contain a __pycache__ folder inside those directories, since we include the whole folder in the manifest, the pycache directories end up with the files and not the cache files. This patch catches that and adds the directories to the correct structure. (From OE-Core rev: df9401e7e69ce162e257e827d67eb217666e532d) Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* go: Upgrade 1.10 -> 1.10.1Otavio Salvador2018-03-311-2/+5
| | | | | | | | | | This is a minor release that fixes many important issues found since 1.10 release. (From OE-Core rev: 7068024c1ee8a3ec03904d50860fc42d7c421f87) Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mmc-utils: Fix string overflow errorKhem Raj2018-03-312-2/+40
| | | | | | | | | | | The SRCREV change bring another patch from upstream b4fe0c8 fix ENH_START_ADDR overflow (From OE-Core rev: 97dd1b0ab5524fe9cda53f60847f3e3c07cc90a8) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3: consolidate sqlite3 filesRoss Burton2018-03-301-2/+5
| | | | | | | | | | Some of the sqlite3 module was in python3-misc by accident, move the files into python3-sqlite3 where they belong. (From OE-Core rev: f06a8d20560b8e93cf875ee58eddda0a976e7b14) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu: actually use the aarch64 patchRoss Burton2018-03-301-0/+1
| | | | | | | (From OE-Core rev: 590c2f13325c3f8906850c6e3b71f2fac8ed6336) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu: fix qemuarm64 intermediate kernel hang in raid6_select_algo funcVictor Kamensky2018-03-281-0/+67
| | | | | | | | | | | | | | Backport fix from qemu mainline for intermediate qemuarm64 hang issue. Root caused in OE environment, issue with aarch64 qemu logic of executing instructions that reenabe interrupts. See patch commit message for more details. Upstream-Status: Backport (From OE-Core rev: aa33945fc7cf7bfa859c4091bcfa2695c422849b) Signed-off-by: Victor Kamensky <kamensky@cisco.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* elfutils: Fix gcc compile time alignment errorsKhem Raj2018-03-283-94/+124
| | | | | | | | | | Allow devtool to organize the SRC_URI (From OE-Core rev: 49aae1d75ff1c6a9643c30a8cc5776a2ffa83dd3) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* pseudo: explicitly enable xattr supportAndreas Kaufmann2018-03-281-1/+1
| | | | | | | | | | | | | | | | | | | Pseudo is using a custom configure script that detects if it shall build with extended file attribute support or not. The check is done by simply calling 'getfattr' provided by attr-native which is not part of the dependency list. Due to the recent changes (recipe specific sysroot & cleanup of $PATH) this call fails now when the recipe is being build for the first time (at least when being build for nativesdk case). Explicitly setting up a dependency to attr-native just to satisfy configure would be wrong also since the real dependency is to attr/nativesdk-attr which are already part of the dependency list (see DEPENDS). Therefore bypass the test in the configure by explicitly enabling xattr using a configure option available in any case. (From OE-Core rev: a7381eb16ba2183ed990a009bb8e82b4702f3d98) Signed-off-by: Andreas Kaufmann <andreas.kaufmann.79@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* distcc: Change SRC_URIArmin Kuster2018-03-251-1/+1
| | | | | | | | | | | | | | | | | | ERROR: distcc-3.2-r0 do_fetch: Fetcher failure: Unable to find revision d8b18df3e9dcbe4f092bed565835d3975e99432c in branch 3.2 even from upstream ERROR: distcc-3.2-r0 do_fetch: Fetcher failure for URL: 'git://github.com/distcc/distcc.git;branch=3.2'. Unable to fetch URL from any source. ERROR: distcc-3.2-r0 do_fetch: Function failed: base_do_fetch [v2] upstream deleted the branch and the hash no longer exists. Took the git snapshot from yocto and created a copy on my github. There was no offical 3.2 release, only rc versions. (From OE-Core rev: aee44c6b1c36fb1c1f760fec60087933d1e8ea79) Signed-off-by: Armin Kuster <akuster@mvista.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* librepo: disable building of tests and docsAnuj Mittal2018-03-251-2/+2
| | | | | | | | | | Also remove libcheck dependency which was required only for tests. (From OE-Core rev: cde1b85d402f5999814de4022e3b6ddc90b4604a) Signed-off-by: Anuj Mittal <anuj.mittal@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dpkg: Backport riscv supportKhem Raj2018-03-203-5/+71
| | | | | | | | | | Refresh patches with devtool (From OE-Core rev: 6d21977c9d1cf00b102a58e28797250b9a853caf) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mtd-utils: Explicitly add pthread options to cflagsKhem Raj2018-03-201-0/+2
| | | | | | | | | | | | Some architectures e.g. riscv gcc does not add -D_REENTRANT when enabling pthreads. Help it here by adding these options while gcc gets fixed (From OE-Core rev: 856aa732cac62a2c45473bcc91f7d0c423c52f81) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* opkg-utils: use multithreaded xz when building packagesRoss Burton2018-03-202-0/+19
| | | | | | | (From OE-Core rev: 369c43cca4f00272e0f9eb8b939f38f00dc43cc3) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python-numpy: update to 1.14.2Derek Straka2018-03-203-2/+2
| | | | | | | | | | Update to the latest stable release (From OE-Core rev: 0f31b37d1233867e5dfdd126b98d5017df602888) Signed-off-by: Derek Straka <derek@asterius.io> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-pip: update to 9.0.2Derek Straka2018-03-201-2/+2
| | | | | | | | | | Update to the latest stable release (From OE-Core rev: 998ac44d8be496c852a41fa112f997362db7da4f) Signed-off-by: Derek Straka <derek@asterius.io> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-pygobject: update to 3.28.1Derek Straka2018-03-201-3/+2
| | | | | | | | | | | | Update to the latest stable release Tested in qemux86-64 running core-image-minimal (From OE-Core rev: aa33df15dca690b6556794b604cb99bd13dbce72) Signed-off-by: Derek Straka <derek@asterius.io> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python*-setuptools: update to 39.0.0Derek Straka2018-03-203-2/+2
| | | | | | | | | | | | Update the python{3}-setuptools to the latest stable version Tested on the qemu with core-image-minimal (From OE-Core rev: 8422880acf65802dbaa08238ae9e63670ed49ff3) Signed-off-by: Derek Straka <derek@asterius.io> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python-numpy: Fix build for riscv64Khem Raj2018-03-204-0/+204
| | | | | | | | (From OE-Core rev: d33b321bce110fae8e5730f507be70f33d91fe22) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-native: update to version 3.5.5 to fix security issuesDerek Straka2018-03-201-3/+3
| | | | | | | | | | | | | | License-Update: checksum change is due to bump in copyright year Resolves CVE-2017-1000158 and other potential security issues See https://docs.python.org/3.5/whatsnew/changelog.html#python-3-5-5-final (From OE-Core rev: e19df4b40d76cdae65a26fb08efc17542e0e86b9) Signed-off-by: Derek Straka <derek@asterius.io> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-native: fix build races in 'make regen-all'Alexander Kanavin2018-03-201-0/+2
| | | | | | | | | | | | Python 2.x and target Python 3.x do not have this issue. [YOCTO #12596] (From OE-Core rev: 5bfba3d09cfabb3a1895dcf9921801df318d804c) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3: add readline to PACKAGECONFIGAnuj Mittal2018-03-201-1/+4
| | | | | | | | | | | | | Provide a way to make readline dependency optional in case someone might want to use BSD alternative editline instead. Using editline would need some changes though (python issue13501). (From OE-Core rev: 9b12a3f031373ad0696409e4f933b1a585ea7f1f) Signed-off-by: Anuj Mittal <anuj.mittal@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* distcc: remove UPSTREAM_VERSION_UNKNOWNAlexander Kanavin2018-03-201-1/+0
| | | | | | | | | | Upstream has finally released a new version. (From OE-Core rev: 5d7683c7d86abd101bcee0c06cceff4ba3ee8593) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Do not use --with-linker-hash-style if LINKER_HASH_STYLE is emptyKhem Raj2018-03-201-1/+1
| | | | | | | | | | | We allow to set LINKER_HASH_STYLE to be empty so this would fail since --with-linker-hash-style needs an argument and cant be empty (From OE-Core rev: e176ab07d1afbb5d7e80d39d49b0f68738509c18) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: backport patch to fix ICE in MIPS64 target in G++Mark Hatle2018-03-202-0/+273
| | | | | | | | | | Backport a patch to fix an ICE when compiling for MIPS64. (From OE-Core rev: eaa35d43dc1490f53aa1aece948d1542048460b6) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* btrfs-tools: add RECIPE_NO_UPDATE_REASONAlexander Kanavin2018-03-151-0/+1
| | | | | | | | (From OE-Core rev: a158b458d63622a3cd1605124c380d2a130beda9) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3: Fix purelib install and runtime pathsJason Wessel2018-03-151-8/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | oe-core commit: 45afadf0b6 fixed the pip problem with purelib for python2, even though the the patch stated it was for python3. This patch addresses the purelib problem for python3. If you install the package python3-pip you will have a pip3 binary where you can see the problem on the device easily where the modules install into the incorrect area and are not able to be referenced by python3 at all. Example error: pip3 install imutils pip3 list |grep imutils || echo ERROR no imutils ERROR no imutils python3 -c 'import imutils' Traceback (most recent call last): File "<string>", line 1, in <module> ImportError: No module named 'imutils' (From OE-Core rev: 54e0b3bfc132613902418be148a900b10f6d9e38) Signed-off-by: Jason Wessel <jason.wessel@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* valgrind: Fix multilib header conflict - valgrind/config.hZhang Xiao2018-03-151-1/+2
| | | | | | | | | | Header file conflict between 32-bit and 64-bit versions. (From OE-Core rev: 6084879306db61c347b6f01f3bb64de327a9052d) Signed-off-by: Zhang Xiao <xiao.zhang@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python-numpy: reorganize numpy recipes to use a common .inc file to reduce ↵Derek Straka2018-03-153-221/+113
| | | | | | | | | | duplication (From OE-Core rev: 38edecc64d76e3228cc2d7d5447d57b85e784ac2) Signed-off-by: Derek Straka <derek@asterius.io> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* btrfs-tools: set CLEANBROKEN to 1 to avoid rebuild failureChen Qi2018-03-151-0/+2
| | | | | | | | | | | | | When rebuilding btrfs-tools, we would sometimes meet the following error. Makefile:43: *** Makefile.inc not generated, please configure first. Set CLEANBROKEN to "1" to solve this problem. (From OE-Core rev: 4e2687ef9e649c8c1dc4011d2e7c05dfbba56fb8) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3: update to version 3.5.5 to fix security issuesDerek Straka2018-03-151-3/+3
| | | | | | | | | | | | | License-Update: checksum change is due to bump in copyright year Resolves CVE-2017-1000158 and other potential security issues See https://docs.python.org/3.5/whatsnew/changelog.html#python-3-5-5-final (From OE-Core rev: 4a27d50e4e8db87d005aca9d976fe8e674952777) Signed-off-by: Derek Straka <derek@asterius.io> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python*-setuptools: update to 38.5.2Derek Straka2018-03-153-2/+2
| | | | | | | | | | | Update the python{3}-setuptools to the latest stable version Tested on the qemu with core-image-minimal (From OE-Core rev: 106239a250488508f5c3593d9c8c3d4f70ff0ba3) Signed-off-by: Derek Straka <derek@asterius.io> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* unfs3: Fix libtirpc usage for unfs3-native versionRichard Purdie2018-03-151-2/+2
| | | | | | (From OE-Core rev: e37c4f1ff2b440b0a232b0482c136cc9f7b24e0f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* unfs3: Fix build with muslKhem Raj2018-03-152-3/+44
| | | | | | | | | | | Should also fix build on new build hosts where with glibc 2.27 rpc support is dropped in favor of libtirpc (From OE-Core rev: 86f4c68c76098d6735b4cb640996d748b8ff82fb) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mklibs-native: refresh patchesAlexander Kanavin2018-03-111-12/+13
| | | | | | | | | | | | | | | | | | | | The patch tool will apply patches by default with "fuzz", which is where if the hunk context isn't present but what is there is close enough, it will force the patch in. Whilst this is useful when there's just whitespace changes, when applied to source it is possible for a patch applied with fuzz to produce broken code which still compiles (see #10450). This is obviously bad. We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For that to be realistic the existing patches with fuzz need to be rebased and reviewed. (From OE-Core rev: 7b1dfc0f67905435906ae806987e945134311045) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tcf-agent: refresh patchesRoss Burton2018-03-111-6/+8
| | | | | | | | | | | | | | | | | | | | | The patch tool will apply patches by default with "fuzz", which is where if the hunk context isn't present but what is there is close enough, it will force the patch in. Whilst this is useful when there's just whitespace changes, when applied to source it is possible for a patch applied with fuzz to produce broken code which still compiles (see #10450). This is obviously bad. We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For that to be realistic the existing patches with fuzz need to be rebased and reviewed. (From OE-Core rev: 9f77858360b33de6c4f66638fea8a8051fb6208f) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ruby: refresh patchesRoss Burton2018-03-111-10/+7
| | | | | | | | | | | | | | | | | | | | | The patch tool will apply patches by default with "fuzz", which is where if the hunk context isn't present but what is there is close enough, it will force the patch in. Whilst this is useful when there's just whitespace changes, when applied to source it is possible for a patch applied with fuzz to produce broken code which still compiles (see #10450). This is obviously bad. We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For that to be realistic the existing patches with fuzz need to be rebased and reviewed. (From OE-Core rev: 44e650f961888b75797da8ecc23654f672c5fae6) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu: drop already applied glibc-2.25.patchAlexander Kanavin2018-03-112-75/+0
| | | | | | | | | | Due to patch fuzz it was applied again in a different place. (From OE-Core rev: c1596c6a26bc099a5f27f8a7f9feb7d07bd30cd5) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu: refresh patchesRoss Burton2018-03-112-22/+16
| | | | | | | | | | | | | | | | | | | | | The patch tool will apply patches by default with "fuzz", which is where if the hunk context isn't present but what is there is close enough, it will force the patch in. Whilst this is useful when there's just whitespace changes, when applied to source it is possible for a patch applied with fuzz to produce broken code which still compiles (see #10450). This is obviously bad. We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For that to be realistic the existing patches with fuzz need to be rebased and reviewed. (From OE-Core rev: a5c1069d2c0570186792d61151e1865642afd73a) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python: refresh patchesRoss Burton2018-03-116-168/+166
| | | | | | | | | | | | | | | | | | | | | The patch tool will apply patches by default with "fuzz", which is where if the hunk context isn't present but what is there is close enough, it will force the patch in. Whilst this is useful when there's just whitespace changes, when applied to source it is possible for a patch applied with fuzz to produce broken code which still compiles (see #10450). This is obviously bad. We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For that to be realistic the existing patches with fuzz need to be rebased and reviewed. (From OE-Core rev: 8a5c1328c4ea63443a92813c54bd2229c9959ff9) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* opkg-utils: refresh patchesRoss Burton2018-03-112-16/+10
| | | | | | | | | | | | | | | | | | | | | The patch tool will apply patches by default with "fuzz", which is where if the hunk context isn't present but what is there is close enough, it will force the patch in. Whilst this is useful when there's just whitespace changes, when applied to source it is possible for a patch applied with fuzz to produce broken code which still compiles (see #10450). This is obviously bad. We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For that to be realistic the existing patches with fuzz need to be rebased and reviewed. (From OE-Core rev: ca733ba0e28d6d4c199e149ce8ae428397dfa51f) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* m4: refresh patchesRoss Burton2018-03-111-5/+6
| | | | | | | | | | | | | | | | | | | | | The patch tool will apply patches by default with "fuzz", which is where if the hunk context isn't present but what is there is close enough, it will force the patch in. Whilst this is useful when there's just whitespace changes, when applied to source it is possible for a patch applied with fuzz to produce broken code which still compiles (see #10450). This is obviously bad. We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For that to be realistic the existing patches with fuzz need to be rebased and reviewed. (From OE-Core rev: 87118e6a2ed6da1ceaf484c326ec6d0ac8c1b8be) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* i2c-tools: refresh patchesRoss Burton2018-03-111-14/+11
| | | | | | | | | | | | | | | | | | | | | The patch tool will apply patches by default with "fuzz", which is where if the hunk context isn't present but what is there is close enough, it will force the patch in. Whilst this is useful when there's just whitespace changes, when applied to source it is possible for a patch applied with fuzz to produce broken code which still compiles (see #10450). This is obviously bad. We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For that to be realistic the existing patches with fuzz need to be rebased and reviewed. (From OE-Core rev: 00677e03156228f752476520911c19d4156db8da) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: drop patch that is already upstreamAlexander Kanavin2018-03-112-52/+0
| | | | | | | | | | | | Due to patch fuzz, it was applied again, so the same code sequence was repeated twice. Not sure if that caused any bugs, but certainly wasn't the right thing to do. (From OE-Core rev: e3a50788bfeabbde226e280803a01dd7f765b2bc) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* e2fsprogs: refresh patchesRoss Burton2018-03-112-21/+21
| | | | | | | | | | | | | | | | | | | | | The patch tool will apply patches by default with "fuzz", which is where if the hunk context isn't present but what is there is close enough, it will force the patch in. Whilst this is useful when there's just whitespace changes, when applied to source it is possible for a patch applied with fuzz to produce broken code which still compiles (see #10450). This is obviously bad. We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For that to be realistic the existing patches with fuzz need to be rebased and reviewed. (From OE-Core rev: 6a83aca280fece30fd7c17f32f07f592f6300c6c) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-07-04 07:35:22 +0000