<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv=Content-Type content="text/html; charset=us-ascii"> <meta name=Generator content="Microsoft Word 11 (filtered medium)">  <style>  </style>  </head> <body lang=EN-GB link=blue vlink=blue> <div class=Section1> Folks,<o:p></o:p> <o:p> </o:p> I am tantalisingly close to finding the problem I’ve got with the Xorg that I’ve built but I just need one little pointer in the right direction.<o:p></o:p> <o:p> </o:p> In my previous post I found that some functions in Xorg were not being found by driver modules trying to be linked in. In the example in the previous post one such function was xf86LoadKernelModule and another example shown in Xorg.0.log was a miPolyRectangle() function. So I went grep’ing and nm’img about until I could find out where these were missing from.<o:p></o:p> <o:p> </o:p> In the end I found that the Xorg I built in Vmware (and that worked) had these things listed in the output of “nm Xorg” but the one I built on the target system didn’t have them. Yet I found the miPolyRectangle in the libmi.a that had been built on both systems. So there was something preventing libmi.a getting linked in during the build of Xorg. Finally I compared the xserver/config.log on both systems and the difference there that explains why one works and one doesn’t is:<o:p></o:p> <o:p> </o:p> XWIN_LIBS='$(top_builddir)/fb/libfb.la $(top_builddir)/Xext/libXext.la $(top_builddir)/config/libconfig.la $(top_builddir)/Xi/libXi.la $(top_builddir)/xkb/libxkb.la $(top_builddir)/xkb/libxkbstubs.la $(top_builddir)/composite/libcomposite.la $(top_builddir)/damageext/libdamageext.la '<o:p></o:p> <o:p> </o:p> (which works)<o:p></o:p> <o:p> </o:p> Versus<o:p></o:p> <o:p> </o:p> XWIN_LIBS='$(top_builddir)/fb/libfb.la $(top_builddir)/mi/libmi.la $(top_builddir)/xfixes/libxfixes.la $(top_builddir)/Xext/libXext.la $(top_builddir)/config/libconfig.la $(top_builddir)/randr/librandr.la $(top_builddir)/render/librender.la $(top_builddir)/dbe/libdbe.la $(top_builddir)/glx/libglx.la $(top_builddir)/xkb/libxkb.la $(top_builddir)/xkb/libxkbstubs.la $(top_builddir)/composite/libcomposite.la $(top_builddir)/damageext/libdamageext.la $(top_builddir)/miext/damage/libdamage.la $(top_builddir)/miext/shadow/libshadow.la $(top_builddir)/Xi/libXi.la $(top_builddir)/os/libos.la'<o:p></o:p> <o:p> </o:p> (which does not work)<o:p></o:p> <o:p> </o:p> libmi appears in the second but not the first and something about this causes it not to be linked into the final Xorg that is built.<o:p></o:p> <o:p> </o:p> So what causes something to be listed or not listed on this line created by autogen.sh in the xserver directory? Presumably the autogen is finding something different between the two setups – but what?<o:p></o:p> <o:p> </o:p> Cliff<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <div> <div class=MsoNormal align=center style='text-align:center'> <hr size=2 width="100%" align=center tabindex=-1> </div> From: xorg-bounces@lists.freedesktop.org [mailto:xorg-bounces@lists.freedesktop.org] On Behalf Of Cliff Lawson Sent: 18 December 2008 17:59 To: xorg@lists.freedesktop.org Subject: RE: Building latest Intel support for 945G<o:p></o:p> </div> <o:p> </o:p> But then the first sign of trouble is:<o:p></o:p> <o:p> </o:p> (II) LoadModule: "dri"<o:p></o:p> (II) Loading /root/X/lib/xorg/modules/extensions//libdri.so<o:p></o:p> dlopen: /root/X/lib/xorg/modules/extensions//libdri.so: undefined symbol: xf86LoadKernelModule<o:p></o:p> (EE) Failed to load /root/X/lib/xorg/modules/extensions//libdri.so<o:p></o:p> (II) UnloadModule: "dri"<o:p></o:p> (EE) Failed to load module "dri" (loader failed, 7)<o:p></o:p> <o:p> </o:p> So the problem appears to be the fact that this is trying to link to xf86LoadKernelModule() that does not exist. So which bit of the jigsaw is it that should be providing this and which I must, therefore, have not got up to date yet?<o:p></o:p> <o:p> </o:p> Cliff Lawson<o:p></o:p> <o:p> </o:p> </div> </body> </html> <center>Scanned by MailDefender - managed email security from intY - www.maildefender.net</center> <center>Scanned by MailDefender - managed email security from intY - www.maildefender.net</center> No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.176 / Virus Database: 270.9.18/1850 - Release Date: 17/12/2008 19:21 <center>Scanned by MailDefender - managed email security from intY - www.maildefender.net</center> <center>Scanned by MailDefender - managed email security from intY - www.maildefender.net</center> No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.176 / Virus Database: 270.9.18/1850 - Release Date: 17/12/2008 19:21 <center>Scanned by MailDefender - managed email security from intY - www.maildefender.net</center>