This is the mail archive of the crossgcc@sources.redhat.com 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: static linking error

From: Dan Kegel <dank at kegel dot com>
To: Charles Lockhart <lockhart at jeans dot ifa dot hawaii dot edu>, crossgcc <crossgcc at sources dot redhat dot com>
Date: Tue, 08 Jul 2003 14:14:47 -0700
Subject: Re: static linking error
References: <3F0B2734.4050505@irtf.ifa.hawaii.edu> <3F0B2F48.1060507@kegel.com> <3F0B2F0B.1030602@irtf.ifa.hawaii.edu>

Charles Lockhart wrote:

Running "$(CROSS_COMPILE)gcc test.c -s" I get a small binary file that's identical to the one generated if I don't statically link the executable.

Ah, silly me, I meant -static.

I'm trying to create a stand alone executable that I can download to the target system via a jtag interface and have it run. But maybe I'm taking the wrong approach.


Hmm.  Most people in your shoes use newlib, not glibc.  Newlib, I hear,
includes things like itoa without having any nasty references to
an underlying operating system.

'Course, you'll need to add newlib support to the crosstool script to do
that.  It's probably not too hard; somebody else was already interested
in it, maybe they've started.
- Dan

--
Dan Kegel
http://www.kegel.com
http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045


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

References:
- static linking error
  - From: Charles Lockhart
- Re: static linking error
  - From: Dan Kegel

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