gcc: Undefined references while linking (2)
CJ
carjay@gmx.net
Tue Sep 24 20:55:00 GMT 2002
William A. Gatliff wrote:
>Anyway, you could just throw in stubs for _exit, sbrk, kill and getpid
>to get around the unresolved symbols. Yes, those would be provided by
>an OS or reasonable facsimile thereof. Completely unnecessary unless
>you need them.
>
>I don't get the EH_FRAME_BEGIN thing yet, though. What happens if
>your test module has:
>
>void __main(void){}
>
>(two underscores) in it?
>
>
Hi,
if I try both of your suggestions it works though I also tried it with
another function name (like "void foo(void){}) and it still works, so
that name has no special meaning. I take it that because there is no
crt0.S, no "main"-function is required. Still then I don't understand
why using "main" produces the "EH_FRAME"-error.
Basically I feel like I need to do a lot of reading, but the problem is,
I don't really know where to look. :-(
Will see if the GCC-manual can give me some insight.
Carsten
------
Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
More information about the crossgcc
mailing list