This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: unresolved symbol terminate__Fv and __throw
- To: mrs at windriver dot com
- Subject: Re: unresolved symbol terminate__Fv and __throw
- From: "Martin v. Loewis" <martin at loewis dot home dot cs dot tu-berlin dot de>
- Date: Thu, 6 Jan 2000 00:14:30 +0100
- CC: gcc at gcc dot gnu dot org, vgo at ratio dot de
- References: <200001051931.LAA04607@kankakee.wrs.com>
> > Is it possible to implement this two functions, and if , what parameter
> > do they need?
>
> Sure, gcc -nostdlib -r -o t1.o t.o `gcc --print-libgcc` will resolve
> all the symbols it can from the library and include those in the t1.o
> file.
Alternatively, you could customize libgcc2.c, frame.c, etc to produce
your own version (that wouldn't rely on libc stuff). In addition,
you'd also have to fight initialization, by calling
__register_frame_info appropriately.
I guess you have the initialization problem, anyway; I doubt the Linux
module loading does the right processing of .init sections for your -
if you have been linking crtbegin/end at all...
Regards,
Martin