linux/poky.git/meta/recipes-support/libiconv, branch master

libiconv: remove 0001-Fix-link-error-when-compiling-with-gcc-O0.patch

2017-07-11T14:57:08+00:00

The recipe and patches (including this patch) had been moved into meta-mingw, this dangling patch is useless here, so should be removed. (From OE-Core rev: b1c4661742d12cfd444043e597d01bd627ee4ca4) Signed-off-by: Robert Yang Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

libiconv: remove recipe

2017-06-28T14:52:17+00:00

It was in use by oe-core only when uclibc was used, and so serves no purpose anymore. Both glibc and musl provide their own implementation. However, meta-mingw still depends on it, and so the recipe has been moved there. (From OE-Core rev: fd5f849353e045d60965079a1571160fdd980b0c) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

libiconv: fix linker failure under GCC 7

2017-05-11T15:59:18+00:00

(From OE-Core rev: 7e646dd052c7013416d99d4c0201b4694fc1bbb6) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

recipes: Move out stale GPLv2 versions to a seperate layer

2017-03-07T20:05:31+00:00

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. (From OE-Core rev: 19b7e950346fb1dde6505c45236eba6cd9b33b4b) Signed-off-by: Richard Purdie

meta: remove True option to getVar calls

2016-12-16T10:23:23+00:00

getVar() now defaults to expanding by default, thus remove the True option from getVar() calls with a regex search and replace. Search made with the following regex: getVar ?$( ?[^,()]*), True$ (From OE-Core rev: 7c552996597faaee2fbee185b250c0ee30ea3b5f) Signed-off-by: Joshua Lock Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

libiconv_1.11.1: merge build and packaging fixes from libiconv_1.14

2015-08-10T19:40:27+00:00

054151c libiconv: Fix B != S with uclibc builds 273c437 libiconv: Remove RPATH from binaries fcb8d6f libiconv_1.14.bb: Fix build failure [partial-merge] (From OE-Core rev: 898e9d7c6da2ddc60597edc2ee7b939fa38d410e) Signed-off-by: Andre McCurdy Signed-off-by: Richard Purdie

libiconv_1.11.1: fix LICENSE declaration, LGPL -> LGPLv2.0

2015-08-10T19:40:27+00:00

(From OE-Core rev: 7d2da0ef71c2ab950a67a50f5952858b33b628bc) Signed-off-by: Andre McCurdy Signed-off-by: Richard Purdie

recipes: Remove references to eglibc

2014-09-01T17:03:05+00:00

change use of eglibc related variabled to glibc equivalents (From OE-Core rev: fd15d6e0c8da75951a91d4467eda23c229b1026d) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie

libiconv: Fix B != S with uclibc builds

2014-05-08T12:00:34+00:00

Without this, uclibc builds fail with libtool version mismatches. The issue is that we need to remove the files in ${S}, not ${B} which is now the default after the B != S change. (From OE-Core rev: 054151c77dae51e2826eeac9b9ae2de3a08f0bb6) Signed-off-by: Richard Purdie Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

Add missing SUMMARY values

2014-01-02T12:50:18+00:00

These recipes all had a long DESCRIPTION but no SUMMARY; since the SUMMARY is often displayed alone by package managers and the default value ("${PN} version ${PV}") isn't particularly useful, we should always try to set SUMMARY. (From OE-Core rev: db02edd2e9d7645592933cbb25ea0ca4d6561392) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie