Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!purdue!news.bu.edu!noc.near.net!MathWorks.Com!europa.eng.gtefsd.com!gatech!news.byu.edu!cwis.isu.edu!u.cc.utah.edu!cs.weber.edu!terry From: terry@cs.weber.edu (Terry Lambert) Newsgroups: comp.os.386bsd.misc Subject: Re: Shared Library Status ? Date: 8 Mar 1994 01:48:21 GMT Organization: Weber State University, Ogden, UT Lines: 31 Message-ID: <2lglh5$otn@u.cc.utah.edu> References: <michaelv.762936864@ponderous.cc.iastate.edu> <hastyCM9r6q.KFB@netcom.com> <CMApnr.3rB@cogsci.ed.ac.uk> NNTP-Posting-Host: cs.weber.edu In article <CMApnr.3rB@cogsci.ed.ac.uk> richard@cogsci.ed.ac.uk (Richard Tobin) writes: >In article <hastyCM9r6q.KFB@netcom.com> hasty@netcom.com (Amancio Hasty Jr) writes: [ ... 11 minute kernel compile on old system, 22 minutes on NetBSD with shared libraries ... ] >Well, there are rather a lot of variables there! For example, you've >probably switched from gcc1 to gcc2. FreeBSD-current (and 1.1-Beta) is gcc2. >Building the kernel is a fairly bad case for shared libraries - lots of >small(ish) compilations, each with several processes being started. I am [mostly] running FreeBSD-current. My kernel compile takes four minutes for the generic config. For the full sources from scratch without the "ports" stuff, I spend right around 3 hours. I remember an Amdahl at a tradeshow once that could do the same in about 35 minutes. Most of the time seemed to be waiting for the screen to scroll using the 9600 baud link to the machine. This is a rather singularly useless benchmark unless you guarantee all the hardware is the same in all cases. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers.