DSL Tips and Tricks :: A quick guide on compiling XOrg 7.0 on DSL

I re-ran the MesaLib compilation with "make linux-dri-x86" and used the -m switch in the build_from_tarballs script.

A message came up in the compilation of xorg-server about finding mesa sources and glx so I guess I'm on the right track - I ran out of ramdisk at some point in building fonts so it's hard to tell for sure.

I guess I'll have to do the full compilation in stages making unc's as I go along or perhaps build to /opt with a persistant opt...

wow... you've been doing all of this in swap? At the very least, I'd recommend a symlink /opt/xorg72 to some location on a hard disk.

Well, not exactly in swap - although the cpu is a 267MHz Pentium II, it has 512MB RAM plus 1GB swap. With a frugal toram hd install, this leaves me +/- 400MB for /home according to torsmo.

I like the idea of the /opt/xorg72 symlink, maybe I'll try that next...

I ran the build_from_tarballs script again using /opt/xorg72 with a symlink to hd - the compile ran without error, but the first thing I noticed is that X will only run as root. When I compiled to /usr/local, X would run as user DSL.

From this excerpt from the compile checks, it looks like the hardware acceleration built OK - maybe the second line explains why X will only run as root (unfortunately I don't keep the output from the /usr/local build):

Code Sample

Building xserver module component xorg-server-1.2.0...
...
checking to see if we can install the Xorg server as root... yes
...
checking for XLIB... yes
checking for GL... yes
Creating destination directories for mesa module ... DONE
Creating destination directories for glx module ... DONE
Checking that the source files exist for mesa module ... DONE
Checking that the source files exist for glx module ... DONE
Deleting existing files for mesa module ... DONE
Deleting existing files for glx module ... DONE
Linking files for mesa module ... DONE
Linking files for glx module ... DONE
...

As ^hats^ says, the X autoconfig fails with a framebuffer error - even though it correctly identifies my graphics card, it then ignores it. The xorgcfg utilty does the same thing and managed to wrongly setup a 3-button PS/2 mouse.

Anyway, after playing around with the xorg.conf file, things seem to work and (according to Xorg.0.log) the glx and dri modules load.

I guess I need to solve the problem of why X will only run as root from /opt/xorg before I can think about making an extension - maybe this is due to the symlink to hd and the permissions on the hd?

Is it possible to make a uci extension after compiling to /usr/local?

It looks like you've got the same root problem - which prevented me from creating an extension in the first place.

Afaik if it's run with root privs, it'll set permissions on executable files with something like 4755. But from my previous finds, there's a more in-depth problem (the fb console) which I'm not sure of.

Did you not install to /opt/xorg72 using the build script? If so, everything should be able in there, and you can just with that.

Next Page...
original here.