Newsgroups: comp.windows.x.i386unix,comp.unix.pc-clone.32bit,comp.unix.bsd,comp.windows.x,comp.answers,news.answers
Path: news1.ucsd.edu!ihnp4.ucsd.edu!munnari.OZ.AU!news.mel.connect.com.au!news.mira.net.au!Germany.EU.net!howland.reston.ans.net!gatech!news.mathworks.com!uhog.mit.edu!rutgers!utcsri!info.ecf!steve
From: steve@ecf.toronto.edu (Steve Kotsopoulos)
Subject: X on Intel-based Unix Frequently Asked Questions [FAQ]
Summary: X options for Intel-based Unix (SYSV/386, BSD, Linux, Mach)
Originator: steve@ecf.toronto.edu
Sender: news@ecf.toronto.edu (News Administrator)
Message-ID: <Dtx92y.ADu@ecf.toronto.edu>
Approved: news-answers-request@MIT.Edu
Date: Tue, 2 Jul 1996 15:16:10 GMT
Expires: Thu, 1 Aug 1996 00:00:00 GMT
X-Nntp-Posting-Host: skule.ecf
Reply-To: steve@ecf.toronto.edu
Organization: University of Toronto, Engineering Computing Facility
Followup-To: poster
Lines: 667
Xref: news1.ucsd.edu comp.windows.x.i386unix:20371 comp.unix.pc-clone.32bit:9650 comp.windows.x:56820 comp.answers:15560 news.answers:62088
Archive-name: x-faq/Intel-Unix-X-faq
Last-modified: 21 June 1996
This article includes answers to:
I) What options do I have for X software on my Intel-based Unix system?
Free options
Commercial options
II) What is XFree86 and where do I get it?
What is XFree86?
What OSs are supported?
What video hardware is supported?
Who else supports accelerated boards?
What other hardware or software requirements are there?
Where can I get source and binaries for XFree86?
IV) What general things should I know about running XFree86?
Installation directories
Configuration files
Determining VGA dot clocks and monitor modes
Rebuilding/reconfiguring the server from the link kit
V) What OS-specific things should I know about running XFree86?
SVR4
SVR3
BSD
Linux
Mach
VI) What things should I know for building XFree86 from source?
VII) Is there anything special about building clients with XFree86?
BSD compatibility library
ANSICCOPTIONS
VIII) Where to get more information
The latest version of this article is available by anonymous
ftp from ftp.x.org:/contrib/faqs/Intel-Unix-X-faq.Z
This article does NOT include answers to general X questions, since they
are already covered by the X FAQ that is regularly posted by David B. Lewis
<faq%craft@uunet.uu.net>.
For information on X packages for DOS systems, consult the (PC)NFS FAQ
available from seagull.rtd.com:/pub/tcpip/pcnfs.FAQ.v1.2.Z
If you have anything to add or change on this FAQ just let me know.
(especially if you had a problem that someone else was able to help you with)
Send changes to steve@ecf.toronto.edu, please put 'FAQ' somewhere
in the subject line so that my mail filter will put it in the correct folder.
Please do not ask me questions that are not answered in this FAQ. I don't
have time to respond to these individually. Instead, post your question
to the net, and send me the question and answer together when you get it.
Frequently Asked Questions About X on Intel-based Unix (with answers)
=====================================================================
I) What options do I have for X software on my Intel-based Unix system?
Subject: Free options
The best option is XFree86, which is an enhanced version of X386 1.2.
Any other version of X386 will be more difficult to compile.
Information on how to obtain it is listed below.
X386 is the port of the X11 server to System V/386 that was done by
Thomas Roell (roell@xinside.com). It supports a wide variety of SVGA boards.
There are 2 major free versions: X386 1.1 is based on X11R4,
X386 1.2 is included in MIT's X11R5 distribution (ie. you
don't need to patch it into the MIT source any more).
Several other options are available for people running NeXTSTEP on
i486 and Pentium hardware. Information on mouseX, Cub'X and Co-Xist
is available via anonymous ftp from cs.orst.edu in /pub/next/XNeXT.
Subject: Commercial options
1) Metro Link
4711 North Powerline Road
Fort Lauderdale, FL 33309
(305) 938-0283
Fax: (305) 938-1982
email: sales@metrolink.com
http://www.metrolink.com/
Summary: OS: AT&T System V 3.2, Interactive, Linux, LynxOS, QNX,
SCO ODT, SCO UNIX, Solaris x86, System V 4.0,
System V 4.2, UnixWare 1.1/2.0, Venix
HW: Many graphics cards including those based on:
VGA, 8514, S3, ATI Mach 8/32/64, ET3000, ET4000,
Matrox MGA, Cirrus Logic, Western Digital
including boards from: ATI, Diamond, Matrox,
Number Nine, Orchid, Pixelworks, Trident.
Other: Motif, XIE Imaging Extension, Xv Video Extension,
Audio Drivers, Multi Media Tools
2) X Inside Incorporated
1801 Broadway, Suite 1710
Denver, CO 80202
+1(303)298-7478, (800)XIN-SIDE [800-946-7433]
Fax: +1(303)298-1406
email: sales@xinside.com
Department: Automated Information Services
Email: info@xinside.com
Web: http://www.xinside.com/
Anon-FTP: ftp.xinside.com
Mail lists: majordomo@xinside.com
Summary: OS: The server comes in two packages: one for BSDI,
FreeBSD, Linux, or NetBSD and one for ISC, SCO,
Solaris/X86 or Unixware. The Unixware set actually
should work for most SVR4 based Unix platforms.
HW: Over 356 graphics adapters from over 40 vendors,
almost any monitor.
Other: Extensions include MIT-SCREEN-SAVER, MIT-SHM,
Multi-Buffering, SHAPE, XIdle, XsightExtension,
Multihead, XVideo, OpenGL (beta testing now).
Motif 2.0 is shipping for Linux and BSDI BSD/OS.
See web site for comprehensive list of supported boards and
a demo version of the server that is available for download.
The X Inside server, known as 'accelerated X', is bundled into the
Caldera implementation of Linux, and with BSDI's BSD/os.
3) The Santa Cruz Operation, Inc.
p.o. box 1900
Santa Cruz, California 95061
(408) 425 7222, (800) SCO UNIX,
FAX: (408) 458 4227
email: info@sco.com
Summary: OS: ODT 1.1, ODT 2.0, ODT 3.0
HW: X11R5 server support for SVGA, 8514/A, S3, TMS340x0,
GD5426, P9000, ET4000/W32, Mach32, WD90C33, 86C801,
86C805, 86C928, WD90C31, XGA2, QVision, misc. localbus
video systems (see Hardware Compatibility Handbook
for actual card vendors).
Other: Motif
4) Answer Software & Consulting
p.o. box 14171
Columbus, Ohio 43214
614-263-XLAB
email: sales@x4coher.com
Summary: OS: Coherent 4.0.1r72 or greater
HW: works with any VESA compliant video
5) OpenWindows (shipped as part of the Solaris for x86 OS)
SunSoft Inc.
2550 Garcia Ave.
Mountain View, CA 94043
Phone: 415-960-3200
Summary: OS: Solaris for x86, SunSoft's version of SVR4
HW: ATI, Cirrus, S3, 8514, VGA, XGA, Matrox, Weitek, etc.
Complete list of supported cards available by
mailing x86hcl@sun.com.
Other: X11R5 clients, XView, OLIT, DeskSet, Adobe Display
PostScript, XGL (3D Graphics), XIL (Imaging)
6) Mark Williams Company
Mark Williams Company went out of business about Feb 2 1995.
Check comp.os.coherent for details and flamewars.
NOTE: Other commercial vendors (including OS vendors describing
bundled software) are welcome to submit summary information
such as the above.
II) What is XFree86 and where do I get it?
Subject: What is XFree86?
XFree86 is a port of X11R6 that supports several versions of Intel-
based Unix and Unix-like operating systems. This release consists of
new features and performance improvements as well as many bug fixes.
The release is available as source patches against the X Consortium
X11R6 code, as well as binary distributions for many architectures.
What's new in XFree86 3.1.2?
The following items have been added since XFree86 3.1.1 was released
in January 1995:
1. XFree86 3.1.2 includes the X Consortium's recently released
public patch (fix-12).
2. Support for the S3 968 and 868 chipsets.
3. Support in the S3 server for the IBM RGB 5xx series RAMDACs.
4. Support in the S3 server for the STG1703 RAMDAC.
5. Support in the S3 server for the SC1148{2,3,4,5,7,9} RAMDACs at
15bpp.
6. XGA-2 support for the AGX server.
7. 16bpp support for the AGX server.
8. Bug fixes and enhancements to the Mach64 server.
9. Bug fixes for the Mach32 server.
10. Improved performance for the P9000 server.
11. Bug fixes for the VGA16 and Mono servers.
12. A new Xserver extension (and client) to allow interactive video
mode tuning.
13. Improved VESA DPMS screensaver support for some servers.
14. New chipset support for the SVGA server. This includes the ARK
Logic ARK1000PV and ARK2000PV and RealTek RTG3106.
15. Support for the WD90C24 series of laptop chipsets.
16. Updates to the SVGA vgawonder driver.
17. Improved 3 Button mouse emulation.
18. Support for LynxOS AT versions 2.2.1 and 2.3.
19. Support for Unixware 2.0.
20. Support for BSD/OS 2.0.
21. Support for Linux/ELF.
22. Workarounds for some NumLock problems.
23. Cyrillic fonts (using KOI8-R encoding) from Cronyx Ltd.
Plus a lots of other small items. Refer to the CHANGELOG file in the
source distribution for full details.
Also included are a tutorial on monitor timing by Eric Raymond, and the
current X386 mode database and a sample xdm configuration by David Wexelblat.
Subject: What OSs are supported?
SVR4.0:
o Esix: 4.0.3A, 4.0.4, 4.0.4.1
o Microport: 2.2, 3.1, 4.1, 4.2
o Dell: 2.1, 2.2, 2.2.1
o UHC: 2.0, 3.6
o Consensys: 1.2
o MST: 4.0.3 (Load 2.07 and Load 3.02)
o ISC: 4.0.3
o AT&T: 2.1, 4.0
o NCR: MP-RAS
o SunSoft: Solaris x86 2.1, 2.4
SVR4.2:
o Consensys
o Novell UnixWare
SVR3:
o SCO: 3.2.2, 3.2.4
o ISC: 3.0, 4.0, 4.1
Others:
o NetBSD 1.0
o FreeBSD 1.1.5.1, 2.0, 2.0.5
o BSD/386 1.1, BSD/OS 2.0
o Mach 386
o Linux
o Amoeba
o Minix-386
o LynxOS AT 2.2.1, 2.3
Note that Esix 3.2D is not supported yet, but anyone should feel
free to submit patches. If you are interested in tackling this,
send mail to xfree86-core@xfree86.org
Subject: What video hardware is supported?
At this time, XFree86 3.1.2 supports the following accelerated chipsets:
8514/A
(and true clones)
ATI
Mach8, Mach32, Mach64
Cirrus
CLGD5420, CLGD5422, CLGD5424, CLGD5426, CLGD5428, CLGD5429,
CLGD5430, CLGD5434
S3 86C911, 86C924, 86C801, 86C805, 86C805i, 86C928, 86C864, 86C964,
86C732, 86C764, 86C868, 86C968
Western Digital
WD90C31, WD90C33, WD90C24A
Weitek
P9000
IIT
AGX-014, AGX-015, AGX-016
IBM
XGA-2
Tseng
ET4000/W32, ET4000/W32i, ET4000/W32p
The Cirrus, Western Digital and Oak accelerators are supported in the
SVGA server; the other chipsets each have their own server. A list of
some cards which the accelerated servers have been tested is included
in the files AccelCards, Devices, the xf86config utility's Cards
database, and some of the chipset-specific README files. They may
well work on other cards, but we cannot guarantee it.
In addition, the following SVGA chipsets are supported:
Tseng
ET3000, ET4000AX, ET4000/W32
Western Digital/Paradise
PVGA1
Western Digital
WD90C00, WD90C10, WD90C11, WD90C24, WD90C24A, WD90C30,
WD90C31,WD90C33
Genoa
GVGA
Trident
TVGA8800CS, TVGA8900B, TVGA8900C, TVGA8900CL, TVGA9000,
TVGA9000i, TVGA9100B, TVGA9200CX, TVGA9320, TVGA9400CX, TVGA9420
ATI
18800, 18800-1, 28800-2, 28800-4, 28800-5, 28800-6, 68800-3,
68800-6, 68800AX, 68800LX, 88800CX, 88800GX
NCR
77C22, 77C22E, 77C22E+
Cirrus Logic
CLGD5420, CLGD5422, CLGD5424, CLGD5426, CLGD5428, CLGD5429,
CLGD5430, CLGD5434, CLGD6205, CLGD6215, CLGD6225, CLGD6235,
CLGD6410, CLGD6412, CLGD6420, CLGD6440
Compaq
AVGA
OAK
OTI067, OTI077, OTI087
Avance Logic
ALG2101, ALG2228, ALG2301, ALG2302, ALG2308, ALG2401
Chips & Technology
65520, 65530, 65540, 65545
MX MX68000, MX680010
Video 7/Headland Technologies
HT216-32
ARK Logic
ARK1000PV, ARK2000PV
RealTek
RTG3106
All of the above are supported in both 256 color and monochrome modes,
with the exception of the Advance Logic, MX, Chips & Technology, Video
7, ARK, RealTek chipsets, which are only supported in 256 color mode.
Refer to the chipset-specific README files (currently for Cirrus,
Tseng, Western Digital, ATI, ARK, Trident, Oak and Video 7) for more
information about using those chipsets.
The monochrome server also supports generic VGA cards, using 64k of
video memory in a single bank, the Hercules monochrome card, the
Hyundai HGC1280, Sigma LaserView, Visa and Apollo monochrome cards.
On the Compaq AVGA, only 64k of video memory is supported for the
monochrome server, and the GVGA has not been tested with more than
64k.
The VGA16 server supports memory banking with the ET4000, Trident,
ATI, NCR, OAK and Cirrus 6420 chipsets allowing virtual display sizes
up to about 1600x1200 (with 1MB of video memory). For other chipsets
the display size is limited to approximately 800x600.
Note: The Diamond SpeedStar 24 (and possibly recent SpeedStar+) boards
are NOT supported, even though they use the ET4000. The Stealth 32
which uses the ET4000/W32p is also not fully supported. The Weitek
9100 and 9130 chipsets are not supported (these are used on the
Diamond Viper Pro and Viper SE boards). Most other Diamond boards
will work with this release of XFree86. Diamond is now actively
supporting The XFree86 Project, Inc.
The Trident TGUI9440 series of chips is not yet supported, but we are
working on this.
Some types of the Mach64 cards are not fully supported. Refer to
README.Mach64 for details.
Subject: Who else supports accelerated boards?
This support is available in commercial products several vendors.
See the "Commercial options" section for details.
Subject: What other hardware or software requirements are there?
Obviously, a supported video board and OS are required. To run
X efficiently, 8-12MB of real memory should be considered a minimum.
The various binary releases take 10-40MB of disk space, depending
on the OS (e.g. whether or not it supports shared libraries).
To build from sources, at least 80MB of free disk space will
be required, although 120MB should be considered a comfortable
lower bound. If you are VERY tight on space, look into tinyX.
Subject: Where can I get source and binaries for XFree86?
Source patches are available to upgrade X11R6 PL12 from the X
Consortium to XFree86 3.1.2. They and binaries for many OSs are
available via anonymous FTP from:
o ftp.XFree86.org:/pub/XFree86/3.1.2
<ftp://ftp.XFree86.org/pub/XFree86/3.1.2>
and the following mirror sites:
o North America:
+ XFree86.cdrom.com:/pub/XFree86
<ftp://XFree86.cdrom.com/pub/XFree86> (source and binaries)
+ ftp.rge.com:/pub/X/XFree86/3.1.2
<ftp://ftp.rge.com/pub/X/XFree86/3.1.2> (source and
binaries)
+ ftp.iastate.edu:/pub/XFree86/XFree86-3.1.2
<ftp://ftp.iastate.edu/pub/XFree86/XFree86-3.1.2> (source
patches and NetBSD binaries)
(Also via AFS:
/afs/iastate.edu/public/ftp/pub/XFree86/XFree86-3.1.2)
+ tsx-11.mit.edu:/pub/linux/packages/X11/XFree86-3.1.2
<ftp://tsx-11.mit.edu/pub/linux/packages/X11/XFree86-3.1.2>
(Linux binaries and source)
+ ref.tfs.com:/pub/mirrors/XFree86
<ftp://ref.tfs.com/pub/mirrors/XFree86> (source patches and
FreeBSD binaries)
+ ftp.eecs.umich.edu:/BSD/XFree86/3.1.2
<ftp://ftp.eecs.umich.edu/BSD/XFree86/3.1.2> (source and
binaries)
o Europe:
+ fvkma.tu-graz.ac.at:/pub/X11/XFree86/3.1.2 <ftp://fvkma.tu-
graz.ac.at/pub/XFree86/3.1.2> (source and binaries)
+ ftp.fee.vutbr.cz:/pub/XFree86/3.1.2
<ftp://ftp.fee.vutbr.cz/pub/XFree86> (source patches and
binaries)
+ ftp.gwdg.de:/pub/xfree86/XFree86/3.1.2
<ftp://ftp.gwdg.de/pub/xfree86/XFree86/3.1.2> (source and
binaries)
+ ftp.uni-erlangen.de:/pub/Linux/MIRROR.xfree86/3.1.2
<ftp://ftp.uni-erlangen.de/pub/Linux/MIRROR.xfree86/3.1.2>
(source patches and Linux binaries)
+ ftp.uni-stuttgart.de:/pub/X11/Xfree86/3.1.2 <ftp://ftp.uni-
stuttgart.de/pub/X11/Xfree86/3.1.2> (source and binaries)
+ ftp.funet.fi:/pub/X11/XFree86/3.1.2
<ftp://ftp.funet.fi/pub/X11/XFree86/3.1.2> (source and
binaries)
+ ftp.calvacom.fr:/pub/unix/X/XFree86
<ftp://ftp.calvacom.fr/pub/unix/X/XFree86> (source and
binaries)
+ ftp.ibp.fr:/pub/X11/XFree86/XFree86-3.1.2
<ftp://ftp.ibp.fr/pub/X11/XFree86/XFree86-3.1.2> (source and
binaries)
+ ftp.laas.fr:/pub/netbsd/XFree86-3.1.2
<ftp://ftp.laas.fr/pub/NetBSD/XFree86-3.1.2> (NetBSD binaries
only)
+ ftp.pvv.unit.no:/pub/XFree86/3.1.2
<ftp://ftp.pvv.unit.no/pub/XFree86/3.1.2> (source and
binaries)
o Asia/Australia:
+ x.physics.usyd.edu.au:/pub/XFree86/3.1.2
<ftp://x.physics.usyd.edu.au/pub/XFree86/3.1.2> (source and
binaries)
+ ftp.iij.ad.jp:/pub/X/XFree86/XFree86/3.1.2
<ftp://ftp.iij.ad.jp/pub/X/XFree86/XFree86/3.1.2> (source and
binaries)
+ ftp.sf.co.kr:/pub/XFree86/3.1.2
<ftp://ftp.sf.co.kr/pub/XFree86/3.1.2> (source and binaries)
+ ftp.nectec.or.th:/pub/mirrors/XFree86/3.1.2
<ftp://ftp.nectec.or.th/pub/mirrors/XFree86/3.1.2> (source
patches and binaries)
Please use the closest mirror site where possible.
For the rest of this FAQ, these archive sites will be called $FTP.
Refer to the README file under the specified directory for information
on which files you need to get to build your distribution.
Ensure that you are getting XFree86 3.1.2 - some of these sites may
archive older releases as well. Each binary distribution will contain
a README file that describes what files you need to take from the
archive, and which compile-time option selections were made when
building the distribution.
IV) What general things should I know about running XFree86?
Subject: Installation directories
The top-level installation directory is specified by the ProjectRoot
(/usr/X11R6, by default) variable in config/site.def. Binaries, include
files, and libraries are installed in $ProjectRoot/{bin,include,lib}.
This can be changed when rebuilding from sources, and can be modified
via symbolic links for those OSs that support them. This directory is
nonstandard, and was chosen this way to allow XFree86 to be installed
alongside a commercial/vendor-supplied X implementation.
Subject: Configuration files
The XFree86 server reads a configuration file ("XF86Config") on startup.
The search path, contents and syntax for this file are documented in
the server manpage, which should be consulted before asking questions.
Subject: Determining VGA dot clocks and monitor modes
David E Wexelblat (dwex@XFree86.Org) maintains a database of known
clock settings for VGA cards and monitor settings.
The database is installed in /usr/X11R6/lib/X11/etc/modeDB.txt, and
is in the source tree under mit/server/ddx/x386/etc. This database is
also available from him (for the latest copy), and is kept on
ftp.XFree86.Org:/pub/XFree86/current/doc/modeDB.txt, which is updated
occasionally. Obtain a copy of this database. It just might have the
settings you need. If you create new settings, please send them to
David for inclusion in the database.
If this doesn't help you, the VideoModes.doc (by Eric Raymond) file
with XFree86 contains tutorials on how to come up with these timings.
Also look at the AccelCards file. It has a list of `known-to-work' cards
with additional info like clock chip, clocks, ramdac, etc.
They are both available from ftp.XFree86.Org:/pub/XFree86/current/doc/
which also has many helpful other files.
It may be helpful to start with settings that almost work, and use
this description to get them right. When you do, send the information
to David Wexelblat for inclusion in the database.
NOTE: The old 'clock.exe' program is not supported any more, and
is completely unnecessary. If you need to determine dot
clock values for a new board, remove the 'Clocks' line from
your XF86Config file (if present), and start the server. The
server will probe for clocks itself and print them out.
You can use these values to put a 'Clocks' line into your
XF86Config file, which is not necessary, but will speed up
starting the server in the future.
Subject: Rebuilding/reconfiguring the server from the link kit
If you have installed the server Binary Link Kit, it is possible to
reconfigure the drivers and font renderers in the server. This is
fully explained in the README file that is available with the link kit.
V) What OS-specific things should I know about running XFree86?
First of all, the server must be installed suid-root (mode 4755).
Subject: SVR4
Make sure you look at $FTP/README.SVR4.
Why won't my xterm run properly?
If your kernel is not built with the consem module, you should define
CONSEM=no in your environment. Otherwise xterm won't run.
csh users should use 'setenv CONSEM no'
The Esix console driver patch 403019 is known to cause keymapping
problems with XFree86. It is recommended that this patch not be
installed. Alternatively, the keymap can be fixed with xmodmap.
Subject: SVR3
Make sure you look at $FTP/README.isc, if that's what you are running.
Subject: BSD
Make sure you look at $FTP/[ README.Bsdi README.FreeBSD README.NetBSD ].
Subject: Linux
Make sure you look at $FTP/README.Linux.
You must be running Linux 0.99pl13 or greater, and have the 4.5.26 gcc
jump libraries and ld.so-1.3 installed.
Make sure all the servers XF86_*, xload and xterm are setuid root.
If your kernel doesn't have TCP support compiled in, you'll have to
run the server as "X -pn". The default startup configuration assumes
that TCP is not available. If it is, change the two files
/usr/X11R6/bin/startx and /usr/X11R6/lib/X11/xdm/Xservers, removing the
-pn argument to X386.
Make sure /dev/console is either a link to /dev/tty0 or has the major
number 4, minor number 0. Also note that if /dev/console is not
owned by the user running X, then xconsole and xterm will not permit
console output redirection. Xdm will properly change the owner, but
startx won't.
For more detailed information, please read the files README and
X11-HOWTO present with the distribution on tsx-11.mit.edu.
Subject: Mach
Make sure you look at $FTP/README.Mach.
VI) What things should I know for building XFree86 from source?
This section has been removed from the FAQ, since it is
fully explained in $FTP/README and the OS-specific READMEs.
Please look at those files for information on building XFree86.
VII) Is there anything special about building clients with XFree86?
Subject: BSD compatibility library
A lot of clients make use of BSD functions like bcopy(), etc.
The default configuration files are set up to link with libXbsd.a
which contains emulation for bcopy(), bzero(), bcmp(), ffs(), random(),
seed(). A better way of providing the 'b' functions is to include
<X11/Xfuncs.h> in source files that call them. Xfuncs.h provides macro
definitions for these in terms of the SYSV 'mem' functions. If you are
linking with a vendor supplied library which calls some of these
functions, then you should link with libXbsd.a
Subject: ANSICCOPTIONS
This is something that was added to allow a developer to get rid of the
ANSI-ness defined in the default CCOPTIONS without having to rewrite
the entire CCOPTIONS line. For example, with stock MIT, you'd see
something like
CCOPTIONS="-ansi -O2 -fwritable-strings"
and to get rid of the ANSI-ness, the developer would have to put
CCOPTIONS="-O2 -fwritable-strings"
in his Imakefile. With this change, you would see a default of
ANSICCOPTIONS="-ansi"
CCOPTIONS="-O2 -fwritable-strings"
and all the developer would have to put in the Imakefile is:
ANSICCOPTIONS=
to get rid of the ANSI-ness (many X clients will die a horrible death
with -ansi). The effect is even more dramatic in practice, because
CCOPTIONS is actually quite complex. The other issue is that one must
add 'ANSICCOPTIONS=$(ANSICCOPTIONS)' to a PassCDebugFlags definition.
Subject: Where to get more information
Additional documentation is available in the XFree86(1),
XF86Config(4/5), XF86_SVGA(1), XF86_Mono(1), XF86_VGA16(1),
XF86_Accel(1) and xvidtune(1) manual pages. In addition, several
README files and tutorial documents are provided. These are available
in /usr/X11R6/lib/X11/doc in the binary distributions, and in
xc/programs/Xserver/hw/xfree86/doc in the source distribution.
The files README.Config and VideoModes.doc should be consulted for
information on how to set up the XFree86 servers. All supplied
documents and manual pages should be read before contacting the
XFree86 team for assistance.
Documentation on SVGA driver development can be found in the directory
/usr/X11R6/lib/Server/VGADriverDoc in the binary distribution, and in
the directory xc/programs/Xserver/hw/xfree86/VGADriverDoc in the
source distribution.
If you are totally at a loss, you can contact the XFree86 Support Team
at <XFree86@XFree86.Org>. Before doing so, please make sure that you
are using the latest release of XFree86. Check the versions listed on
ftp.xfree86.org:/pub/XFree86 <ftp://ftp.xfree86.org/pub/XFree86>.
There is a Usenet news group comp.windows.x.i386unix that contains
mostly discussions about XFree86 and related topics. Many questions
can be answered there.
--------------------------------------------------
XFree86 Contact Information
Ongoing development planning and support is coordinated by the XFree86
Core Team. At this time the Core Team consists of (in alphabetical order):
Robin Cutshaw <robin@XFree86.org>
David Dawes <dawes@XFree86.org>
Marc Evans <marc@XFree86.org>
Dirk Hohndel <hohndel@XFree86.org>
Rich Murphey <rich@XFree86.org>
Jon Tombs <tombs@XFree86.org>
David Wexelblat <dwex@XFree86.org>
Mail sent to <Core@XFree86.org> will reach the core team.
Also, you can access their web server at url http://www.xfree86.org
--------------------------------------------------
Thanks to all the people who already sent me corrections or additions,
especially David Wexelblat (one of the major contributors of updates).
--
Steve Kotsopoulos M.Eng. steve@ecf.toronto.edu
Systems Analyst Engineering Computing Facility, University of Toronto
http://www.ecf.toronto.edu/~steve/