|Summary:||Circular build dependency between XFree and Mesa|
|Product:||[Retired] Red Hat Linux||Reporter:||Pawel Salek <pawsa>|
|Component:||Mesa||Assignee:||Bernhard Rosenkraenzer <bero>|
|Status:||CLOSED DEFERRED||QA Contact:||Aaron Brown <abrown>|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2001-03-23 05:23:03 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
Description Pawel Salek 2001-03-21 16:15:13 UTC
XFree requires Mesa-devel to build but one of Mesa files refers to X11/Xdefs.h file from XFree-devel. Reproducible: Always Steps to Reproduce: 1. try boostraping Mesa or XFree from sources. I guess one possible solution is to build them together, but is it the best one?
Comment 1 Bernhard Rosenkraenzer 2001-03-21 16:27:12 UTC
Yes, the Mesa package should be merged with the XFree86 package in the long run.
Comment 2 Mike A. Harris 2001-03-23 05:22:58 UTC
This sucks. Unfortunately, the only real solution I think is to marry Mesa into XFree86 as Bero suggests, and it is far too late to do this at this point in time. Alternatively we could include the XFree files in the Mesa code with the patch that is already there. Bero, can you update the Mesa package's main XFree86 tarball to also include the headers from XFree 4.0.3 and use them? The comment at the top of the specfile should be updated also so that when XFree gets updated the new patch will get created that includes the necessary stuff from XFree86. I think this is the best solution right now, as the only other one would be removing the dependancy on Mesa from XFree86 which will result in lots of bug reports from people running mismatched X and Mesa. The 4.0.3 code is unchanged from the last Mesa update so nothing else weird should change.
Comment 3 Bernhard Rosenkraenzer 2001-06-01 15:10:48 UTC
Setting to deferred until the packages have been merged.