This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Undefined symbols with exceptions for an egcs 1.1.1 cross-compiler
- To: egcs at egcs dot cygnus dot com
- Subject: Re: Undefined symbols with exceptions for an egcs 1.1.1 cross-compiler
- From: mrs at wrs dot com (Mike Stump)
- Date: Thu, 7 Jan 1999 15:41:13 -0800
> From: Damian Gilmurray <dgilmurray@adaptivebroadband.com>
> Date: 07 Jan 1999 12:14:28 +0000
> These symbols were indeed being defined in tinfo.o and tinfo2.o but were
> defined as common symbols. However, the cross-compiler is for an embedded
> environment and in this environment we are using a bespoke linker
Why? Use GNU ld. Worst case scenario, you convert OMF to the style
you want at the end with a custom program. You will win more in the
end if you do this.
> This linker cannot handle the resolution of common symbols
Well, sounds like you need to fix your linker.
> With the following patch:
> I can successfully link the application. I know very little about the
> implementation of RTTI so please excuse any ignorance on my behalf but is
> there a particular reason why the no-common flag is ignored here?
Yes, because ignoring it wont work. You can sit down and try and
redesign rtti around your patch, but I don't think that is the right
direction.