no x

[Daniel Stone]

On Sun, Feb 19, 2006 at 08:26:25AM -0800, Stuart Kreitman wrote:
> Some fishy messages in .log file. They ought to be flagged as (EE).
> Are there errors in the X build tree?
> 
> >(II) Loading sub module "GLcore"
> >(II) LoadModule: "GLcore"
> >(II) Loading /usr/X11R6/lib/modules/extensions/libGLcore.a
> >Skipping "/usr/X11R6/lib/modules/extensions/libGLcore.a:m_debug_clip.o":  
> >No symbols found
> >Skipping "/usr/X11R6/lib/modules/extensions/libGLcore.a:m_debug_norm.o":  
> >No symbols found
> >Skipping "/usr/X11R6/lib/modules/extensions/libGLcore.a:m_debug_xform.o":  
> >No symbols found

All this means is that m_debug_{clip,norm,xform}.c were built, but
exported no symbols, by virtue of looking something like this:
#ifdef DEBUG
...
#endif

.a files simply being an amalgamation of object files, this never gets
optimised away.

> >(II) Loading sub module "fb"
> >(II) LoadModule: "fb"
> >(II) Loading /usr/X11R6/lib/modules/libfb.a
> >Skipping "/usr/X11R6/lib/modules/libfb.a:fbmmx.o":  No symbols found

As above.

> >(II) LoadModule: "xtt"
> >(WW) Warning, couldn't open module xtt
> >(II) UnloadModule: "xtt"
> >(EE) Failed to load module "xtt" (module does not exist, 0)

This is problematic, if you care about core TrueType fonts.

> >(II) Primary Device is: PCI 01:00:0
> >(WW) RADEON: No matching Device section for instance (BusID PCI:1:0:1) 
> >found

This is because Radeons export two PCI IDs (one for each head), as
required by some versions of Windows.  Since we don't have that
requirement, we don't attempt to do anything useful with the secondary
ID.