linux/poky.git/meta/recipes-core/gettext, branch sumo

gettext: beat library detection into shape

2018-01-30T12:53:16+00:00

For reasons I can't explain gettext uses several hundred lines of convoluted m4 to find the paths to a library. If we don't tell it where to find a library it will hunt around and potentially have host contamination as /usr/lib on the host is explicitly searched. If we tell it the prefix to a library then we get bad RPATHs in the binaries (such as /usr/lib/../lib), and the search assumes that it knows best about what the library directories are under that prefix (even when it's wrong). So, replace the lookup where possible with pkg-config calls (libxml2, glib, libcroco). libunistring doens't have a pkgconfig file so just don't use the system libunistring: the library is tiny anyway. (From OE-Core rev: 1ff35fbbdd50660b86f8e254685ae0c8338b6e11) (From OE-Core rev: e6c0f8eddf8ff4a6132934a69e0f3450d4843ece) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

gettext: rationalise optional dependencies

2018-01-11T10:26:07+00:00

gettext has optional dependencies on libxml2, glib, libcroco and libunistring. If they're not available then gettext will use internal copies, but it can also use system libraries. For gettext-native and nativesdk-gettext continue to use the internal copies to reduce the dependencies, but for target use the system shared libraries. Also gettext 0.19.7 onwards swapped expat for libxm2, so remove the build dependency on expat. (From OE-Core rev: a82aa376a9229428ec25629e97a1efa56f0afae7) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

gettext: relocate msgfmt utility for all recipes

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

Now that epiphany needs a working msgfmt as well, let's do this trick where it should be. (From OE-Core rev: 7c0032b81f56fea5bec33aa0e74d6e28873f72a8) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

meta: Drop remnants of uclibc support

2017-06-22T08:16:00+00:00

uclibc support was removed a while ago and musl works much better. Start to remove the various overrides and patches related to uclibc which are no longer needed. uclibc support in a layer would still be possible. I have strong reasons to believe nobody is still using uclibc since patches are missing and I doubt the metadata even parses anymore. (From OE-Core rev: 653704e9cf325cb494eb23facca19e9f05132ffd) Signed-off-by: Richard Purdie

gettext: split recipe's description

2017-03-17T16:53:06+00:00

Split long recipe description into multiple lines. (From OE-Core rev: 13cf0df0252941b9575da613488cbc141e043a8a) Signed-off-by: Leonardo Sandoval 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

gettext: fix formatting issues

2017-02-23T20:49:51+00:00

Fixed when compile with "-Wformat -Wformat-security -Werror=format-security": | gettext-tools/gnulib-lib/libcroco/cr-statement.c: In function 'cr_statement_dump_charset': | gettext-tools/gnulib-lib/libcroco/cr-statement.c:2661:17: error: format not a string literal and no format arguments [-Werror=format-security] | fprintf (a_fp, str) ; And: gettext-tools/gnulib-lib/libxml/timsort.h:326:80: warning: format '%lu' expects argument of type 'long unsigned int', but argument 3 has type 'unsigned int' [-Wformat=] fprintf(stderr, "Error allocating temporary storage for tim sort: need %lu bytes", sizeof(SORT_TYPE) * new_size); [YOCTO #9544] (From OE-Core rev: 41eb2da1b05515e3803a331686fa6ca763ae2e69) Signed-off-by: Robert Yang Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

gettext_0.16.1: whitespace changes to align with v0.19.8.1

2016-08-23T16:44:40+00:00

This further aligns this recipe with the GPLv3 version to make it easier to spot differences between the two recipes. (From OE-Core rev: e25a533e8ca2fc1fa897df252830825cb9a5f028) Signed-off-by: André Draszik Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

gettext_0.16.1: align configure options with v0.19.8.1 recipe

2016-08-23T16:44:40+00:00

It doesn't look like we need any of those features, so let's disable them explicitly. (From OE-Core rev: 0a095473eec333f918ef831dea1c2f269a64fc62) Signed-off-by: André Draszik Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

gettext_0.16.1: fix lispdir configure option

2016-08-23T16:44:40+00:00

The option is called --with(out)-lispdir, not --with(out)-lisp (From OE-Core rev: 422c92d2806f776252c15ec9fe204b204503c4d2) Signed-off-by: André Draszik Signed-off-by: Ross Burton Signed-off-by: Richard Purdie