This is the solution for the above GL library...
You have to compile mesa FIRST...
copy all your X11 includes to mesa source directory before compiling since mesa depends on it... then compile mesa... Then only you compile X11... Works for me...
But you will need a good glibc(patched or later version than 2.3.6)
else make will generate error when reaching xserver

No, it didn't say "no GL library", it was something like unable to find glx... I'll check it and give you the specifics once I get home. As for fonts, it starts out with about 5 or 6 of them saying that they weren't found and that they are now being removed from the list. Then it stops at the "fixed" font. When I looked at xorg.conf I couldn't find any references to the fixed font.

Yet, I did find out that Suse 10.2, while it still is Alpha, has X11R7. So I might just revert everything and update my version. I just have a quick question about which symlink I have to change. Do I just go to /usr/bin and do ln -s /usr/X11R6/bin X11 ?

Thanks for all your help.

Did you try copying only Mesa includes to X11 prefix directory first, instead of building the entire Mesa package? Because, consider this: If you were building from source, and you didn't have a previous X.org install... Where would you get the X11 includes from, to build Mesa? So, it *should* be possible to build BOTH x.org and mesa, without having to have one previously built/installed. As it is, if you build Mesa first, you're building against old includes which may be incompatible with the new x.org includes.

What you suggested (build Mesa first) is what I *actually* did, except that I rebuilt Mesa against the new X11R7 includes after completing the X.org build, and then re-installed the libs. The thing with this is, as I mentioned before, you can't do it if you don't have a previous X.org install, and anyway it's not an ideal solution. Besides, why the hell would you need the runtime-linked GL libraries in order to build X? It's not like the build process is drawing complex 3D shapes in fullscreen while you wait...

That'd be /usr/X11R7/bin Also, change symlink /usr/X11 to point to /usr/X11R7, backup /usr/X11R6 to an archive and make /usr/X11R6 a symlink to /usr/X11R7. Actually, it's probably better to find everything that points to X11R6 and make it point at /usr/X11 instead.. then make /usr/X11 point at /usr/X11R7.

About the fonts, I don't know what gives. I get 2 font errors, except it doesn't quit for me. On my old (stock Slackware X11R6.8) build, I got 1 font error, a different one. I suspect the other fonts aren't crucial, but the 'fixed' font is? Or perhaps it's just that *none* of your fonts are working, and the 'fixed' font is the last one.

Also, in your xorg.conf, have you verified that the fontpath options point to the X11R7 directory, instead of X11R6? About 'glx', I'm not sure; maybe the glx module didn't get built for some reason. Or, did you install a special driver for an nVidia card? I'm not sure if 'glx' is nvidia-specific or not... I'm pretty sure that not all of my xorg modules built, as it couldn't find the 'synaptics' module.

OBIOUSLY you downloaded the X11R7.1.1.0 package and did NOT download the 1.0.0 package... It DEPENDS on older X11r7-1.0.0 package...


First thing...X11 does NOT depend on Mesa... It is only the build script "makes" it depends on mesa... Your suggestion can't work... I have tried it before Mesa DEPENDS on X11 to compile... without X11... Mesa CANNOT compile...(based on my knowledge... and reference from BLFS )

I installed ONLY the proto headers of X11 THEN install mesa THEN install X using the script AFTER THAT only i recompile mesa...

Actually, these are errors that appear when X is initializing - not at build-time. Hence the reference to xorg.conf. Anyway, attempting to build X11R7.1 will quit immediately on a failed dependency of "X11" long before it gets to anything related to glx.

From here: Good work, sherlock. The X server requires Mesa, and if you don't have it, the X11 build script dies before the needed X proto headers are supplied to the build directory (i.e. you'll have to hunt around in the 300+ tarballs to find the headers you need to build Mesa).

Yes, I know Mesa depends on X11 headers to compile, and that's been the main point of my past few posts. However, due to the reasons above, X11 depends on Mesa headers to compile as well. This leaves in a deadlock: Both need the other one's headers. I suggested, since I know where the Mesa headers are, and I know where they need to go, that we start by copying the Mesa headers, and when the X11 build successfully completes, the X11 headers will magically appear where they need to be for Mesa to build.

