Bug 111666

Summary:	drm.h:50:9: error: unknown type name 'uint8_t'
Product:	Mesa	Reporter:	Vinson Lee <vlee>
Component:	Other	Assignee:	mesa-dev
Status:	RESOLVED MOVED	QA Contact:	mesa-dev
Severity:	not set
Priority:	not set	CC:	eric
Version:	git	Keywords:	bisected, regression
Hardware:	x86-64 (AMD64)
OS:	Mac OS X (All)
Whiteboard:
i915 platform:		i915 features:

Description Vinson Lee 2019-09-12 00:30:19 UTC

In file included from ../src/gallium/state_trackers/dri/dri_helpers.c:24:
In file included from ../include/drm-uapi/drm_fourcc.h:27:
../include/drm-uapi/drm.h:50:9: error: unknown type name 'uint8_t'
typedef uint8_t  __u8;
        ^
../include/drm-uapi/drm.h:52:9: error: unknown type name 'uint16_t'
typedef uint16_t __u16;
        ^
../include/drm-uapi/drm.h:54:9: error: unknown type name 'uint32_t'
typedef uint32_t __u32;
        ^
../include/drm-uapi/drm.h:56:9: error: unknown type name 'uint64_t'
typedef uint64_t __u64;
        ^


272f9cfe6a19212354c89dc443959473ac5d398e is the first bad commit
commit 272f9cfe6a19212354c89dc443959473ac5d398e
Author: Eric Anholt <eric@anholt.net>
Date:   Thu Aug 29 17:00:09 2019 -0700

    dri: Use DRM_FORMAT_* instead of defining our own copy.
    
    We have only two defines that aren't from DRM_FORMAT_*: SARGB and
    SABGR.  Keep only those as __DRI_IMAGE_FOURCC and garbage collect the
    rest.
    
    While this header is also used from the X server, the X server doesn't
    use any __DRI_IMAGE enums.
    
    Reviewed-by: Eric Engestrom <eric.engestrom@intel.com>
    Reviewed-by: Kristian H. Kristensen <hoegsberg@google.com>

Comment 1 GitLab Migration User 2019-09-18 20:19:46 UTC

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/950.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.