Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 175528 - xorg-server-1.3.0.0 ebuild fails in rrmode.c
Summary: xorg-server-1.3.0.0 ebuild fails in rrmode.c
Status: RESOLVED DUPLICATE of bug 175452
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High major (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-22 07:12 UTC by Robert Bradbury
Modified: 2007-04-22 07:15 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Bradbury 2007-04-22 07:12:03 UTC
In subdirectory "work/xorg-server-1.3.0.0/randr":
one gets the error:
rrmode.c: In function 'ProcRRCreateMode':
rrmode.c:311: error: 'xRRCreateModeReply' has no member named 'pad0'

The declaration at fault is:
  xRRCreateModeReply  rep;

This seems to be due to an include of:
  /usr/include/X11/extensions/randrproto.h
where "xRRCreateModeReply" has members pad1 thru pad5 but no pad0.

The date on rrmode.c is 19 Feb 2007 which is after the X11 7.2 release date of ~15 Feb 2007.  So it would appear that the sources in the distributed package may be inconsistent.

There is no "randrproto.h" in the entire extracted ebuild tree so it is either missing from the distribution or is not being generated properly during the ebuild.



Reproducible: Always

Steps to Reproduce:
1. add "xorg-xserver ~x86" to /etc/portage/package.keywords
2. emerge xorg-xserver


Actual Results:  
rrmode.c fails to compile as documented.


I am puzzled as to why one would be emerging xorg-server 1.3.0.0 if one has an x11-base/xorg-x11-7.2 installed unless xorg-server is a subset of xorg-x11-7.2.

I may have a poor understanding of the relationship between xorg-server and xorg-x11.
Comment 1 Vlastimil Babka (Caster) (RETIRED) gentoo-dev 2007-04-22 07:15:26 UTC

*** This bug has been marked as a duplicate of bug 175452 ***