Bug 2060 - BUILDING doesn't describe testing prerequisities
Summary: BUILDING doesn't describe testing prerequisities
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Documentation (show other bugs)
Version: unspecified
Hardware: All All
: high normal
Assignee: Xorg Project Team
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 3643
  Show dependency treegraph
 
Reported: 2004-12-12 04:24 UTC by Karel Clock Kulhavy
Modified: 2005-12-20 15:55 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Karel Clock Kulhavy 2004-12-12 04:24:30 UTC
BUILDING reads:
"The build tools
known to be required include: gcc, make, C library development package, bi-
son, flex, zlib (development package), ncurses (development package), font-
config (development package), expat (development package), and Perl"

Nothing is said about
* how to meet these prerequisities if those packages weren't installed
previously - usually list of official homepages of the projects that contain a
step-by-step guide how to install on a system where the package wasn't previously
installed
* How to test if an already installed package meets requirements imposed by
xserver (integrity, version, etc.) - usually list of required static and dynamic
libraries in certain paths, includes in certain paths, .pc files in certain paths
etc.

I suggest the following:
* answers to outlined questions to be deterined by authorized persons (presumably
the developers of xserver)
* answers put into BUILDING together with list of required libraries
Comment 1 Siward de Groot 2005-08-07 22:26:54 UTC
Created attachment 3285 [details] [review]
Proposed patch to fix the problem
Comment 2 Alan Coopersmith 2005-11-05 10:24:27 UTC
Proposed patch from comment #1 was lost in bugzilla disk death.   Please 
reattach.
Comment 3 Alan Coopersmith 2005-12-21 10:55:53 UTC
Mostly fixed in Xorg 6.9 BUILDING instructions.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.