I've just installed the 4.2.99.902pre CVS tree (as of Saturday night).
Installation generally went smoothly on my x86 Linux 2.4.20 box with a
Radeon 7500 QW and DVI flat panel. I built the tree with gcc 3.2.2
using '-O2 -march=pentium4 -fomit-frame-pointer' and haven't noticed
any instability, though I admit that I don't exercise the hardware 3D
acceleration at all and hence don't care about the known compilation
problem there with gcc 3.2.
I wanted to point out a few items that I hope make it into the release
notes or other conspicuous build documentation:
1. The current RELNOTES mention that, on systems with an
existing Freetype 2 library, one can use that library by
configuring with
#define BuildFreetype2Library NO
#define Freetype2Dir <appropriate directory>
(This section of RELNOTES seems to have been updated for .901).
I tried these options and found that 'make install' failed to
install fontconfig, Xft, or any Xft-using applications (in particular
xterm). Although 'make World' completed without error, 'make
install' attempted to recompile the offending libs and failed
because it couldn't find the relevant Freetype headers.
After studying the config/cf directory, I changed the options in
my host.def to
#define HasFreetype2 YES
#define Freetype2Dir <appropriate directory>
then rebuilt and reinstalled, and all was well.
Since HasFreetype2 = YES implies BuildFreetype2Library = NO, I'm
guessing that my bad experience was the result of a documentation
bug rather than a build bug, and that the release notes should be
corrected.
2. In the course of wading through config/cf, I noticed that one
could '#define HasZlib YES' to use the system's existing libz
instead of building a new static libz.a. I'd like to see this
option prominently documented in the release notes, as I suspect
most people would rather not link statically with a separate
version of libc (at least not after v1.1.3's security problems.)
3. I've been building with '#define HasPam YES' since the 4.1 days
to PAM-ify xdm, but I've never seen this option documented.
I originally found it by digging through the xdm sources.
Anyhow, I'm now happily using the resulting X installation.
Living dangerously in St. Louis,
Jeremy
PS - when building and installing fontconfig as part of a 'make World
/ make install', is it really necessary to replace the user's existing
/etc/fonts/fonts.conf? I'm happy that my old configuration (with my
preferred antialiasing settings) was backed up by the install process,
but I'd as soon the new config file were not installed at all if an
existing config is present.
_______________________________________________
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel
