Bug 60943 - /usr/include/xorg/fb.h(98): catastrophic error: #error directive: "GLYPHPADBYTES must be 4"
Summary: /usr/include/xorg/fb.h(98): catastrophic error: #error directive: "GLYPHPADBY...
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Other (show other bugs)
Version: git
Hardware: x86-64 (AMD64) Linux (All)
: medium blocker
Assignee: mesa-dev
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-16 05:37 UTC by Vinson Lee
Modified: 2014-09-06 22:22 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Vinson Lee 2013-02-16 05:37:59 UTC
mesa: f1ab67c13ab97f19c08d99c6ba101edc7d7b80e6 (master)

$ icc -v
icc version 13.1.0 (gcc version 4.6.0 compatibility)

$ scons
[...]
  Compiling src/gallium/state_trackers/xorg/xorg_composite.c ...
/usr/include/xorg/fb.h(98): catastrophic error: #error directive: "GLYPHPADBYTES must be 4"
  #error "GLYPHPADBYTES must be 4"
   ^

The Intel C Compiler defines the macro __x86_64__. It does not define __amd64__  or __amd64. This leads to a build failure as /usr/include/xorg/servermd.h does not check for __x84_64__.

servermd.h use to check for __x86_64__ and the check was removed in this commit.

http://cgit.freedesktop.org/xorg/xserver/commit/include/servermd.h?id=9719354ae04a41e9834ac9ba8fd9e895092ba4f1

commit 9719354ae04a41e9834ac9ba8fd9e895092ba4f1
Author: Adam Jackson <ajax@redhat.com>
Date:   Tue Jun 24 14:37:06 2008 -0400

    Check for __amd64__, not __x86_64__.
    
    Spiritual revert of 1fa4de80fcfc697b5e5879cc351fb3e9dbf6acbe.  Intel's C
    compiler claims to be gcc-compatible; if they're not defining the same
    macros as gcc then that's their bug, not ours.  Even if we were to do
    this aliasing we should do it once and for all in servermd.h.
Comment 1 Vinson Lee 2014-09-06 22:22:17 UTC
Fixed by "dix: Default GLYPHPADBYTES to 4" http://cgit.freedesktop.org/xorg/xserver/commit/include/servermd.h?id=17c3347f14822b9f7da4253c71f6ed51be2b38d1.


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.