FireBurn/Overlay

mesa can not find xorg even though 1.14.1 is installed

Asphxiated opened this issue · 5 comments

Asphxiated commented

llvm, and clang compile and install just fine on my system but when I try to compile the new mesa files during configure it says:

checking for XORG: no
(xorg-server) packsage not found. >=1.6.0 required

All other packages that require X/xorg compile fine.... I even add the X librarys to the environmental variable XORG_LIBS and it still wont find them....

Maybe you can offer come help, does mesa look in some non-standard library path now?

-Asphyxiated

FireBurn commented

Are you using the xorg or xa state tracker?
On 11 Jun 2013 05:25, "Bobby" notifications@github.com wrote:

llvm, and clang compile and install just fine on my system but when I try
to compile the new mesa files during configure it says:

checking for XORG: no
(xorg-server) packsage not found. >=1.6.0 required

All other packages that require X/xorg compile fine.... I even add the X
librarys to the environmental variable XORG_LIBS and it still wont find
them....

Maybe you can offer come help, does mesa look in some non-standard library
path now?

-Asphyxiated

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/21
.

FireBurn commented

OK I've pushed a commit that only enables the xorg state tracker on the native abi - this should fix your issue

Out of interest what are you using the xorg state tracker for?

Asphxiated commented

Forgive my ingorance but if you by xorg state tracker you mean that the xorg use flag on mesa enables this 'xorg state tracker' and is not required, I did not know this. I thought that it was required to use the xorg libraries, as other use flags do for variuos features in other programs. If this is not what you speak of at all I am apologize...

Asphxiated commented

Oh and it does work now, thank you very much!

FireBurn commented

Yes its a badly named use flag. I think radeonsi might need it tho so it
needed fixing anyway. Cheers
On 11 Jun 2013 08:37, "Bobby" notifications@github.com wrote:

Oh and it does work now, thank you very much!

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/21#issuecomment-19247003
.