eb1a45f4c1
libglib2 recently changed to use the result of the autoconf macro to decide how to use strerror_r() in g_strerror() instead of embedding the same preprocessor condition as in glibc's strings.h (upstream commit c8e268bb was first included in release 2.53.4). Following this change, if ac_cv_func_strerror_r_char_p is incorrectly set to "no", the error string is an uninitialized buffer which cannot be encoded as UTF-8. The final result of this is that GLib functions that are expected to fill in an error pointer on failure in fact leave this pointing to NULL which is likely to cause a segfault in client applications. In fact the autoconf check compiles a test file but does not need to run it, so the test is safe when cross-compiling and returns the correct answer. So remove this cached value and let the configure script figure it out for itself, fixing g_strerror() on glibc systems. Signed-off-by: John Keeping <john@metanate.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> |
||
|---|---|---|
| .. | ||
| 0001-fix-compile-time-atomic-detection.patch | ||
| 0002-disable-tests.patch | ||
| Config.in | ||
| libglib2.hash | ||
| libglib2.mk | ||