summaryrefslogtreecommitdiffstats
path: root/package/python-django/python-django.hash
diff options
context:
space:
mode:
authorYann E. MORIN <yann.morin.1998@free.fr>2018-08-17 14:38:03 +0200
committerPeter Korsgaard <peter@korsgaard.com>2018-08-17 18:57:25 +0200
commitc48f8a64626c60bd1b46804b7cf1a699ff53cdf3 (patch)
treedab7ba21271ffdc2877177b10ec4d3c134c6af65 /package/python-django/python-django.hash
parentf70b13a7cb6eb01e9d78fddcb695b84a22e5699b (diff)
downloadbuildroot-c48f8a64626c60bd1b46804b7cf1a699ff53cdf3.tar.gz
buildroot-c48f8a64626c60bd1b46804b7cf1a699ff53cdf3.zip
package/m4: fix build on host with glibc-2.28
glibc-2.28 did quite some lifting in their headers, which breaks the way some packages were detecting glibc, like gnulib. However, packages do bundle gnulib (it was meant to be bundled), and so does m4. Since m4 hasn't seen the slightest commit since 2017-01-09, it is bundling an old gnulib version, that predates glibc-2.28, and thus breaks. It also means that upstream hasn't already fixed the issue. Furthermore, as upstream is using a git submodule for gnulib, and that the paths are not the same in the release tarball (in lib/) and in the git tree (in gnulib/), we can't do a plain backport. So, we selectively backport the two patches from gnulib upstream, restricted to only the files that happen to be used in m4. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Reported-by: c32 on IRC Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Diffstat (limited to 'package/python-django/python-django.hash')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud