diff options
| author | alpine-mips-patches <info@mobile-stream.com> | 2018-11-17 20:29:33 +0000 |
|---|---|---|
| committer | Leonardo Arena <rnalrd@alpinelinux.org> | 2019-01-04 10:23:08 +0000 |
| commit | b0c083a319da3cd9268c630b9b4b662e1d01b5c5 (patch) | |
| tree | 5e7ab7532786108b3c0a6f31fd92327b7efdb250 /community/python3-tkinter | |
| parent | 64a969f0cd8a0df31772a84d6b0d9f264c4a337e (diff) | |
| download | aports-b0c083a319da3cd9268c630b9b4b662e1d01b5c5.tar.bz2 aports-b0c083a319da3cd9268c630b9b4b662e1d01b5c5.tar.xz | |
main/xfsprogs: fix build on mips* and ppc64le
musl-1.1.20 implements support (or lack thereof) for the MAP_SYNC flag by #define'ing
it uncoditionally in generic <sys/mman.h> then #undef'ining optionally in arch-specific
<bits/mman.h> (e.g. for mips* and powerpc*). So io/mmap.c fails to compile since it
includes <sys/mman.h> (which undefines MAP_SYNC on mips* and powerpc*) after "linux.h"
(which either defines fallback MAP_SYNC values or pulls <asm-generic/mman{-common.h}>).
The proposes patch also fixes the flawed MAP_SYNC detection logic in the configure script
because io/mmap.c always uses the MAP_SYNC definition (either real one or zero fallback).
Otherwise xfsprogs wrongly detects the MAP_SYNC presence on mips* and ppc64le and the code
does not define MAP_SYNC fallback so io/mmap.c still fails to compile.
Note the last (2018-07-11) successful xfsprogs build for ppc64le was against musl-1.1.19
(without any support for MAP_SYNC).
The problem with MAP_SYNC detection is as follows. The configure script checks only
<asm-generic/mman{-common}.h> headers for the MAP_SYNC definition instead of using
the arch-specific <asm/mman.h>. But some architectures (mips, powerpc, parisc) do not
support the MAP_SYNC feature at all, do not use the <asm-generic/mman{-common.h}> files
and do not define the flag in the corresponding <asm/mman.h> header.
Diffstat (limited to 'community/python3-tkinter')
0 files changed, 0 insertions, 0 deletions
