This is the mail archive of the egcs@egcs.cygnus.com mailing list for the EGCS project. See the EGCS home page for more information.


[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index] [Subject Index] [Author Index] [Thread Index]

Re: multiple definitions of 'xxx keyed to...' in egcs-1.1.1



>>>>> Jeffrey A Law <law@hurl.cygnus.com> writes:

 >   In message <199902160838.JAA00531@mira.isdn.cs.tu-berlin.de>you write:
 >> For ELF targets, do you really think this is a widely-used approach?

 > Widely used is not the criteria.  Lots of things are not widely used, but
 > we still have to support them.

We have never supported running ctors for a single .o, and I don't see any
reason to start.  I've never heard of loading a single .o dynamically
without linking it into a shared object.

 >> If you insist on loading relocatable ELF objects dynamically, you
 >> still can do that: just locate and execute the .init section. No
 >> symbol name needed.

 > Do we have a .init section for just the .o?  If so, then ignore this issue.

We have an .init section; we don't have the _init function if we don't link
against crt[in].o.

Jason