This is the mail archive of the
mailing list for the GCC project.
Re: FAQ: how to build a statically-linked gcc?
- From: "Wolcott, Ken (MED, Compuware)" <Ken dot Wolcott at med dot ge dot com>
- To: Ronald Landheer-Cieslak <blytkerchan at users dot sourceforge dot net>, Dan Kegel <dank at kegel dot com>
- Cc: GCC Mailing List <gcc at gcc dot gnu dot org>, crossgcc <crossgcc at sources dot redhat dot com>
- Date: Wed, 15 Oct 2003 11:41:50 -0500
- Subject: Re: FAQ: how to build a statically-linked gcc?
- Organization: GEMS-IT
- References: <3F8D702F.email@example.com> <20031015170411.GC3117@linux_rln.harvest>
- Reply-to: "Wolcott, Ken (MED, Compuware)" <ken dot wolcott at med dot ge dot com>
I tried "--disable-shared" and I also tried "--enable-static" as options to
gcc (3.3) configure and running ldd on the resultant gcc executeable showed
it was using local libraries, while inserting "-static" on the LD line in the
generated Makefile resulted in ldd not being able to find any external
linkages. My newbie opinion is that configure is broken.
On Wednesday 15 October 2003 12:04, Ronald Landheer-Cieslak wrote:
> AFAIK, --disable-shared should do that.. but I think that laso has a
> side-effect on exception handling..
> If there's a better way, I'd like to know it :)
> On Wed, Oct 15, 2003 at 09:05:03AM -0700, Dan Kegel wrote:
> > Can somebody clue me in on the right way to build static gcc binaries?
> > http://gcc.gnu.org/install/configure.html doesn't seem to say.
> > One user of my crosstool script really wants this,
> > and is currently hacking the Makefile to add -static
> > ( http://sources.redhat.com/ml/crossgcc/2003-10/msg00068.html ).
> > Thanks,
> > 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
> > firstname.lastname@example.org