Return to BSD News archive
Newsgroups: comp.os.386bsd.apps Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!sgiblab!spool.mu.edu!nigel.msen.com!zib-berlin.de!math.fu-berlin.de!fub46!gusw From: gusw@zedat.fu-berlin.de (Gunther Shadow) Subject: Re: Anybody made akcl-1-625? Message-ID: <I59QBO6L@math.fu-berlin.de> Sender: news@math.fu-berlin.de (Math Department) Nntp-Posting-Host: fub46.zedat.fu-berlin.de Organization: Free University of Berlin, Germany References: <AH6QBAUW@math.fu-berlin.de> <CttvvB.C3x@cogsci.ed.ac.uk> <GD7QBDG@math.fu-berlin.de> <CtwosL.3Ar@cogsci.ed.ac.uk> Date: Wed, 3 Aug 1994 21:17:36 GMT Lines: 28 richard@cogsci.ed.ac.uk (Richard Tobin) writes: >> The real problem is, that I don't want to link with -static, but >>I want to get a dynamic -- and thus a more efficient -- akcl. >I don't see the point. It isn't going to be much smaller (a few tens >of K perhaps) and certainly no faster. Dynamic executables aren't >more "efficient" except in terms of size (they're slower), and unless >you're linking with some huge library (eg X) the size difference will >be negligible for a system as big as KCL. And size is exactly the factor that concerns me most! Particularely I want to link akcl with the xakcl code, so I am able to use the X11 interface for akcl. When I tried it on 386bsd long time ago, I ended up with an executable more than 3 MB in size. Now imagine this running on an 8MB dram machine with X11 server and emacs all active at the same time! I think that there will be more of efficiency with shared libraries here. I see now that the fasl loader may be the next source of a problem, but I didn't try that yet. Thank's a lot, -Gunther -- Gunther Schadow_________________________Hopfenweg 19, Berlin 12357, FR. Germany Dept. of Anaesthesia and Operative Intensive Care Medicine/ Dept. of Medical Informatics at the |gusw@boskop.uks.fu-berlin.de Universitaetsklinikum Steglitz, Berlin, FRG. |gusw@fub46.zedat.fu-berlin.de