Mail Archives: djgpp/2002/06/08/14:10:18
> > `djgpp_first_dtor'
> > `djgpp_last_ctor'
> > `djgpp_last_dtor'
> > `djgpp_first_ctor'
> > `end'
>
So what it sounds like to me is more-or-less "this is normally defined
on-the-fly automaticly, so it isn't neccessary for you to define it." But
DXE2GEN is apparently not allowing 'the linker' to define it. This is my
problem.
BTW: By 'the linker', do you mean gcc or really just ld? Because dxe2gen
*bypasses* gcc and gpp because it calls ld.exe directly. Any command options
that dxe2gen does not understand get passed on to ld.exe. Suggestion: Could
there be a direct ld.exe option that defines these symbols (or read
djgpp.djl )?
> The linker itself defines those, in accordance with its linker script
> (lib/djgpp.djl at the moment, or perhaps built in or elsewhere
> depending on your build).
>
> > `__djgpp_selector_limit'
>
> crt0.o but it's a "common" definition, so ultimately the linker
> creates a suitable global for it.
Been there tried that. I can't call up crt0.o manually. I get a dxe2gen
error:
$$dxe$$.o: linker output file has more than one section
Ben
- Raw text -