Re: statically linked gcc executables

1 msg	sign_extended 32bit -addition
1 msg	g77 compiler issues
10 msg	Building a cross-compiler
2 msg	linking error with static templated member
2 msg	How to control optimization of each function
4 msg	Updating gcc on PPC with Leopard
4 msg	Problem building gcc on solaris9: no rule to ma...
10 msg	Mangle functions
1 msg	How to Properly Set a Tree Member Variable
8 msg	undefined reference to vtable for xxx
2 msg	inline assembly as PIC code?
2 msg	ICE on x86_64-pc-mingw32 / g++
5 msg	Linking problems with gcc 4.2.2 and AIX 5.2
4 msg	32 vs 34 libraries
7 msg	Why does gcc produce an unnecessary `nop' instr...
1 msg	Obtaining first argument in Objective C method ...
2 msg	install question
1 msg	configure doesn't want to use the GNU linker

statically linked gcc executables
\ Angelo leto (24 Jan 2008)
. \ Andrew Haley (24 Jan 2008)
. . \ Angelo Leto (24 Jan 2008)
. . . \ Ted Byers (24 Jan 2008)
. . . . \ Angelo Leto (24 Jan 2008)
. . . . \ John Carter (29 Jan 2008)
. . . . . \ Ted Byers (29 Jan 2008)
. . . \ Andrew Haley (24 Jan 2008)
. . . . \ Angelo Leto (24 Jan 2008)
. . . . . \ Andrew Haley (24 Jan 2008)
. . . . . . \ Angelo Leto (25 Jan 2008)
. . . . . . . \ Andrew Haley (25 Jan 2008)
. . . . . . . . \ Angelo Leto (25 Jan 2008)
. . . . . . . . . \ Angelo Leto (29 Jan 2008)
. . . . . . . . . . \ Ted Byers (29 Jan 2008)
. . . . . . . . . . . \ Angelo Leto (29 Jan 2008)
. . . . . . . . . . . . \ Ted Byers (29 Jan 2008)
. . . . . . . . . . . \ John Carter (30 Jan 2008)
. . . \ Ian Lance Taylor (25 Jan 2008)

3 msg	how could i get version of a library

Subject:	Re: statically linked gcc executables
Group:	Gcc-help
From:	John Carter
Date:	30 Jan 2008

On Tue, 29 Jan 2008, Ted Byers wrote:

> Once I make the decision to
> upgrade my tools, I don't waste further time on the
> old ones.

Yup. In all the words, these are the ones that best describe the
unavoidable difference.

You can decide what tools you will use, you can afford to abandon old
branches, we can't.

That choice of tools use for us is largely determine by what phase of
the various product lifecycles they on.

Typically some of the team will be on the final stages of a release
cycle, I'm _never_ permitted to even touch their toolset.

Some of the team will be cutting new code for a future release. I will
be feeding them the latest distro and toolchain.

Some of those guys will be pulled back to fix bugs on and do patch
releases on older releases of products. They must have the old toolset
that can live on the latest distro, but can still build the old code.

Sometimes up to two to three versions back! As I've said elsewhen in
this forum... reality sucks.

The guy in the latest Dr. Dobbs who is raving about the concept of
virtualization understands exactly where I'm at!

http://drdobbs.com/development-tools/205917147

John Carter Phone : (64)(3) 358 6639
Tait Electronics Fax : (64)(3) 359 4632
PO Box 1645 Christchurch Email : john.carter
New Zealand