COMPILE.TXT | 20 10 + 10 - 0 !
README | 6 3 + 3 - 0 !
config.mk | 2 1 + 1 - 0 !
3 files changed, 14 insertions(+), 14 deletions(-)

 fix typos.
 Some things here and there that need to be fixed.

Makefile | 14 7 + 7 - 0 !
1 file changed, 7 insertions(+), 7 deletions(-)

 stop installing libcapstone in /usr/lib64.
 Upstream seems to make a distinction between x86_64 and the rest of
 architectures and install the libraries in /usr/lib64 if we are building

Makefile | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 cppflags is not being used.
 Without CPPFLAGS we cannot have fortified builds.

bindings/python/Makefile | 2 1 + 1 - 0 !
bindings/python/capstone/capstone.py | 2 1 + 1 - 0 !
bindings/python/pyx/ccapstone.pxd | 2 1 + 1 - 0 !
bindings/python/setup_cython.py | 26 14 + 12 - 0 !
4 files changed, 17 insertions(+), 15 deletions(-)

 fix build system for python bindings.
 The build system in capstone for the Python bindings works by installing
 the library with the headers, and then building the bindings.  Change that
 to allow building them in the same run we create the library, and search
 for the versioned library instead of the .so one, removing the dependency
 on libcapstone-dev.

MCInst.h | 2 1 + 1 - 0 !
arch/Mips/MipsInstPrinter.c | 36 18 + 18 - 0 !
cs.c | 8 4 + 4 - 0 !
include/capstone.h | 2 1 + 1 - 0 !
tests/test_mips.c | 10 5 + 5 - 0 !
5 files changed, 29 insertions(+), 29 deletions(-)

 bug#755193: capstone: ftbfs on mips
Date: Thu, 24 Jul 2014 16:36:32 +0000

package capstone FTBFS again on mips/mipsel.

It seams that adding -Umpis as CFLAGS in Makefile does not fully solve the
issue.

If we add this flag directory in rules for mips, package builds successfully.

Patch that contains needed changes is attached: fix-capstone-rules.patch