Hello Chris.

Thanks Chris.

Upstream git master already contains the same fix I came up with
(#include <stdint.h>).

I updated the packaging to fio-2.6 and asked Sven to review and sponsor
the package.

http://people.teamix.net/~ms/debian/sid/fio/fio_2.6-1.dsc

http://people.teamix.net/~ms/debian/sid/fio/

Or any of the git repos like:

https://anonscm.debian.org/cgit/collab-maint/fio.git

Sven may take a while for the review, cause he is quite busy.

Thanks,
Martin


Am Mittwoch, 24. Februar 2016, 09:49:03 CET schrieben Sie:
> Source: fio
> Version: 2.2.10-1
> Severity: serious
> Justification: fails to build from source
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: ftbfs
> X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
> 
> Dear Maintainer,
> 
> fio fails to build from source in unstable/amd64:
> 
>   [..]
> 
>       CC engines/e4defrag.o
>       CC engines/splice.o
>       CC engines/rbd.o
>       CC engines/mtd.o
>       CC lib/libmtd.o
>       CC lib/libmtd_legacy.o
>   In file included from lib/libmtd_legacy.c:38:0:
>   lib/libmtd.h:288:8: error: unknown type name 'uint8_t'
>           uint8_t mode);
>           ^
>   lib/libmtd.h:305:4: error: unknown type name 'uint64_t'
>       uint64_t start, uint64_t length, void *data);
>       ^
>   lib/libmtd.h:305:20: error: unknown type name 'uint64_t'
>       uint64_t start, uint64_t length, void *data);
>                       ^
>   lib/libmtd.h:322:5: error: unknown type name 'uint64_t'
>        uint64_t start, uint64_t length, void *data);
>        ^
>   lib/libmtd.h:322:21: error: unknown type name 'uint64_t'
>        uint64_t start, uint64_t length, void *data);
>                        ^
>   Makefile:287: recipe for target 'lib/libmtd_legacy.o' failed
>   make[1]: *** [lib/libmtd_legacy.o] Error 1
>   make[1]: Leaving directory 
> '/home/lamby/temp/cdt.20160224080541.mSFrnTpDmm/fio-2.2.10'
>   dh_auto_build: make -j1 returned exit code 2
>   debian/rules:15: recipe for target 'build' failed
>   make: *** [build] Error 2
> 
>   [..]
> 
> The full build log is attached.
> 
> 
> Regards,
> 
> 

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to