bug id=57303

Alan Coopersmith alan.coopersmith at oracle.com
Fri Jan 25 21:49:31 PST 2013


On 01/25/13 06:44 PM, Peter Hutterer wrote:
> On Fri, Jan 25, 2013 at 07:50:51PM -0500, Dennis Clarke wrote:
>>
>>
>>>
>>> build.sh takes a --modfile arg listing all the modules you want to build.
>>
>> awesome.
>>
>> I looked in there and saw the tseng driver for an IBM PS/2 from 1994 I think. Not needed. 
>>
>> Well, at the moment the only trouble spot I seem to hit was something called a newport driver, so I commented that out in the build.sh script : 

Newport was a video board for SGI Indy/Indigo2 workstations (more details can
be found in it's README file for the morbidly curious), not likely to be found
anywhere near most PC's.

>> Fire off a rebuild and see : 
>> aster $ ./util/modular/build.sh --clone --autoresume built.modules /opt/xorg
>> Building to run Linux / x86_64 ()
>> Fri Jan 25 19:46:35 EST 2013
>> Skipping util module component macros...
> 
> skipping means it didn't build it, so judging by the output you skipped all
> modules.

I thought there was a build.sh flag to output the default mod list, but I don't
see it or remember it.   The file I pass to --modfile has a the modules listed
as:

util/macros
font/util
doc/xorg-sgml-doctools
doc/xorg-docs
proto/bigreqsproto

and so on.

Of course, I also run it with the -n flag to keep on going after error, since
I'm usually just using it to see which modules build cleanly and which I now
need to fix to build on Solaris for some reason.

-- 
	-Alan Coopersmith-              alan.coopersmith at oracle.com
	 Oracle Solaris Engineering - http://blogs.oracle.com/alanc


More information about the xorg mailing list