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’

[Simon McVittie <smcv@debian.org>]

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.

https://buildd.debian.org/status/fetch.php?pkg=intel-media-driver&arch=i386&ver=22.5.1%2Bdfsg1-1&stamp=1659479611&raw=0

/<<PKGBUILDDIR>>/media_softlet/linux/common/os/osservice/mos_utilities_specific.cpp: In static member function ‘static MOS_STATUS MosUtilitiesSpecificNext::UserFeatureDumpDataToFile(const char*, MOS_PUF_KEYLIST)’:
/<<PKGBUILDDIR>>/media_softlet/linux/common/os/osservice/mos_utilities_specific.cpp:1023:44: error: format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 3 has type ‘uint64_t’ {aka ‘long long unsigned int’} [-Werror=format=]
 1023 |                     fprintf(File, "\t\t\t%lu\n",
      |                                          ~~^
      |                                            |
      |                                            long unsigned int
      |                                          %llu
 1024 |                         *(uint64_t*)(pKeyTmp->pElem->pValueArray[j].ulValueBuf));
      |                         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      |                         |
      |                         uint64_t {aka long long unsigned int}

The solution might be as simple as including <inttypes.h> or <cinttypes>,
and using "%" PRIu64 instead of "%lu". I'm testing that now.

    smcv