Bug 72126 - xorg-server-1.14.4 fails to compile in mips64, due to casting wrong size int to pointer
Summary: xorg-server-1.14.4 fails to compile in mips64, due to casting wrong size int ...
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/General (show other bugs)
Version: unspecified
Hardware: Other Linux (All)
: medium normal
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-28 15:25 UTC by Cherry Mui
Modified: 2014-07-19 13:52 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
build log (tail lines) (5.63 KB, text/plain)
2013-11-28 15:25 UTC, Cherry Mui
no flags Details
xorg-server-1.14.4-mips64-uintptr_t.patch (608 bytes, patch)
2013-11-28 15:27 UTC, Cherry Mui
no flags Details | Splinter Review

Description Cherry Mui 2013-11-28 15:25:56 UTC
Created attachment 89958 [details]
build log (tail lines)

xorg-server-1.14.4 fails to compile on mips64el (loongson2e). it is due to casting unsigned int to pointer, which are of different sizes on mips64. build.log is attached.

changing unsigned int to uintptr_t solves the problem on my machine. hope the patch does not break other architectures.

The same problem happens on other versions of xorg-server, e.g. 1.14.3, or 1.14.99.903.
Comment 1 Cherry Mui 2013-11-28 15:27:24 UTC
Created attachment 89959 [details] [review]
xorg-server-1.14.4-mips64-uintptr_t.patch
Comment 2 Bernd Kuhls 2014-04-13 19:20:40 UTC
The bug still exists in xorg-xserver 1.15.0 and is fixed by the attached patch.
Comment 3 Bernd Kuhls 2014-04-15 05:06:47 UTC
The bug still exists in xorg-xserver 1.15.1 and is fixed by the attached patch.
Comment 4 Chí-Thanh Christopher Nguyễn 2014-06-05 12:59:05 UTC
This might be fixed by http://cgit.freedesktop.org/xorg/xserver/commit/?id=19e5a13970ad9d440c0789395e94931429ef4fbb
Comment 5 Bernd Kuhls 2014-07-19 13:52:59 UTC
Bug is fixed in xorg server 1.16.0, thanks!


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.