Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 28 May 2007 11:43:28 -0700
From:      Garrett Cooper <youshi10@u.washington.edu>
To:        Mike Meyer <mwm-keyword-freebsdhackers2.e313df@mired.org>
Cc:        ports@freebsd.org, Hartmut Brandt <hartmut.brandt@dlr.de>, hackers@freebsd.org
Subject:   Re: Looking for speed increases in "make index" and pkg_version for ports
Message-ID:  <465B22D0.8070907@u.washington.edu>
In-Reply-To: <465B1BE1.7010208@u.washington.edu>
References:  <4659EF80.70100@math.missouri.edu>	<465AB421.10802@dlr.de>	<18011.6019.436391.128372@bhuda.mired.org> <465B1BE1.7010208@u.washington.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
Garrett Cooper wrote:
> Mike Meyer wrote:
>> In <465AB421.10802@dlr.de>, Hartmut Brandt <hartmut.brandt@dlr.de> typed:
>>> 1. make and its sub-makes for a) reading the file; b) parsing the file
>>> (note that .if and .for processing is done while parsing); c) processing
>>> targets.
>>
>> Make and submakes have been gone over already. See <URL:
>> http://miller.emu.id.au/pmiller/books/rmch/ >.
>>
>> I'm not sure it can be applied to the ports tree, though. I haven't
>> looked into it, but recalled this paper when you mentioned measuring
>> makes and sub-makes.
>>
>>     <mike
> 
> Reducing the number of variables will certainly cut down on the amount 
> of overhead in the make/submake context switches by a long shot.
> 
> Maybe someone should consider running a 'pre-make' using the .mk files, 
> find the variables of interest for all particular sub-ports, and then 
> carry on the 'root make', i.e. make process in each port directory, with 
> just the variables of interest.
> 
> -Garrett

s/long shot/possibly a lot/g

Also, I was thinking in particular of the X.Org 7.2 packages, because 
the bulk majority of the packages are smaller, and compile in a short 
amount of time.

-Garrett



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?465B22D0.8070907>