Bug#1016953: intel-media-driver: FTBFS on i386: error: format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 3 has type ‘uint64_t’

2022-08-10 Thread Sebastian Ramacher
Control: forwarded -1 https://github.com/intel/media-driver/issues/1468 Control: tags -1 upstream On 2022-08-10 21:13:47 +0100, Simon McVittie wrote: > Control: tags -1 - patch > > On Wed, 10 Aug 2022 at 20:55:44 +0100, Simon McVittie wrote: > > Yes, that seems to work. > > Sorry, no, that

Bug#1016953: intel-media-driver: FTBFS on i386: error: format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 3 has type ‘uint64_t’

2022-08-10 Thread Simon McVittie
Control: tags -1 - patch On Wed, 10 Aug 2022 at 20:55:44 +0100, Simon McVittie wrote: > Yes, that seems to work. Sorry, no, that change is not sufficient. I also get: In file included from /<>/media_common/agnostic/common/os/mos_os.h:31, from

Bug#1016953: intel-media-driver: FTBFS on i386: error: format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 3 has type ‘uint64_t’

2022-08-10 Thread Simon McVittie
Control: tags -1 + patch On Wed, 10 Aug 2022 at 15:07:09 +0100, Simon McVittie wrote: > The solution might be as simple as including or , > and using "%" PRIu64 instead of "%lu". Yes, that seems to work. smcv From: Simon McVittie Date: Wed, 10 Aug 2022 14:49:50 +0100 Subject:

Bug#1016953: intel-media-driver: FTBFS on i386: error: format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 3 has type ‘uint64_t’

2022-08-10 Thread Simon McVittie
Source: intel-media-driver Version: 22.5.1+dfsg1-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) intel-media-driver failed to build on i386, breaking multiarch co-installation of amd64 and i386 driver libraries.