delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp-workers/2002/12/20/14:01:38

Date: Fri, 20 Dec 2002 20:59:51 +0300
From: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender: halo1 AT zahav DOT net DOT il
To: djgpp-workers AT delorie DOT com
Message-Id: <9743-Fri20Dec2002205950+0200-eliz@is.elta.co.il>
X-Mailer: emacs 21.3.50 (via feedmail 8 I) and Blat ver 1.8.9
In-reply-to: <10212192240.AA24070@clio.rice.edu> (sandmann@clio.rice.edu)
Subject: Re: Audit of empty image
References: <10212192240 DOT AA24070 AT clio DOT rice DOT edu>
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com

> From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
> Date: Thu, 19 Dec 2002 16:40:58 -0600 (CST)
> 
> The following symbols get pulled into each image built with CVS.  It 
> makes my head spin...

Well, please remember that the startup code does memory allocation,
creates the environ[] array and looks at environment variables such
as LFN, copies strings to and fro, expands command-line wildcards,
reads and processes the DJGPP.ENV file, etc. etc...  So it's niot
surprising we use so many library functions: otherwise, where would
the 30KB of minimal image come from? ;-)

> Some like lseek and llseek we can probably fix.

Also `remove' and `_truename' caused my brows to go up.  Whatever do
we need those for in the startup code?

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019