tim@comcon.UUCP (Tim Brown) (12/31/89)
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 Stop. This is from a complete re-install from tar file. I only made some changes so DIR would work and termsig. 2. How *do* I link a smaller bash? Mine is comming out at 580K+! Thanks much. -- Tim Brown | Computer Connection | (attmail or uunet)!comcon!tim |
bfox@sbphy.ai.mit.edu (Brian Fox) (01/02/90)
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