cvs commit: hints XFree86_126.96.36.199.txt
timothy at linuxfromscratch.org
timothy at linuxfromscratch.org
Mon Feb 17 11:46:13 PST 2003
timothy 03/02/17 14:46:13
Modified: . XFree86_188.8.131.52.txt
Updated libxml, clarified use of symlinks.
Revision Changes Path
1.2 +48 -39 hints/XFree86_184.108.40.206.txt
RCS file: /home/cvsroot/hints/XFree86_220.127.116.11.txt,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- XFree86_18.104.22.168.txt 30 Jan 2003 00:48:49 -0000 1.1
+++ XFree86_22.214.171.124.txt 17 Feb 2003 19:46:13 -0000 1.2
@@ -9,7 +9,7 @@
SYNOPSIS: This hint explains how to obtain and install a beta-release
copy of XFree86 from CVS.
@@ -35,6 +35,16 @@
* * * Now, on to something more informative * * *
+ 2003-Feb-17, Updated Appendix B with new libxml version
+ Removed reference to old Bison dependency (yay!)
+ Updated information about the "core" cursor theme
+ Pushed forward the expiry since the XFree86 team did same
+ Clarified reasons for Freetype2 symlinks in /usr/X11R6
+ Acronym cleanups
@@ -121,17 +131,11 @@
This release of XFree86, presumably being more advanced than previous
versions, has a slightly larger number of things that should be installed
-before you attempt to compile it. The first one I'll mention is bison
-version 1.35. This is the version specified by LFS 4.0, which is what is
-cited at the top of this hint. If you use newer than this you'll need to
-dig through the BLFS mailing list archives to find a URL for a patch that
-will alter the source code of XFree86 to compensate for the syntax differences
-that will cause newer versions of bison to choke. If you don't do this, your
-build of XFree86 _will_ fail, complaining about errors involving files with a
-".y" filename ending. If you've built XFree86 from source before, you should
-be familiar with this routine.
+before you attempt to compile it. Mercifully, this release isn't hampered by
+ancient Bison syntax, so it doesn't really matter which version of Bison you
- The next thing you'll definitely need is CVS. The XFree86 page mentions a
+ The thing you will definitely need is CVS. The XFree86 page mentions a
utility called CVSup which you should avoid like the plague. It'll only take
a moment to install cvs if you don't already have it, and it requires no
knowledge or finesse to use. Once tarballs are released you won't need this
@@ -149,7 +153,7 @@
There are _no_ tarballs of the beta. I'll save you a *huge* amount of time
-by giving you strong warning _against_ attempting to build CVSup for use in
+by giving you another warning _against_ attempting to build CVSup for use in
obtaining the source as the XFree86.org site mentions. Just use plain old
cvs to get the source unless you _already_ have CVSup (and Modula-3) on your
system and working. Building Modula-3 and CVSup can make compiling the JRE
@@ -239,19 +243,17 @@
try, then congratulations are in order! If your build stops and complains
about undefined references to "inflate" or "deflate" then you need to re-read
the Appendices concerning how your library pre-requisites were installed. If
-your build stops and complains about any files ending in ".y" then you ignored
-or misread what was said at the top of Section II about bison and should read
-that again. If you get any other kind of errors, well, this is a beta release
-and isn't actually guaranteed to compile. Give it a few hours, re-run the cvs
-commands to see if updates to the source tree have been made, and then try
-again before posting to a mailing list about it.
+you get any other kind of errors, well... this is a beta release and is not
+actually guaranteed to compile. Give it a few hours, re-run the cvs commands
+to see if updates to the source tree have been made, and then try _a second
+time_ before posting to a mailing list about it.
Assuming everything compiled, now would be a good time to make backups of
-your important files, extra fonts, app-default customizations, kdm/gdm config,
+your important files, extra fonts, app-default customizations, KDM/GDM config,
etc. You might also want to just make a backup of everything you're about
to delete on a CDR or something but that's up to you. The one thing you
should definitely now do is remove _all_ your old XFree86 files. This means
@@ -325,18 +327,23 @@
working properly--you won't be happy if you find a problem when the machine is
trying to boot to runlevel 4 or 5.
- Admire the pretty red cursor pointer, which is the new 'redglass' cursor
-theme. If you'd like to go back to a white cursor pointer, you can change
-this by adding the following to your ~/.Xdefaults file:
- At the moment, redglass and whiteglass are the only two themes that ship
-with the new XFree86 (get cracking Gimp fiends!), and some searching of the
-web should turn up any further details about them you might need.
+ If you're wondering where the colored mouse pointers you've heard so much
+about went to, apparently all those radical changes have scared the XFree86
+devs, and to prevent rioting in the streets XFree86 once again defaults to
+the plain black-with-white-outlines set of cursors. The new redglass and
+whiteglass themes are still there, tho'. If you want them, add something akin
+to the following line to your ~/.Xdefaults file:
+ At the moment, redglass and whiteglass are the only two new themes that ship
+with the new XFree86 (get cracking, Gimp fiends!) that are meant for CRT/LCD
+displays, and some searching of the web should turn up any further details
+about them you might need.
Provided you're satisfied with the way your display is working, you should
-be able to switch your machine back to runlevel 4 or 5 now. Have fun!
+be able to reinstall GDM or KDM and switch your machine back to runlevel 4 or 5
+now. Have fun!
@@ -382,9 +389,9 @@
we're very sensibly preventing XFree86 from building it's own version of this
library, so we might as well cover a proper way to build it.
- Start by getting a copy of the source tarball for version 2.4.30 of libxml2
-which should have an md5sum of 1d40d3ead987c858805b70d2fe84a6c4. If you are
+ Start by getting a copy of the source tarball for version 2.5.3 of libxml2
+which should have an md5sum of c2ee2c99309a732d0e9c32e530241012. If you are
planning on using Gnome, you will need Python installed (2.2.2 works fine for
me) _before_ you build this library, since it will install some python
bindings which apparently some programs need to build. For this reason we
@@ -394,7 +401,7 @@
because more than just this library will have to be rebuilt if this is done
incorrectly the first time.
- You can use the shell script below to compile and install libxml2 2.4.30.
+ You can use the shell script below to compile and install libxml2 2.5.3.
Feel free to change the optimization levels to anything you'd like.
@@ -535,12 +542,14 @@
around them. One of the more inflexible ways that were attempted was to get
the freetype2 headers by forcing the compiler to search /usr/X11R6/include
alone for them, expecting to get Freetype 2.0.6/9. This _breaks_ when we
-disable XFree86 building it's own version of the library. Considering it was
-broken to begin with, and 2.1.3 can handle the function calls without any
-problems, if at some point in the future you have problems with this (which
-plagued the wxWindows library for some time) you can use the following shell
-script to put symlinks into /usr/X11R6 pointing to all the parts of Freetype2
-in /usr. This solves the problem and doesn't break anything in the process.
+disable XFree86 building it's own version of the library. Considering that
+old version of Freetype2 was broken to begin with, and 2.1.3 can handle the
+function calls without any problems, if at some point in the future you have
+problems building things that appear to be the result of this kind of madness,
+(which plagued the wxWindows library for some time) you can use the following
+shell script to put symlinks into /usr/X11R6 pointing to all the parts of
+Freetype2 in /usr. This solves the problem and doesn't break anything in the
Unsubscribe: send email to listar at linuxfromscratch.org
and put 'unsubscribe hints' in the subject header of the message
More information about the hints