This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: crosstool-generated toolchain produces massive ELF executable

From: Bill Gatliff <bgat at billgatliff dot com>
To: Dave Korn <dave dot korn at artimi dot com>
Cc: "'Robert P. J. Day'" <rpjday at mindspring dot com>, "'Khem Raj'" <khem at mvista dot com>, "'crossgcc list'" <crossgcc at sources dot redhat dot com>
Date: Tue, 31 Jan 2006 07:11:56 -0600
Subject: Re: crosstool-generated toolchain produces massive ELF executable
References: <006101c62653$359c13c0$a501a8c0@CAM.ARTIMI.COM>

Dave et al.:

Dave Korn wrote:

 Sometimes using just a few simple glibc functions can inadvertently pull in a whole boatload of other dependencies.  Does
compiling with -fno-exceptions help?
Otherwise you're just going to have to look at the output of the linker map where it shows which symbols caused which other symbols to be pulled in and figure it out. Is there a sprintf() call somewhere you could leave out, for instance?

--cref is pretty handy for this. It tells you the dependencies that caused a given module to link.

b.g.

--
Bill Gatliff
bgat@billgatliff.com


------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.org

References:
- RE: crosstool-generated toolchain produces massive ELF executable
  - From: Dave Korn

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]