Thanks Brian. Looks like Multilib was the major difference. The 2.95.2 build responded with ".;" while the 4.2.0 build responded with 8 libraries. I'm about to try a build with --disable-multilib and see what happens. I just needed some hints on where to look. That helped. Thanks John Morrison Printronix, Inc -----Original Message----- From: Brian Dessent [mailto:brian@xxxxxxxxxxx] Sent: Tuesday, April 08, 2008 3:05 PM To: John Morrison Cc: gcc-help@xxxxxxxxxxx Subject: Re: Ouch! Install size went from 18M to 900M. John Morrison wrote: > I can not believe that the compiler and binutils increased that much > between 2.95.2 and 4.2.0. What can I specify to cut this down? There > must have been something that opted in that I can turn off. I would guess mutlilibs and debug info contribute to that. You can print the list of multilibs configured for your target with -print-multi-lib, and if it's too many or you don't need multilib capability you can --disable-multilib when configuring. Some targets build a great number of multilibs. To strip debug info there are a number of techniques, e.g. 'make LDFLAGS="-s"'. But really, you have the before and after files, we don't. So it would seem you are the only one that can truly answer this question. gcc is a complex program with many optional supporting libs/features, and supports so many various targets that it's hard to just pick and ancient version built with unknown options and recent version and tell what's different given only disk space usage. Brian
