This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: why no gcc3_compiled symbol
- From: Andreas Schwab <schwab at suse dot de>
- To: Jack Howarth <howarth at bromo dot med dot uc dot edu>
- Cc: gcc at gcc dot gnu dot org
- Date: Wed, 31 Jul 2002 14:28:21 +0200
- Subject: Re: why no gcc3_compiled symbol
- References: <200207311205.IAA71417@bromo.msbb.uc.edu>
Jack Howarth <howarth@bromo.msbb.uc.edu> writes:
|> Does anyone know why gcc >= 3.0 doesn't have a gcc3_compiled
|> symbol like gcc 2.9x had a gcc2_compiled symbol? I ask because in
|> tracking down a problem with a gcc 3.1.1 built XFree86 loading its
|> libGLcore.a xserver module we found gcc 3.1.1 will create completely
|> empty object files. This compares to gcc 2.95.4 or 2.96 which would
|> always leave a gcc2_compiled placekeeper symbol in an empty object
|> file. This is arose because when you strip a gcc 3.1.1 built
|> static lib that has such an empty object file linked in you get
|> a object file with no symbols at all. This breaks the current
|> XFree86 loader.
Then the XFree86 loader is broken, IMHO.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."