This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.

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: Building _statically linked_ crosscompiler toolchain.

From: David Daney <ddaney at avtrex dot com>
To: John Carter <john dot carter at tait dot co dot nz>
Cc: gcc-help at gcc dot gnu dot org
Date: Thu, 07 Jun 2007 17:18:51 -0700
Subject: Re: Building _statically linked_ crosscompiler toolchain.
References: <Pine.LNX.4.64.0706081145370.4424@parore.tait.co.nz>

John Carter wrote:

Ok, so I can build the latest gcc,binutils i686 linux hosted, embedded
sparc-elf newlib target crosscompiler tool chain.

Great.

Unfortunately some of the team (bless their smelly sockses) are on
different Linux distributions, older distributions etc. Thus different
shareable libraries.

ie. The tools don't run on many of my colleagues machines.

Obviously the answer is to statically link the tools.

The question is "What is The One True Way (or any blooming way) to
build a _completely_ statically linked gcc crosscompiler toolchain?"

glibc does not work very well statically linked. So I don't think that is a good idea.

Perhaps you should build the toolchain on the oldest distribution that will have to be supported. An alternative is to have a build for each incompatible host system.

David Daney

Follow-Ups:
- Re: Building _statically linked_ crosscompiler toolchain.
  - From: John Carter

References:
- Building _statically linked_ crosscompiler toolchain.
  - From: John Carter

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