Since I don't know which tarball the required X11 headers for Mesa are contained in (required are the GL headers by the way), and whether they're all contained in the same tarball or scattered through 10 seemingly unrelated ones, I decided this was not a feasible approach.

Now, why did you decide to recompile Mesa? Is this because you used the headers from the old X11R6 installation, which (if you read my previous posts) was the entire reason I suggested a different approach?

Ok, this is what it says:

...
(EE) Failed to load module "glx" (module does not exist, 0)
Could not init font path element /../.., removing from list (It does this about 5 times with different fonts)
...
Fatal Server error:
Could not open default font 'fixed'


Well I built it with no problems, so I'm guessing Mesa was fine. I dont understand why it doesn't stop at the glx error though. It's not an nVidia thing, I have an ATI card anyways (an AIW, thus is the reason why I want to upgrade X) I didn't install 7.1, that's for sure. I'll check the fontpath once I get home again.

I know this seems like the easy way out but it's just pretty hard to keep having to do this going from work to home, and I'm not that big of a fan of Suse nowadays... So I'm probably going to switch to FC5. I'm not that experienced to go into an alpha release and Suse10.2 is coming out in November. I wouldn't mind a switch.

Anyways, thanks for all your help and replies.

Yes, the nVidia thing was my mistake. GLX has nothing to with nVidia, as you can see here. I don't know why it wouldn't build, but I'll suggest a couple things:
1) Check your source tarballs, make sure you're not missing the source for the glx module.
2) Check if the glx module exists; I can't remember offhand, but the path is something like /usr/X11R7/lib/modules/(something).
3) If it exists, I don't know what's wrong.

I'm having the same problem with the 'synaptics' module for my laptop touchpad, same error. First, it didn't get built/installed even though it was included in the X11 source tarballs. I then built it using a source package I downloaded from (presumably) the official page, and put it in the correct directory(?), but X11 still gives the same error. Darn.

I managed to install ALL the proto headers(Its contained in a directory named proto... all we have to do is to untar it and install it)
Yes... IF you are using the scripts... yes it dies... BUT... If you compile the tarballs by hand(Ignore GLX support FIRST) then it works... Which ULTIMATELY says... X11 does not depends on Mesa... (My personal opinion though ) And like i have said... The X11R7 headers is in proto directory... you DON'T need to HUNT the headers

It is not that i used old X11R6 headers... I used X11R7 proto headers... But IMHO... Since Mesa depends on X11... then we should reinstall the package AFTER its dependency is met... Just an opinion though...(Which i did)

>>I managed to install ALL the proto headers(Its contained in a directory named proto... all we have to do is to untar it and install it)

Fair enough; then in this case, it looks like your approach (build Mesa first) is better, since it gives the advantage of using Mesa's "make install" to copy the Mesa includes, in case you get mixed up with the source directory structure etc... I downloaded the 'everything' directory for X11R7, which (I hope) explains my ignorance of the proto directory

I did download the everything directory too... But it seem that downloading the modular based directory makes more sense to me later even downloading is a bit harder

I am still wondering which(X11R7 and Mesa) package should be installed first since both depends on each other...If you've got some article... Please share it here...Thank you Doing more research

Found another problem with the approach I suggest...
X11 WON'T install ALL headers with just the proto directory... there are still headers missing...
Hunter2's solution seems to be better... Trying it out now...
(this solution is still in progress , so there may still be errors)
-install X11 using script UNTIL it gets to the glXNoPro....
-install Mesa using X11 headers installed just now
-continue installing X11 by modifying the buildscript

Any news? Did it work, or is it still building? (And what changes to buildscript? Did you copy the Mesa headers first?)

Well... It did work
-install X11 using script UNTIL it gets to the glXNoPro....(Something similar to glxNo blah blah blah...., i forgot what really is the error)
-install Mesa using X11 headers installed just now (copy over the /usr/X11R7/include to your Mesa source then compile)
-continue installing X11 by modifying the buildscript...(You can leave the script to default but it will take more time)

Hope that helps

PS: No major changes to the script... except that... adding a few # infront of some build command IFF you want