[darwinbuild] buildorder

Kevin Van Vechten kevin at opendarwin.org
Tue Dec 20 13:38:37 PST 2005


Oh, I know...  The buildorder script relies on the plists from  
release.opendarwin.org.  You can do the following in your existing  
build directory (/tmp/Builds/Build8F46) to "upgrade" your plist:

# curl -O http://release.opendarwin.org/release/8.3.1/plists/ 
8F46od1.plist
# darwinbuild -init 8F46od1

Then the buildorder script should work.  What happened is buildorder  
relies on the "group" information in the od1 plist, that tell it  
which projects are used as compilers, etc., so it can make better  
ordering decisions.  I probably should add that information into the  
"standard" 8F46.plist.  Thanks for the report.

- Kevin

On Dec 20, 2005, at 1:29 PM, Shannon Pasto wrote:

> yes I do have write permissions to this directory ( /tmp/Builds/ 
> Build8F46 ).
>
> when I run the command ( /usr/local/share/darwinbuild/buildorder  
> projects.txt ordered.txt ) I get a list of 'considering projects'  
> then 'Compilers:' with nothing after compilers.  The dependency  
> graph is done, then I get 'Aborting, unmet dependency loop'.   
> Following that I get a list of remaining projects.
>
> not sure if unmet line means anything.
>
> Shannon
>
> On 21/12/2005, at 08:16 , Kevin Van Vechten wrote:
>
>> Do you have write permission to the current directory?  Are you  
>> seeing any errors?  buildorder is working for me, and there have  
>> never been any changes made to the file...
>>
>> - Kevin
>>
>> On Dec 20, 2005, at 12:51 PM, Shannon Pasto wrote:
>>
>>> the ordered.txt file is not being created in the current directory.
>>>
>>> Shannon
>>>
>>> On 21/12/2005, at 07:44 , Kevin Van Vechten wrote:
>>>
>>>> On Dec 20, 2005, at 12:33 PM, Shannon Pasto wrote:
>>>>> do assume correctly that when 'buildorder' is run it should  
>>>>> output the projects in the order that they should be built to a  
>>>>> file which is entered as part of the command?  If it is, then  
>>>>> it didn't for me.  All I got was the list (on a single line)  
>>>>> output to std out.
>>>>>
>>>>> Can someone please confirm this?
>>>>
>>>> In the example I gave:
>>>>
>>>> # darwinxref version '*' | sed -e 's/-.*//' > projects.txt
>>>> # /usr/local/share/darwinbuild/buildorder projects.txt ordered.txt
>>>> # /usr/local/share/darwinbuild/buildlist ordered.txt
>>>>
>>>> ordered.txt is the output file, and does not need to exist prior  
>>>> to issuing the buildorder command.  You can ignore the output  
>>>> printed to stdout.
>>>>
>>>> - Kevin
>>>>
>>>
>>> --
>>> Mr Shannon Pasto
>>> Apple Certified Desktop Technician
>>> Apple Certified Portable Technician
>>> Apple Certified Helpdesk Specialist
>>>
>>> The Walter & Eliza Hall Institute of Medical Research
>>> Information Technology Services
>>> 1G Royal Parade
>>> PARKVILLE VIC 3050
>>> AUSTRALIA
>>> ph 03 9345 2422 (int +61 3 9345 2422)
>>> fax 03 9347 0852 (int +61 3 9347 0852)
>>> mailto:shannonp at wehi.EDU.AU
>>> http://www.wehi.edu.au/
>>>
>>
>
> --
> Mr Shannon Pasto
> Apple Certified Desktop Technician
> Apple Certified Portable Technician
> Apple Certified Helpdesk Specialist
>
> The Walter & Eliza Hall Institute of Medical Research
> Information Technology Services
> 1G Royal Parade
> PARKVILLE VIC 3050
> AUSTRALIA
> ph 03 9345 2422 (int +61 3 9345 2422)
> fax 03 9347 0852 (int +61 3 9347 0852)
> mailto:shannonp at wehi.EDU.AU
> http://www.wehi.edu.au/
>




More information about the darwinbuild-dev mailing list