[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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



Your message dated Sat, 17 Sep 2022 08:34:49 +0000
with message-id <E1oZTHl-00758q-2U@fasolo.debian.org>
and subject line Bug#1016953: fixed in intel-media-driver 22.5.1+dfsg1+really22.4.3-1
has caused the Debian Bug report #1016953,
regarding intel-media-driver: FTBFS on i386: error: format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 3 has type ‘uint64_t’
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1016953: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016953
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
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

--- End Message ---
--- Begin Message ---
Source: intel-media-driver
Source-Version: 22.5.1+dfsg1+really22.4.3-1
Done: Sebastian Ramacher <sramacher@debian.org>

We believe that the bug you reported is fixed in the latest version of
intel-media-driver, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1016953@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sebastian Ramacher <sramacher@debian.org> (supplier of updated intel-media-driver package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sat, 17 Sep 2022 10:17:13 +0200
Source: intel-media-driver
Architecture: source
Version: 22.5.1+dfsg1+really22.4.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers <debian-multimedia@lists.debian.org>
Changed-By: Sebastian Ramacher <sramacher@debian.org>
Closes: 1016953
Changes:
 intel-media-driver (22.5.1+dfsg1+really22.4.3-1) unstable; urgency=medium
 .
   * Revert to upstream version 22.4.3 (Closes: #1016953)
Checksums-Sha1:
 a903d197a7a85492850c90d8dcc3377186cc268b 2463 intel-media-driver_22.5.1+dfsg1+really22.4.3-1.dsc
 e54bc39354e3e80bbb8be546baa137b9c3f4681f 7595344 intel-media-driver_22.5.1+dfsg1+really22.4.3.orig.tar.xz
 c75644988c036081c16d4eda957f131a940e3654 7200 intel-media-driver_22.5.1+dfsg1+really22.4.3-1.debian.tar.xz
Checksums-Sha256:
 f55c339f267e56478834872cfb6bff7dc9dd500a5e03f12f7340f176a4b2e29d 2463 intel-media-driver_22.5.1+dfsg1+really22.4.3-1.dsc
 3f2ff26b9c3ae37a94f38da9869f4d5f99e2326c7d1793e5fdea9b825a76322b 7595344 intel-media-driver_22.5.1+dfsg1+really22.4.3.orig.tar.xz
 866a2c4b5ef03b3dfa34156b09a1538d019d10c14eca2a74191af594e66f8ace 7200 intel-media-driver_22.5.1+dfsg1+really22.4.3-1.debian.tar.xz
Files:
 996667e50190dad7eaf5af772302f6aa 2463 video optional intel-media-driver_22.5.1+dfsg1+really22.4.3-1.dsc
 663371c315a88c78d76ababe5354c22b 7595344 video optional intel-media-driver_22.5.1+dfsg1+really22.4.3.orig.tar.xz
 04a39d1b4f014cdf93b7d1d89668348f 7200 video optional intel-media-driver_22.5.1+dfsg1+really22.4.3-1.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAmMlhV0ACgkQafL8UW6n
GZO59w/+KfYZmGOP7nRZ5A1ZfUWZW76VZLvzuaWreMJF6r5nOHi9gKDY+XAvtvp4
xES4gCGEUrr9OY07I6DX5t1XIuCo2k9bZ+gThmbmPB4U+ASdLMTgs+U7v2znVgsc
RELy1lT6+7k+jnx72tMB/ydcEpWvEMUAPzrrXuGzNsF+P3RIExSB2SfNv+DOACNp
8VEM1CYqiUHCyP9MlgNVYucvBzeeLYreLMOh2tyr5OWBQbRtiesXbgLAch1uuyOr
Bi9T8QQx/UCFdwmbbl98RtVrHKWm3Js5QfYjxn6+W+GqdhkMxaX07iw/10Hdhhtj
r7WCpyWMkSULTg0WFxjy7KzZjPLxeRtfd0KJtkEq37w9Azzskv/hbzFj7d5KTSil
u91lKdCrbNK0ezw/+q8I4Hjhh9P/sD3k3B41bAzBbsDARzEB3Uykj8I5KSSgf5d8
s59E55Ei7IUL4vyXsSdhoFsgqLA4mtZdnPiJ3K4W5iTwkP57v1WCzsd3fIKl4+wK
t0lUt6lr5S4dN3E2pTrHeOt8Z12UpLJGJOokd6f9ata6GFn5BEuF7iOBeW1o1ci2
HW7CB61boHevUBFAZ/mQHGzyC575/9QF1j68f14HMEWZSyvsX9ndQf28immObeME
UDo7WCkdoCyCc/1uBWc6d+HXvoWYOj3xKYvZp6tp8/9YZ7wW8mo=
=wZ8m
-----END PGP SIGNATURE-----

--- End Message ---

Reply to: