Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!caen!hellgate.utah.edu!dog.ee.lbl.gov!ucsd!sdcc6!sdcc12!wa115
From: wa115@sdcc12.ucsd.edu (Russell )
Newsgroups: comp.sys.apollo
Subject: Re: Difference between Unix ld and Aegis bind commands.
Message-ID: <18894@sdcc6.ucsd.edu>
Date: 2 May 91 01:24:52 GMT
References: <1991May1.035524.7904@bullet.ecf.toronto.edu>
Sender: news@sdcc6.ucsd.edu
Organization: University of California, San Diego
Lines: 23

In article <1991May1.035524.7904@bullet.ecf.toronto.edu> aerostr@bullet.ecf.toronto.edu (W. Graham Elliott) writes:
>We have recently noticed a big difference in the size of files
>created with the ld or bind commands.  For a simple Fortran program,
>which we used for testing, the Aegis bind command produced an
>executable file about 1.5 kB in size.  The corresponding ld command
>produced a 22kB file.  For a much larger program the difference was
>850 kB vs. 7,500 kB!
>
>What is in the reason for the difference in the file sizes?  
>Does it have something to do with the shared libraries?

  I'd guess that the apollo bind program is taking advantage of
 Aegis' dynamic binding scheme and not binding the standard
 libraries in with the executable.  The UNIX ld, on the other
 hand, is including the library object in the final coff file.
 That would account for the large size difference in the two
 files.


--------------------------------------------------------------------
Russell Shanks
wa115@sdcc12.ucsd.edu