[uClibc] arm toolchain/static binaries

David Meggy dmeggy at techsol.ca
Thu Jun 17 17:06:50 UTC 2004


On Wed, 2004-06-16 at 08:04, David Muse wrote:
> I've been using an arm-uclibc toolchain based on uclibc-0.9.21 for a
while now and I recently tried to upgrade to a toolchain based on the
current cvs snapshot.  I have been able to compile a complete toolchain
and it can build most of my code, but every now and then, it generates a
static binary.  If I rebuild the same code base again, the same binaries
get linked statically, so it's not exactly random, but I can't figure
out why it's linking them statically.  I'm not passing any flags that
would cause static linking, dynamic versions of each of the libraries
that need to be linked in are available, and the 0.9.21 toolchain builds
dynamically linked binaries.  It's kind of a subtle bug, I didn't notice
it for a while until one day I just noticed that the size of the jffs2
filesystem image that my build process generates was larger than I
remember.

What you have just described sounds like a problem with your build
scripts.  You have to find out where in your build scripts it is
creating these static binaries, and the complete command line to the
compiler/linker.

David

-- 
~~~~~~~~~~~~~~~~~~~~~~~~
     David Meggy
     Engineering

Technical Solutions Inc.
Unit #1 7157 Honeyman St
Delta BC Canada, V4G 1E2
     www.techsol.ca

eMail: dmeggy at techsol.ca
Tel: 604 946 TECH (8324)
Fax: 604 946 6445
~~~~~~~~~~~~~~~~~~~~~~~~




More information about the uClibc mailing list