Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!sbphy.ai.mit.edu!bfox
From: bfox@sbphy.ai.mit.edu (Brian Fox)
Newsgroups: gnu.bash.bug
Subject: bash size
Message-ID: <9001012134.AA26506@sbphy.Ucsb.EDU>
Date: 1 Jan 90 21:34:20 GMT
References: <229@comcon.UUCP>
Sender: daemon@tut.cis.ohio-state.edu
Reply-To: bfox@ai.mit.edu
Distribution: gnu
Organization: GNUs Not Usenet
Lines: 36


	
   Date: 30 Dec 89 22:57:25 GMT
   From: comcon!tim@uunet.uu.net  (Tim Brown)
   Organization: Computer Connection - Anchorage, Alaska
   Sender: bug-bash-request@prep.ai.mit.edu


   Platform: ISC2.0.2 SysV 3.2 on a 386
   Bash v1.04.22
   compiler: cc

   I have bash running ok, but my jaw dropped when I saw the size of the
   executable.  I played alittle....  I tried removing the debug stuff and
   adding optimization, and stripping it.  ld said it couldn't malloc
   19megs!  Since, I have re-installed from the original tar file and would
   be happy with two things.

   1. Resolve this error:

   ld 90 fatal: no string table in file make_cmd.o

This is an error in the compilation.  It is unrelated to the correctness
of the Bash source or Makefile.  On systems running NFS, I have seen
this happen when the target .o file was not fully written (presumably
because of an NFS bug).

   2. How *do* I link a smaller bash?  Mine is comming out at 580K+!

   Thanks much.

A stripped Bash is about half the size of an unstripped one.

The core size ranges from 250k to 350k depending on the hardware.

Brian Fox